squid 4.12-1ubuntu1 source package in Ubuntu

Changelog

squid (4.12-1ubuntu1) groovy; urgency=medium

  * Merge with Debian unstable. Remaining changes:
    - d/usr.sbin.squid: Add sections for maas-proxy, squid-deb-proxy
      squidguard
    - d/p/90-cf.data.ubuntu.patch: Add an example refresh pattern
      for debs.
    - Use snakeoil certificates:
      + d/control: add ssl-cert to dependencies
      + d/p/99-ubuntu-ssl-cert-snakeoil.patch: add a note about ssl
        to the default config file
  * Dropped changes, not needed anymore:
    - 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 https://bugs.squid-cache.org/show_bug.cgi?id=4875.
      [ Dropped because the build now passes on ppc64el ]
  * Dropped changes, incorporated by Debian:
    - Don't restart squid by hand on postinst script
      + d/squid.postinst: When installing/upgrading squid, the service
        is being restarted manually in the postinst script, which can
        break installations that have the squid apparmor enabled because
        it will try to restart the service before reloading the apparmor
        profile.  There is no reason to restart squid manually, since the
        restart will be automatically performed later.
    - Drop conffile check for squid < 2.7
      + d/squid.postinst: squid 2.7 is long, long gone, so it should be
        safe to drop the postinst code to make sure that
        /etc/squid/squid.conf was properly upgraded.
    - d/tests/test-squid.py: Adjust 'pidfile' variable to reflect fact
      that we now store the pidfile under '/run/squid/'.
  * Added changes:
    - d/p/0007-WCCP-Fix-GCC-10-Wstringop-truncation-failures.patch:
      Fix GCC-10 build failure due to -Wstringop-truncation warning.

squid (4.12-1) unstable; urgency=high

  * Urgency high due to security fixes

  [ Sergio Durigan Junior <email address hidden> ]
  * Don't restart squid by hand on postinst script.
    When installing/upgrading squid, the service is being restarted
    manually in the postinst script, which can break installations that
    have the squid apparmor enabled because it will try to restart the
    service before reloading the apparmor profile.
    There is no reason to restart squid manually, since the restart will
    be automatically performed later.

  * Drop conffile check for squid < 2.7
    squid 2.7 is long, long gone, so it should be safe to drop the
    postinst code to make sure that /etc/squid/squid.conf was properly
    upgraded.

  * Fix 'pidfile' on d/t/tests-squid.py.
    The pidfile lives under '/run/squid/', not '/run/'. (Closes: #960327)

  [ Juri Grabowski <email address hidden> ]
  * add gbp.conf for squid

  * New upstream version 4.12
    - Fixes security issue SQUID-2020:5 (CVE-2020-14059)
    - Fixes security issue SQUID-2020:6 (CVE-2020-14058)
    - Fixes security issue SQUID-2020:7 (CVE-2020-15049)

  * remove 0004-upstream-bug5041.patch - Fixed in upstream

  [ Luigi Gangitano <email address hidden> ]

  * Move PID file to /run (Closes: #960819)

 -- Sergio Durigan Junior <email address hidden>  Mon, 10 Aug 2020 11:20:46 -0400