[Bug 1473691] Re: [FFe] squid: Update to latest upstream release (3.5)

[Ryan Harper]

As far as I can see, the entire versioned code block here is wrong, and
> you should *only* be restarting squid.
>
>
The block (without my addition) is from debian itself.  The original block
that's
present in debian:

update-rc.d squid defaults 30 >/dev/null

if test -d /etc/squid3 && dpkg --compare-versions "$2" lt '3.5'; then
    invoke-rc.d squid3 stop
    invoke-rc.d squid start
else
    invoke-rc.d squid restart
fi


However, this failed in our dist-upgrade from trusty scenario as the squid3
service file no longer
exists.  Reading your analysis; it seems that /etc/init.d/squid3 should
still be on disk;
but it was not.

In the dist-upgrade from trusty case; I believe we can just use the squid
restart.

In the upgrade from wily case, it's not clear to me why the
/etc/init.d/squid3 service
file would still be on disk when it wasn't when upgrading from trusty?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1473691

Title:
  [FFe] squid: Update to latest upstream release (3.5)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+subscriptions