Please provide Squid-4

[Amos Jeffries]

Debian is now providing Squid-4.1. Please update the Ubuntu packages.

This will resolve Ubuntu bug #1097032, bug #16669, bug #1793131, and bug #1416009.

UPDATE:: The v4.2 package now in Debian also contains a fix for bug #1103362.

[Hans Joachim Desserud (hjd)]

Thanks for reporting.

Looks like the squid source package was re-used (re-introced) for squid 4.1 (https://tracker.debian.org/pkg/squid), while recent releases has been in squid3. This would normally be synced automatically, except that the squid package was blacklisted in bug 900741 when squid3 was introduced. Subscribed archive admins to take a look at this and decide how they want to solve it.

(Also, it seems that squid3 had quite an Ubuntu-delta, so someone needs to take a look at what needs to be carried over, if anything.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Christian Ehrhardt  (paelzer)]

Thanks Amos for the ping, we will discuss in our standup today who could take a look at the merge.
4.x in Debian LGTM on the tracker page and bugs, do you know about any big things to be aware of when going 3.x->4.x?

[Amos Jeffries (yadi)]

The biggest thing will be that Ubuntu and Debian used different upgrade paths to move to 'squid' binary names. Most of the rest was pulled upstream for v4.

[Andreas Hasenack (ahasenack)]

Amos, I'm going to start submitting to Debian for consideration some of the changes we add to squid. Is using salsa Merge Requests ok with you for that purpose?

[Amos Jeffries (yadi)]

Sure.

[Amos Jeffries (yadi)]

Update FTR: 4.2 is now in the pipeline with the requested merges. Luigi informs me he intends to upload the new version to Debian sometime next week.

[Andreas Hasenack (ahasenack)]

Version 4.1 was uploaded on Aug 20th, and since then has been in the hands of the archive admins to decide:

https://launchpad.net/ubuntu/cosmic/+queue?queue_state=0&queue_text=squid

[Andreas Hasenack (ahasenack)]

I tried.

[Andreas Hasenack (ahasenack)]

This was accepted. I'm working on migrating away from squid-dbg to squid-dbgsym now, so a new upload will happen.

[Launchpad Janitor (janitor)]

This bug was fixed in the package squid - 4.1-1ubuntu1

---------------
squid (4.1-1ubuntu1) cosmic; urgency=medium

  * Merged with Debian unstable (LP: #1780944, LP: #1097032, LP: #16669).
    Remaining changes:
    - Use snakeoil certificates.
      [Updated to use the correct config setting names]
    - Add an example refresh pattern for debs.
      [Improved the refresh patterns based on the configuration from
       squid-deb-proxy package]
    - Add disabled by default AppArmor profile.
      [Updated to include the ssl_certs abstraction and suggestions on how to
       deal with the snakeoil private key and other keys in /etc/ssl.]
  * Dropped changes:
    - Add additional dep8 tests.
      [Adopted in 4.0.21-1~exp5, albeit a stripped down version]
    - Correct attribution and add explanatory note in d/NEWS.debian.
      [That particular upgrade path has happened long ago.]
    - Drop wrong short-circuiting of various invocations; we always want to
      call the debhelper block.
      [This was for the transitional squid3 package, and that transition has
       already happened.]
    - Revert "Set pidfile for systemd's sysv-generator" from Debian.
      [Not needed anymore since we have a native systemd service file
       and no longer rely on the generator.]
    - Enable autoreconf. This is no longer required for the security updates,
      but is needed for the seddery of test-suite/Makefile.am in
      d/t/upstream-test-suite.
      [Replaced by patch 0003-installed-binary-for-debian-ci.patch]
    - Adjust seddery for upstream test squid binary location.
      [sed no longer necessary since patch,
       0003-installed-binary-for-debian-ci.patch, will be dropped
       entirely.]
    - Drop Conflicts/Replaces of squid against squid3. In Ubuntu, the migration
      happened in Xenial, so no upgrade path still requires this code. This
      reduces upgrade ordering difficulty.
      [Again we have a migration, but this time from squid3 to squid, so we
      need this].
    - GCC7 FTBFS fixes (LP: #1712668):
      + d/rules: don't error when hitting the "deprecated" and
      "format-truncation" gcc7 warnings. Upstream 3.5.27 has fixes for these,
      but one in Format.cc that affects 32bit builds was deemed too intrusive
      for the 3.5 stable series and is only in squid 4.x
      [No longer needed with squid 4.x]
    - Do not force gcc-6
      [It was a temporary workaround in Debian that got dropped]
  * Added changes:
    - d/rules: enable cdbs parallel build
    - d/t/test-squid.py: fix apparmor profile filename
    - d/t/test-squid.py: fix the process name. The PID points at the parent.
    - d/t/upstream-test-suite: also make libmem.la, needed by the tests.
    - d/t/0003-installed-binary-for-debian-ci.patch: use the squid
      binary from the system, instead of the one from the source tree.
    - d/p/fix-uninitialized-var.patch: Workaround gcc's maybe-unitialized
      error in parse_time_t, triggered on ppc64el due to the build using -O3
      in that architecture.
    - d/rules: Add -Wno-format-truncation to CXXFLAGS as a workaround if
      building for ppc64el. On that arch, dpkg-buildflags sets -O3 instead of
    ...

[Amos Jeffries (yadi)]

Andreas: I'm working on migrating away from squid-dbg to squid-dbgsym now, so a new upload will happen.

FYI: instructions from the the designers of the *-dbgsym system were that the only thing source packages do is drop old *-dbg binary packages from d/control files. debhelper compat level 9+ automation does the upgrade logic. The instructions also stated that maintainers must not attempt any manual dependency or Conflict tricks. Is there something radically different for Ubuntu?

[Andreas Hasenack (ahasenack)]

> FYI: instructions from the the designers of the *-dbgsym system were that the only thing
> source packages do is drop old *-dbg binary packages from d/control files. debhelper
> compat level 9+ automation does the upgrade logic. The instructions also stated that
> maintainers must not attempt any manual dependency or Conflict tricks. Is there
> something radically different for Ubuntu?

I don't think it's that different in Ubuntu, but maybe britney is called/used a bit differently. What happened in the Ubuntu transition from -proposed to release was that squid-dbg-3.x (from squid3 src) had nowhere to upgrade to because the new debug package is called squid-dbgsym. Since the dbg package requires the exact squid-3.x package to be installed, it was holding the upgrade to squid-4.

It was sorted out by an archive admin by deleting squid-dbg (from squid3 src). What I should have done is prepared a temporary squid3 (src) upload that didn't produce squid-dbg. squid-dbg would then become an NBS (https://wiki.ubuntu.com/UbuntuDevelopment/NBS), be removed (not sure if automatically), and then the squid-4 migration would have happened automatically.

Using dh_strip's --dbgsym-migrate would probably not have helped, since a) that adds breaks/replaces to *all* dbgsym packages, not just the one replacing squid-dbg; and b) the dbgsym packages are in another repository, which I'm not sure britney considers. This attempt is what I meant with "a new upload will happen", but it wasn't necessary in the end.

[Amos Jeffries (yadi)]

Ah, okay. So repo related rather than a end-user problem. Thanks.