Upstream microrelease of squid 5.9

Bug #2040470 reported by Bryce Harrington
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
squid (Ubuntu)
New
Undecided
Unassigned
Jammy
Fix Committed
Undecided
Sergio Durigan Junior

Bug Description

This bug tracks the following MRE updates for the Squid package:

    Jammy (22.04): 5.9

This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.

[Upstream changes]

http://www.squid-cache.org/Versions/v5/ChangeLog.html
(Jammy: 5.7..5.9)

The two releases that we are MRE'ing here (5.8 and 5.9) do not contain major/noticeable changes per se. There are quite a few bugfixes, some of them generic enough to benefit Ubuntu users, others specifically aimed at problems we don't experience (like LLVM-build fixes). A few noteworthy bugfixes have been added to the d/changelog entry.

[Test Plan]

The proposed changes were applied in the following PPA: https://launchpad.net/~sergiodj/+archive/ubuntu/squid/+packages

Build logs can be found for the builds in the PPA linked above. Here are the amd64 one:

https://launchpadlibrarian.net/724125399/buildlog_ubuntu-jammy-amd64.squid_5.9-0ubuntu0.22.04.1~ppa3_BUILDING.txt.gz

All tests are passing during build time, as shown in the build log (builds would fail otherwise, see LP: #2004050).

TODO: add results of local autopkgtest run against all the new Squid versions being uploaded here

[Regression Potential]

Upstream tests are always executed during build-time. Failures would prevent builds from succeeding.

Squid does not have many reverse dependencies. However, any upgrade is a risk to introduce breakage to other packages. Whenever a regression occurs in autopkgtests, we will investigate and provide fixes.

TODO: consider any other regression potential specific to the version being updated and list them here if any.

[Other Info]

No CVEs are being addressed this time. Therefore, this should go through the updates pockets.

Related branches

Bryce Harrington (bryce)
Changed in squid (Ubuntu):
milestone: none → ubuntu-24.02
no longer affects: squid (Ubuntu Noble)
Changed in squid (Ubuntu Jammy):
assignee: nobody → Sergio Durigan Junior (sergiodj)
tags: added: server-todo
description: updated
summary: - MRE updates of squid for noble
+ Upstream microrelease 5.9
description: updated
Bryce Harrington (bryce)
summary: - Upstream microrelease 5.9
+ Upstream microrelease of squid 5.9 for noble
Revision history for this message
Sergio Durigan Junior (sergiodj) wrote : Re: Upstream microrelease 5.9

Hi Bryce,

I'm following the same title pattern as established by Athos, which I think is better in this case. Just leaving the explanation here :-).

summary: - Upstream microrelease of squid 5.9 for noble
+ Upstream microrelease 5.9
Revision history for this message
Bryce Harrington (bryce) wrote : Re: [Bug 2040470] Re: Upstream microrelease 5.9

Hi Sergio,

Ah gotcha; only issue is that in Pinot the MRE cards don't show the
package name, so the resultant card isn't clear what it's for. Could
you explain what makes it better for this case?

On Wed, Apr 10, 2024 at 03:02:37PM -0000, Sergio Durigan Junior wrote:
> Hi Bryce,
>
> I'm following the same title pattern as established by Athos, which I
> think is better in this case. Just leaving the explanation here :-).
>
> ** Summary changed:
>
> - Upstream microrelease of squid 5.9 for noble
> + Upstream microrelease 5.9
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2040470
>
> Title:
> Upstream microrelease 5.9
>
> Status in squid package in Ubuntu:
> New
> Status in squid source package in Jammy:
> New
>
> Bug description:
> This bug tracks the following MRE updates for the Squid package:
>
>     Jammy (22.04): 5.9
>
> This update includes bugfixes following the SRU policy exception
> defined at https://wiki.ubuntu.com/SquidUpdates.
>
> [Upstream changes]
>
> http://www.squid-cache.org/Versions/v5/ChangeLog.html
> (Jammy: 5.7..5.9)
>
> TODO: List the major changes introduced in this release
>
> [Test Plan]
>
> TODO: link the build log containing all tests being executed
>
> TODO: All tests are passing during build time, as shown in the build
> log (builds would fail otherwise, see LP: #2004050).
>
> TODO: add results of local autopkgtest run against all the new Squid
> versions being uploaded here
>
> [Regression Potential]
>
> Upstream tests are always executed during build-time. Failures would
> prevent builds from succeeding.
>
> Squid does not have many reverse dependencies. However, any upgrade is
> a risk to introduce breakage to other packages. Whenever a regression
> occurs in autopkgtests, we will investigate and provide fixes.
>
> TODO: consider any other regression potential specific to the version
> being updated and list them here if any.
>
> [Other Info]
>
> TODO-A: No CVEs are being addressed this time. Therefore, this should
> go through the updates pockets.
>
> TODO-B: CVEs TBD are being addressed by these updates. Therefore, this
> update should go through the security pocket.
>
> TODO: list previous MREs for this package, if any.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/squid/+bug/2040470/+subscriptions

Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

Ah, got it. I've added "of squid" in the title now, should read better on Pinot. Thanks!

summary: - Upstream microrelease 5.9
+ Upstream microrelease of squid 5.9
Changed in squid (Ubuntu Jammy):
status: New → Triaged
description: updated
description: updated
description: updated
Changed in squid (Ubuntu Jammy):
status: Triaged → In Progress
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Please test proposed package

Hello Bryce, or anyone else affected,

Accepted squid into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/squid/5.9-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in squid (Ubuntu Jammy):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-jammy
Revision history for this message
Simon Déziel (sdeziel) wrote :

@sergiodj, it's not a proper SRU/MRE verification but this 5.9-0ubuntu0.22.04.1 is running fine on my home lab. If I run into any problem with it, I'll report back here. Thanks!

Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

Thank you, Simon.

I can also confirm that all autopkgtests passed. Therefore, marking this bug as verified for Jammy.

tags: added: verification-done verification-done-jammy
removed: verification-needed verification-needed-jammy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.