| 2024-07-17 01:25:21 |
Bryce Harrington |
bug |
|
|
added bug |
| 2024-07-17 01:25:22 |
Bryce Harrington |
squid (Ubuntu): importance |
Undecided |
Wishlist |
|
| 2024-07-17 01:25:22 |
Bryce Harrington |
squid (Ubuntu): milestone |
|
ubuntu-24.08 |
|
| 2024-07-17 01:25:24 |
Bryce Harrington |
nominated for series |
|
Ubuntu Focal |
|
| 2024-07-17 01:25:25 |
Bryce Harrington |
bug task added |
|
squid (Ubuntu Focal) |
|
| 2024-07-17 01:25:26 |
Bryce Harrington |
nominated for series |
|
Ubuntu Jammy |
|
| 2024-07-17 01:25:27 |
Bryce Harrington |
bug task added |
|
squid (Ubuntu Jammy) |
|
| 2024-07-17 01:25:28 |
Bryce Harrington |
nominated for series |
|
Ubuntu Noble |
|
| 2024-07-17 01:25:29 |
Bryce Harrington |
bug task added |
|
squid (Ubuntu Noble) |
|
| 2024-07-17 01:25:31 |
Bryce Harrington |
bug |
|
|
added subscriber Canonical Server |
| 2024-08-28 15:34:05 |
Athos Ribeiro |
squid (Ubuntu): assignee |
|
Athos Ribeiro (athos-ribeiro) |
|
| 2024-08-28 15:34:11 |
Athos Ribeiro |
squid (Ubuntu Focal): assignee |
|
Athos Ribeiro (athos-ribeiro) |
|
| 2024-08-28 15:34:14 |
Athos Ribeiro |
squid (Ubuntu Jammy): assignee |
|
Athos Ribeiro (athos-ribeiro) |
|
| 2024-08-28 15:34:16 |
Athos Ribeiro |
squid (Ubuntu Noble): assignee |
|
Athos Ribeiro (athos-ribeiro) |
|
| 2024-08-28 15:56:13 |
Athos Ribeiro |
squid (Ubuntu Focal): status |
New |
Won't Fix |
|
| 2024-08-28 15:56:45 |
Athos Ribeiro |
squid (Ubuntu Jammy): status |
New |
Invalid |
|
| 2024-09-02 21:14:52 |
Athos Ribeiro |
description |
Backport squid to focal, jammy and noble once the update for oracular has been completed.
<List exact versions being upgraded from and to for each release>
[Impact]
TBD
<List bug links to former cases of SRU backports for this package>[Major Changes]
TBD
[Test Plan]
<Link to wiki SRU backport 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, ...>
|
Apart from the oracular update, which will not require a FFe since there are no features being introduced here (see the upstream changes section below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
https://www.squid-cache.org/Versions/v6/squid-6.10-RELEASENOTES.html
The only relevant hunk in a diff from version 6.6 to 6.10 for the upstream "Changelog" file in the root directory of the source package is
-<P>No ./configure options have been changed.</P>
+<DT><B>--disable-esi</B><DD>
+<P>The ESI feature is now disabled by default.
+Use <EM>--enable-esi</EM> if needed.</P>
Which, if applied, would introduce a feature/behavior change here. However, this we already have an "--enable-esi" entry in d/rules in the current noble (and oracualar) versions.
The complete set of changes together with a comprehensive changelog is available at https://github.com/squid-cache/squid/compare/SQUID_6_6..SQUID_6_10.
[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-09-08 23:34:25 |
Athos Ribeiro |
description |
Apart from the oracular update, which will not require a FFe since there are no features being introduced here (see the upstream changes section below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
https://www.squid-cache.org/Versions/v6/squid-6.10-RELEASENOTES.html
The only relevant hunk in a diff from version 6.6 to 6.10 for the upstream "Changelog" file in the root directory of the source package is
-<P>No ./configure options have been changed.</P>
+<DT><B>--disable-esi</B><DD>
+<P>The ESI feature is now disabled by default.
+Use <EM>--enable-esi</EM> if needed.</P>
Which, if applied, would introduce a feature/behavior change here. However, this we already have an "--enable-esi" entry in d/rules in the current noble (and oracualar) versions.
The complete set of changes together with a comprehensive changelog is available at https://github.com/squid-cache/squid/compare/SQUID_6_6..SQUID_6_10.
[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. |
Apart from the oracular update, which will not require a FFe since there are no features being introduced here (see the upstream changes section below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
https://www.squid-cache.org/Versions/v6/squid-6.10-RELEASENOTES.html
The only relevant hunk in a diff from version 6.6 to 6.10 for the upstream "Changelog" file in the root directory of the source package is
-<P>No ./configure options have been changed.</P>
+<DT><B>--disable-esi</B><DD>
+<P>The ESI feature is now disabled by default.
+Use <EM>--enable-esi</EM> if needed.</P>
Which, if applied, would introduce a feature/behavior change here. However, this we already have an "--enable-esi" entry in d/rules in the current noble (and oracualar) versions.
The complete set of changes together with a comprehensive changelog is available at https://github.com/squid-cache/squid/compare/SQUID_6_6..SQUID_6_10.
[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]
No CVEs are being addressed this time (the ones fixed in between 6.6 and 6.10 are already fixed in noble's security pocket). Therefore, this should go through the updates pockets.
TODO: list previous MREs for this package, if any. |
|
| 2024-09-08 23:45:20 |
Athos Ribeiro |
summary |
Backport of squid for focal, jammy and noble |
Upstream microrelease 6.10 |
|
| 2024-09-08 23:49:38 |
Athos Ribeiro |
description |
Apart from the oracular update, which will not require a FFe since there are no features being introduced here (see the upstream changes section below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
https://www.squid-cache.org/Versions/v6/squid-6.10-RELEASENOTES.html
The only relevant hunk in a diff from version 6.6 to 6.10 for the upstream "Changelog" file in the root directory of the source package is
-<P>No ./configure options have been changed.</P>
+<DT><B>--disable-esi</B><DD>
+<P>The ESI feature is now disabled by default.
+Use <EM>--enable-esi</EM> if needed.</P>
Which, if applied, would introduce a feature/behavior change here. However, this we already have an "--enable-esi" entry in d/rules in the current noble (and oracualar) versions.
The complete set of changes together with a comprehensive changelog is available at https://github.com/squid-cache/squid/compare/SQUID_6_6..SQUID_6_10.
[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]
No CVEs are being addressed this time (the ones fixed in between 6.6 and 6.10 are already fixed in noble's security pocket). Therefore, this should go through the updates pockets.
TODO: list previous MREs for this package, if any. |
Apart from the oracular update, which will not require a FFe since there are no features being introduced here (see the upstream changes section below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
https://www.squid-cache.org/Versions/v6/squid-6.10-RELEASENOTES.html
The only relevant hunk in a diff from version 6.6 to 6.10 for the upstream "Changelog" file in the root directory of the source package is
-<P>No ./configure options have been changed.</P>
+<DT><B>--disable-esi</B><DD>
+<P>The ESI feature is now disabled by default.
+Use <EM>--enable-esi</EM> if needed.</P>
Which, if applied, would introduce a feature/behavior change here. However, this we already have an "--enable-esi" entry in d/rules in the current noble (and oracualar) versions.
The complete set of changes together with a comprehensive changelog is available at https://github.com/squid-cache/squid/compare/SQUID_6_6..SQUID_6_10.
[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]
No CVEs are being addressed this time (the ones fixed in between 6.6 and 6.10 are already fixed in noble's security pocket). Therefore, this should go through the updates pockets.
Previous squid MREs:
- https://pad.lv/2013423
- https://pad.lv/2040470 |
|
| 2024-09-09 14:22:59 |
Renan Rodrigo |
merge proposal linked |
|
https://code.launchpad.net/~renanrodrigo/ubuntu/+source/squid/+git/squid/+merge/472902 |
|
| 2024-09-09 14:23:11 |
Renan Rodrigo |
squid (Ubuntu): assignee |
Athos Ribeiro (athos-ribeiro) |
Renan Rodrigo (renanrodrigo) |
|
| 2024-09-10 00:34:13 |
Athos Ribeiro |
squid (Ubuntu): status |
New |
In Progress |
|
| 2024-09-10 00:36:10 |
Athos Ribeiro |
merge proposal linked |
|
https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/squid/+git/squid/+merge/472937 |
|
| 2024-09-10 00:41:18 |
Athos Ribeiro |
description |
Apart from the oracular update, which will not require a FFe since there are no features being introduced here (see the upstream changes section below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
https://www.squid-cache.org/Versions/v6/squid-6.10-RELEASENOTES.html
The only relevant hunk in a diff from version 6.6 to 6.10 for the upstream "Changelog" file in the root directory of the source package is
-<P>No ./configure options have been changed.</P>
+<DT><B>--disable-esi</B><DD>
+<P>The ESI feature is now disabled by default.
+Use <EM>--enable-esi</EM> if needed.</P>
Which, if applied, would introduce a feature/behavior change here. However, this we already have an "--enable-esi" entry in d/rules in the current noble (and oracualar) versions.
The complete set of changes together with a comprehensive changelog is available at https://github.com/squid-cache/squid/compare/SQUID_6_6..SQUID_6_10.
[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]
No CVEs are being addressed this time (the ones fixed in between 6.6 and 6.10 are already fixed in noble's security pocket). Therefore, this should go through the updates pockets.
Previous squid MREs:
- https://pad.lv/2013423
- https://pad.lv/2040470 |
Apart from the oracular update, which will not require a FFe since there are no features being introduced here (see the upstream changes section below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
https://www.squid-cache.org/Versions/v6/squid-6.10-RELEASENOTES.html
The only relevant hunk in a diff from version 6.6 to 6.10 for the upstream "release notes" file (doc/release-notes/release-6.html) is
-<P>No ./configure options have been changed.</P>
+<DT><B>--disable-esi</B><DD>
+<P>The ESI feature is now disabled by default.
+Use <EM>--enable-esi</EM> if needed.</P>
Which, if applied, would introduce a feature/behavior change here. However, this we already have an "--enable-esi" entry in d/rules in the current noble (and oracualar) versions.
The complete set of changes together with a comprehensive changelog is available at https://github.com/squid-cache/squid/compare/SQUID_6_6..SQUID_6_10.
[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]
No CVEs are being addressed this time (the ones fixed in between 6.6 and 6.10 are already fixed in noble's security pocket). Therefore, this should go through the updates pockets.
Previous squid MREs:
- https://pad.lv/2013423
- https://pad.lv/2040470 |
|
| 2024-09-10 10:25:02 |
Renan Rodrigo |
description |
Apart from the oracular update, which will not require a FFe since there are no features being introduced here (see the upstream changes section below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
https://www.squid-cache.org/Versions/v6/squid-6.10-RELEASENOTES.html
The only relevant hunk in a diff from version 6.6 to 6.10 for the upstream "release notes" file (doc/release-notes/release-6.html) is
-<P>No ./configure options have been changed.</P>
+<DT><B>--disable-esi</B><DD>
+<P>The ESI feature is now disabled by default.
+Use <EM>--enable-esi</EM> if needed.</P>
Which, if applied, would introduce a feature/behavior change here. However, this we already have an "--enable-esi" entry in d/rules in the current noble (and oracualar) versions.
The complete set of changes together with a comprehensive changelog is available at https://github.com/squid-cache/squid/compare/SQUID_6_6..SQUID_6_10.
[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]
No CVEs are being addressed this time (the ones fixed in between 6.6 and 6.10 are already fixed in noble's security pocket). Therefore, this should go through the updates pockets.
Previous squid MREs:
- https://pad.lv/2013423
- https://pad.lv/2040470 |
Apart from the oracular update, which will not require a FFe since there are no features being introduced here (see the upstream changes section below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
https://www.squid-cache.org/Versions/v6/squid-6.10-RELEASENOTES.html
The only relevant hunk in a diff from version 6.9 to 6.10 for the upstream "release notes" file (doc/release-notes/release-6.html) is
-<P>No ./configure options have been changed.</P>
+<DT><B>--disable-esi</B><DD>
+<P>The ESI feature is now disabled by default.
+Use <EM>--enable-esi</EM> if needed.</P>
Which, if applied, would introduce a feature/behavior change here. However, this we already have an "--enable-esi" entry in d/rules in the current noble (and oracualar) versions.
The complete set of changes together with a comprehensive changelog is available at https://github.com/squid-cache/squid/compare/SQUID_6_6..SQUID_6_10.
[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]
No CVEs are being addressed this time (the ones fixed in between 6.6 and 6.10 are already fixed in noble's security pocket). Therefore, this should go through the updates pockets.
Previous squid MREs:
- https://pad.lv/2013423
- https://pad.lv/2040470 |
|
| 2024-09-10 10:25:23 |
Renan Rodrigo |
description |
Apart from the oracular update, which will not require a FFe since there are no features being introduced here (see the upstream changes section below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
https://www.squid-cache.org/Versions/v6/squid-6.10-RELEASENOTES.html
The only relevant hunk in a diff from version 6.9 to 6.10 for the upstream "release notes" file (doc/release-notes/release-6.html) is
-<P>No ./configure options have been changed.</P>
+<DT><B>--disable-esi</B><DD>
+<P>The ESI feature is now disabled by default.
+Use <EM>--enable-esi</EM> if needed.</P>
Which, if applied, would introduce a feature/behavior change here. However, this we already have an "--enable-esi" entry in d/rules in the current noble (and oracualar) versions.
The complete set of changes together with a comprehensive changelog is available at https://github.com/squid-cache/squid/compare/SQUID_6_6..SQUID_6_10.
[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]
No CVEs are being addressed this time (the ones fixed in between 6.6 and 6.10 are already fixed in noble's security pocket). Therefore, this should go through the updates pockets.
Previous squid MREs:
- https://pad.lv/2013423
- https://pad.lv/2040470 |
Apart from the oracular update, which will not require a FFe since there are no features being introduced here (see the upstream changes section below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
https://www.squid-cache.org/Versions/v6/squid-6.10-RELEASENOTES.html
The only relevant hunk in a diff from version 6.6 to 6.10 for the upstream "release notes" file (doc/release-notes/release-6.html) is
-<P>No ./configure options have been changed.</P>
+<DT><B>--disable-esi</B><DD>
+<P>The ESI feature is now disabled by default.
+Use <EM>--enable-esi</EM> if needed.</P>
Which, if applied, would introduce a feature/behavior change here. However, this we already have an "--enable-esi" entry in d/rules in the current noble (and oracualar) versions.
The complete set of changes together with a comprehensive changelog is available at https://github.com/squid-cache/squid/compare/SQUID_6_6..SQUID_6_10.
[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]
No CVEs are being addressed this time (the ones fixed in between 6.6 and 6.10 are already fixed in noble's security pocket). Therefore, this should go through the updates pockets.
Previous squid MREs:
- https://pad.lv/2013423
- https://pad.lv/2040470 |
|
| 2024-09-10 10:26:17 |
Renan Rodrigo |
description |
Apart from the oracular update, which will not require a FFe since there are no features being introduced here (see the upstream changes section below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
https://www.squid-cache.org/Versions/v6/squid-6.10-RELEASENOTES.html
The only relevant hunk in a diff from version 6.6 to 6.10 for the upstream "release notes" file (doc/release-notes/release-6.html) is
-<P>No ./configure options have been changed.</P>
+<DT><B>--disable-esi</B><DD>
+<P>The ESI feature is now disabled by default.
+Use <EM>--enable-esi</EM> if needed.</P>
Which, if applied, would introduce a feature/behavior change here. However, this we already have an "--enable-esi" entry in d/rules in the current noble (and oracualar) versions.
The complete set of changes together with a comprehensive changelog is available at https://github.com/squid-cache/squid/compare/SQUID_6_6..SQUID_6_10.
[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]
No CVEs are being addressed this time (the ones fixed in between 6.6 and 6.10 are already fixed in noble's security pocket). Therefore, this should go through the updates pockets.
Previous squid MREs:
- https://pad.lv/2013423
- https://pad.lv/2040470 |
Apart from the oracular update, which will not require a FFe since there are no features being introduced here (see the upstream changes section below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
https://www.squid-cache.org/Versions/v6/squid-6.10-RELEASENOTES.html
The only relevant hunk in a diff from version 6.9 to 6.10 for the upstream "release notes" file (doc/release-notes/release-6.html) is
-<P>No ./configure options have been changed.</P>
+<DT><B>--disable-esi</B><DD>
+<P>The ESI feature is now disabled by default.
+Use <EM>--enable-esi</EM> if needed.</P>
Which, if applied, would introduce a feature/behavior change here. However, this we already have an "--enable-esi" entry in d/rules in the current noble (and oracualar) versions.
The complete set of changes together with a comprehensive changelog is available at https://github.com/squid-cache/squid/compare/SQUID_6_9..SQUID_6_10.
[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]
No CVEs are being addressed this time (the ones fixed in between 6.6 and 6.10 are already fixed in noble's security pocket). Therefore, this should go through the updates pockets.
Previous squid MREs:
- https://pad.lv/2013423
- https://pad.lv/2040470 |
|
| 2024-09-10 10:42:05 |
Renan Rodrigo |
description |
Apart from the oracular update, which will not require a FFe since there are no features being introduced here (see the upstream changes section below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
https://www.squid-cache.org/Versions/v6/squid-6.10-RELEASENOTES.html
The only relevant hunk in a diff from version 6.9 to 6.10 for the upstream "release notes" file (doc/release-notes/release-6.html) is
-<P>No ./configure options have been changed.</P>
+<DT><B>--disable-esi</B><DD>
+<P>The ESI feature is now disabled by default.
+Use <EM>--enable-esi</EM> if needed.</P>
Which, if applied, would introduce a feature/behavior change here. However, this we already have an "--enable-esi" entry in d/rules in the current noble (and oracualar) versions.
The complete set of changes together with a comprehensive changelog is available at https://github.com/squid-cache/squid/compare/SQUID_6_9..SQUID_6_10.
[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]
No CVEs are being addressed this time (the ones fixed in between 6.6 and 6.10 are already fixed in noble's security pocket). Therefore, this should go through the updates pockets.
Previous squid MREs:
- https://pad.lv/2013423
- https://pad.lv/2040470 |
Apart from the oracular update, which will not require a FFe since there are no features being introduced here (see the upstream changes section below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
https://www.squid-cache.org/Versions/v6/squid-6.10-RELEASENOTES.html
The only relevant hunk in a diff from version 6.6 to 6.10 for the upstream "release notes" file (doc/release-notes/release-6.html) is
-<P>No ./configure options have been changed.</P>
+<DT><B>--disable-esi</B><DD>
+<P>The ESI feature is now disabled by default.
+Use <EM>--enable-esi</EM> if needed.</P>
Which, if applied, would introduce a feature/behavior change here. However, this we already have an "--enable-esi" entry in d/rules in the current noble (and oracualar) versions.
The complete set of changes together with a comprehensive changelog is available at https://github.com/squid-cache/squid/compare/SQUID_6_6..SQUID_6_10.
[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]
No CVEs are being addressed this time (the ones fixed in between 6.6 and 6.10 are already fixed in noble's security pocket). Therefore, this should go through the updates pockets.
Previous squid MREs:
- https://pad.lv/2013423
- https://pad.lv/2040470 |
|
| 2024-09-12 20:07:55 |
Athos Ribeiro |
description |
Apart from the oracular update, which will not require a FFe since there are no features being introduced here (see the upstream changes section below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
https://www.squid-cache.org/Versions/v6/squid-6.10-RELEASENOTES.html
The only relevant hunk in a diff from version 6.6 to 6.10 for the upstream "release notes" file (doc/release-notes/release-6.html) is
-<P>No ./configure options have been changed.</P>
+<DT><B>--disable-esi</B><DD>
+<P>The ESI feature is now disabled by default.
+Use <EM>--enable-esi</EM> if needed.</P>
Which, if applied, would introduce a feature/behavior change here. However, this we already have an "--enable-esi" entry in d/rules in the current noble (and oracualar) versions.
The complete set of changes together with a comprehensive changelog is available at https://github.com/squid-cache/squid/compare/SQUID_6_6..SQUID_6_10.
[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]
No CVEs are being addressed this time (the ones fixed in between 6.6 and 6.10 are already fixed in noble's security pocket). Therefore, this should go through the updates pockets.
Previous squid MREs:
- https://pad.lv/2013423
- https://pad.lv/2040470 |
Apart from the oracular update, which will not require a FFe since there are no features being introduced here (see the upstream changes section below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
https://www.squid-cache.org/Versions/v6/squid-6.10-RELEASENOTES.html
The only relevant hunk in a diff from version 6.6 to 6.10 for the upstream "release notes" file (doc/release-notes/release-6.html) is
-<P>No ./configure options have been changed.</P>
+<DT><B>--disable-esi</B><DD>
+<P>The ESI feature is now disabled by default.
+Use <EM>--enable-esi</EM> if needed.</P>
Which, if applied, would introduce a feature/behavior change here. However, this we already have an "--enable-esi" entry in d/rules in the current noble (and oracualar) versions.
The complete set of changes together with a comprehensive changelog is available at https://github.com/squid-cache/squid/compare/SQUID_6_6..SQUID_6_10.
[Test Plan]
Link the build log containing all tests being executed: https://launchpadlibrarian.net/748286177/buildlog_ubuntu-noble-amd64.squid_6.10-0ubuntu0.24.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).
Results of local autopkgtest run against all the new Squid versions being uploaded here:
- squid/6.10-0ubuntu0.24.04.1~ppa1
+ ✅ squid on noble for amd64 @ 10.09.24 14:02:43 Log️ 🗒️
+ ✅ squid on noble for arm64 @ 10.09.24 14:06:07 Log️ 🗒️
+ ✅ squid on noble for ppc64el @ 10.09.24 14:05:36 Log️ 🗒️
+ ✅ squid on noble for s390x @ 10.09.24 14:01:18 Log️ 🗒️
ran with ppa-dev-tools for build in https://launchpad.net/~athos-ribeiro/+archive/ubuntu/squid-mre/+packages
[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.
[Other Info]
No CVEs are being addressed this time (the ones fixed in between 6.6 and 6.10 are already fixed in noble's security pocket). Therefore, this should go through the updates pockets.
Previous squid MREs:
- https://pad.lv/2013423
- https://pad.lv/2040470 |
|
| 2024-09-12 20:08:08 |
Athos Ribeiro |
squid (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2024-09-12 20:08:13 |
Athos Ribeiro |
squid (Ubuntu Noble): status |
New |
In Progress |
|
| 2024-09-12 20:08:28 |
Athos Ribeiro |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2024-09-13 03:49:10 |
Launchpad Janitor |
squid (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2024-09-13 03:49:10 |
Launchpad Janitor |
cve linked |
|
2024-37894 |
|
