© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
I did some upgrade testing on squid3 and there are some troubles apparently, I suspect and will try to modify debian/control to make it work (at least for upgrade from xenial to xenial-proposed).
-----
From precise to trusty with squid3 + squid-deb-proxy +squidguard (to check squid/squid3 renaming with ubuntu deltas)
Last week it was ok (3.3.8-1ubuntu6.4), now upgrading from squid(3) + squid-deb-proxy + squidguard is broken 3.3.8-1ubuntu6.6.
So it appears that I won't be able to test the full upgrade path from precise to xenial
Squidguard would have created some troubles as it was still using /etc/squid or /var/log/squid in precise version. It would have been interesting to test because of this, but last upstream broke release upgrade (last week it failed at starting service but continued upgrade, now it doesn't allow the upgrade to finish).
----
The following are my upgrade tests from trusty to xenial:
long story short: it fails.
I'm in a two stages update due to the squid package being in proposed, first stage from trusty to xenial current, and then to xenial-proposed.
I did the test two times one with installing with 'squid', and then with 'squid3'.
Both trusty setup were working squid3 + squidguard +squid-deb-proxy, and basic conf was apply to check.
First step upgrade caused squidguard to stop working (certainly some API related stuff), and squid-deb-proxy service seems broken, as I can run it by hand. squid3 was still working.
squid3 service is renamed to squid, we need to warn or take appropriate disposition as done in docker.io upgrade path.
Second step upgrade broke squid3. Logs/reference to follow.
----
squidguard and squid-deb-proxy are universe, but the upgrade path must be checked with them also to get some real-world upgrade path.
----
http://