Update to upstream version '4.13'
with Debian dir ca75b8b9f61ec058deb3afb4856a2849a3ef3a39

Update to upstream version '4.12'
with Debian dir 492c2165388d1fc50217af2013cca33f464543ca

Squid cleanup postinst

See merge request squid-team/squid!13

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.

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.

Squid /run dir and apparmor fixes

See merge request squid-team/squid!12

When apparmor is enabled and the squid profile is enforced, we must
make sure that the daemon will be able to access the
/run/system/notify file (because squid's systemd service file type is
"notify").

Debian Policy states that /run is normally cleared at boot time, and
therefore packages must not install files/directories under /run.
Init scripts should be taught to dynamically handle /run instead.

This change uses systemd's RuntimeDirectory and RuntimeDirectoryMode
directives when starting the squid service in order to guarantee that
/run/squid/ will be created with the correct permission.  This has the
added benefit of deleting the directory when the service is stopped.

Group needs write permissin for systemd.

Apparmor profile needs to permit read/write/lock

Release