| 2023-10-25 08:32:40 |
Bryce Harrington |
bug |
|
|
added bug |
| 2023-10-25 08:32:42 |
Bryce Harrington |
squid (Ubuntu): milestone |
|
ubuntu-24.02 |
|
| 2023-10-25 08:32:43 |
Bryce Harrington |
nominated for series |
|
Ubuntu Noble |
|
| 2023-10-25 08:32:44 |
Bryce Harrington |
bug task added |
|
squid (Ubuntu Noble) |
|
| 2023-10-25 08:32:46 |
Bryce Harrington |
bug |
|
|
added subscriber Canonical Server |
| 2024-04-03 16:06:35 |
Sergio Durigan Junior |
nominated for series |
|
Ubuntu Jammy |
|
| 2024-04-03 16:06:35 |
Sergio Durigan Junior |
bug task added |
|
squid (Ubuntu Jammy) |
|
| 2024-04-03 16:06:40 |
Sergio Durigan Junior |
bug task deleted |
squid (Ubuntu Noble) |
|
|
| 2024-04-03 16:06:56 |
Sergio Durigan Junior |
squid (Ubuntu Jammy): assignee |
|
Sergio Durigan Junior (sergiodj) |
|
| 2024-04-03 16:07:08 |
Sergio Durigan Junior |
tags |
needs-mre-backport |
needs-mre-backport server-todo |
|
| 2024-04-03 16:07:16 |
Sergio Durigan Junior |
bug |
|
|
added subscriber Ubuntu Server |
| 2024-04-03 16:09:07 |
Sergio Durigan Junior |
description |
Backport squid as MRE to noble once the update for noble has been completed.
<List exact versions being upgraded from and to for each release>
[Impact]
TBD
<List bug links to former cases of MREs for this package>[Major Changes]
TBD
[Test Plan]
<Link to wiki SRU page>TBD
[Regression Potential]
Upstream has an extensive build and integration test suite. So regressions would likely arise from a change in interaction with Ubuntu-specific integrations, such as in relation to the versions of dependencies available and other packaging-specific matters.
<Also, ...>
|
This bug tracks the following MRE updates for the Squid package:
[Release codename] ([Release version]): Squid [Squid version]
[...]
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
TODO: Add a link to the upstream changelog
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. |
|
| 2024-04-03 16:09:34 |
Sergio Durigan Junior |
summary |
MRE updates of squid for noble |
Upstream microrelease 5.9 |
|
| 2024-04-03 16:11:36 |
Sergio Durigan Junior |
description |
This bug tracks the following MRE updates for the Squid package:
[Release codename] ([Release version]): Squid [Squid version]
[...]
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
TODO: Add a link to the upstream changelog
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. |
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. |
|
| 2024-04-10 05:12:25 |
Bryce Harrington |
summary |
Upstream microrelease 5.9 |
Upstream microrelease of squid 5.9 for noble |
|
| 2024-04-10 15:01:55 |
Sergio Durigan Junior |
summary |
Upstream microrelease of squid 5.9 for noble |
Upstream microrelease 5.9 |
|
| 2024-04-10 18:32:12 |
Sergio Durigan Junior |
summary |
Upstream microrelease 5.9 |
Upstream microrelease of squid 5.9 |
|
| 2024-04-10 19:30:17 |
Sergio Durigan Junior |
merge proposal linked |
|
https://code.launchpad.net/~sergiodj/ubuntu/+source/squid/+git/squid/+merge/464045 |
|
| 2024-04-10 19:30:28 |
Sergio Durigan Junior |
squid (Ubuntu Jammy): status |
New |
Triaged |
|
| 2024-04-10 19:38:46 |
Sergio Durigan Junior |
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. |
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]
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/722976147/buildlog_ubuntu-jammy-amd64.squid_5.9-0ubuntu0.22.04.1~ppa1_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. |
|
| 2024-04-10 19:52:40 |
Sergio Durigan Junior |
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]
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/722976147/buildlog_ubuntu-jammy-amd64.squid_5.9-0ubuntu0.22.04.1~ppa1_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. |
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/722976147/buildlog_ubuntu-jammy-amd64.squid_5.9-0ubuntu0.22.04.1~ppa1_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. |
|
| 2024-04-11 18:04:30 |
Sergio Durigan Junior |
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/722976147/buildlog_ubuntu-jammy-amd64.squid_5.9-0ubuntu0.22.04.1~ppa1_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. |
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. |
|
| 2024-04-15 15:19:31 |
Sergio Durigan Junior |
squid (Ubuntu Jammy): status |
Triaged |
In Progress |
|
| 2024-04-26 09:14:07 |
Timo Aaltonen |
squid (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2024-04-26 09:14:08 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2024-04-26 09:14:10 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2024-04-26 09:14:13 |
Timo Aaltonen |
tags |
needs-mre-backport server-todo |
needs-mre-backport server-todo verification-needed verification-needed-jammy |
|
| 2024-05-08 15:13:59 |
Sergio Durigan Junior |
tags |
needs-mre-backport server-todo verification-needed verification-needed-jammy |
needs-mre-backport server-todo verification-done verification-done-jammy |
|
| 2024-07-03 01:52:57 |
Bryce Harrington |
tags |
needs-mre-backport server-todo verification-done verification-done-jammy |
needs-mre-backport verification-done verification-done-jammy |
|
| 2024-07-04 20:12:15 |
Launchpad Janitor |
squid (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2024-07-04 20:12:19 |
Andreas Hasenack |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2024-07-04 20:12:29 |
Andreas Hasenack |
squid (Ubuntu): status |
New |
Invalid |
|
