There is currently no mechanism for a package maintainer script to
automatically detect that you added additional ports and apply this
change to the new configuration file in a major upstream release update.
If you have a customised configuration file, then when you upgrade you
should get a
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu, since you had previously modified squid.conf and these
customisations needed to be updated in the upgrade.
You can find pointers to get help for this sort of problem here:
If misconfiguration means adding additional ports to the config file,
then you are right. This is another reason for switching to another
distribution. Ubuntu is no distribution for productive environments!!!
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: squid3 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
Removing the lines and dpkg-reconfigure squid worked!
Thx!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1370602
Title:
package squid3 3.3.8-1ubuntu6.1 failed to install/upgrade:
I had the same error.
The manager, localhost and to_localhost definitions are built-in in later
squid-versions...
Simply restart your system after the relase-upgrade and remove the following
lines from your squid.conf:
acl manager proto cache_object
acl localhost src 127.0.0.1/32 ::1
acl
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1370602
Title:
package squid3 3.3.8-1ubuntu6.1 failed to install/upgrade:
Unterprozess
