update squid from 3.3.8 to 3.3.14

Bug #1502178 reported by Tiago Stürmer Daitx on 2015-10-02
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
squid3 (Ubuntu)
Undecided
Unassigned

Bug Description

squid 3.3.8 was released on 2013-07-13, more than 2 years ago. Unless it gets merged with Debian's 3.5 it should at least be updated the new 3.3.14 release from 2015-05-01.

Note: this is not a duplication of LP: #1473691; that one is about updating from 3.3 to 3.5+ and closing a bug that AFAICS was not fixed in 3.3.14. Still, this is a continuation of LP: #1496223 to be used if and only if we don't merge 3.5+ from Debian.

description: updated
Sebastien Bacher (seb128) wrote :

bug #1473691 is about updating as well

Sebastien Bacher (seb128) wrote :

closing as duplicate, updating to one version or another can be discussed on one bug report

Tiago Stürmer Daitx (tdaitx) wrote :

Requires libecap2v5 (gcc5 transition of libecap2) and squid3-3.3.8-1ubuntu16, debdiffs available at LP: #1496223

Build test package at https://launchpad.net/~tdaitx/+archive/ubuntu/testing/+sourcepub/5473877/+listing-archive-extra

Tiago Stürmer Daitx (tdaitx) wrote :

Apologies, this is not a duplicate of LP: #1473691. That one is about updating to 3.5+ and closing a bug that AFAICS was not fixed in 3.3.14.

This is a continuation of LP: #1496223 to be used if and only if we don't get a merge of 3.5+.

Thanks! =)

tags: added: ftbfs
description: updated
Robie Basak (racb) on 2015-10-06
tags: added: upgrade-software-version
tags: added: patch
Adam Conrad (adconrad) wrote :

From a supportability standpoint, it's actually easier to have the same upstream version in trusty and wily (given that trusty is supported longer), so security patches apply identically to both.

Are there any arguments for a late-in-the-release update to 3.3.14 other than "it's newer"?

If not, I'd say we should just close this and look to merging with Debian for 16.04.

Adam,

That's a good point. None of the reported LP bugs are fixed by this
particular update. That said, the list of bug fixes in this update is
quite high.

I would be willing to SRU this for Trusty as well to keep it in sync.

Adam Conrad (adconrad) wrote :

SRUing to trusty would require a pretty comprehensive test plan and a justification for the massive upstream delta. It's likely not a reasonable thing to be suggesting in a stable update.

Steve Langasek (vorlon) wrote :

No longer needed for 16.04; we will jump straight to a merge of squid 3.5 from unstable.

Changed in squid3 (Ubuntu):
status: New → Fix Released
status: Fix Released → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers