Comment 18 for bug 1473691

Kick,

Thanks for the thorough upgrade test. I was able to recreate and debug the proposed package install script. It appears that the squid.postinst expects to find a /etc/init.d/squid3 service script if we also have an existing /etc/squid3 directory. However, in my testing, we do have the /etc/squid3, but the service script itself is called /etc/init.d/squid.

Manually fixing up this in the /var/lib/dpkg/info/squid.postinst and then running sudo apt-get -f install will allow squid upgrade to proposed levels complete successfully.

After the upgrade, I can confirm that squid-deb-proxy and squidGuard work correctly. I'm attaching a debdiff with a fix for this issue (we can check which init script is present and use that to stop/start the squid service after install).

I build squid from the merge branch from rabc's git repo with the attached debdiff, created a local ppa (including a copy of the libecap3 package) and performed an apt-get update && apt-get install squid which upgrades and installs successfully.

After this, squid, squid-deb-proxy and squidGuard all continue to work.