Comment 12 for bug 1780944

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
      -O2 and that triggers a format-truncation error on pcon.cc. See
      See https://bugs.squid-cache.org/show_bug.cgi?id=4875
    - d/t/upstream-test-suite: drop the sed line, since patch
      0003-installed-binary-for-debian-ci.patch is doing this work now.
      (https://salsa.debian.org/squid-team/squid/commit/ad4372b444ba8b1587839)

 -- Andreas Hasenack <email address hidden> Thu, 16 Aug 2018 12:33:17 -0300