Please merge squid3 3.3.3-2 (main) from Debian unstable (main)
Bug #1175049 reported by
H.-Dirk Schmitt
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Precise Backports |
Invalid
|
Undecided
|
Unassigned | ||
squid3 (Debian) |
Fix Released
|
Unknown
|
|||
squid3 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Current Ubuntu Versions are:
* squid3 (3.1.19-
* squid3 (3.1.20-1ubuntu3) raring-proposed; urgency=low
The upstream versions are:
* 3.3
* 3.2 [deprecated, see announcement mails]
* 3.1 [old, [see http://
I suggest to make the squid 3.3 available in precise-backports and saucy.
---
Ubuntu Bug Squad volunteer triager
http://
tags: | added: precise saucy |
Changed in squid3 (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in squid3 (Debian): | |
status: | Unknown → Fix Released |
Changed in squid3 (Ubuntu): | |
status: | Triaged → Fix Released |
To post a comment you must log in.
Thanks for reporting this.
sid is on 3.3.3-2 and Saucy on 3.1.20-1ubuntu3 so a merge is appropriate here. This needs to happen before any backport.
I'm not sure whether the backports team would like a new bug for this after Saucy is updated or not.