>From the Log:
Removing obsolete conffile /etc/squid3/msntauth.conf ...
Preserving user changes to /etc/squid/squid.conf (renamed from
stat: cannot stat '/var/spool/squid3': No such file or directory
chown: cannot access '/var/spool/squid3': No such file or directory
dpkg: error processing package squid (--configure):
subprocess installed post-installation script returned error exit status 1
it seems you formerly had a custom squid configuration that now fails to work.
The issue seems to be around "/var/spool/squid3"
Might that have been renamed to just squid as well?
Yeah I see that the new dir is "/var/spool/squid" now instead.
So this is a case where your local configuration is incompatible with the new
I'd recommend to change the config or system setup so they match against each
I wonder thou if the package upgrade should take care of those in a maintainer
I'd have some ideas, but then users could have done arbitrary things with their
/var/spool/squid3 so any postinst handling might be dangerous killing what an
admin had set up.
So I think this should stay as is.
In your case as said before I'd recommend adapting setup or config file.
Setting the bug to incomplete, please reopen if you think this is an
issue in the package itself or if the recommended workaround doesn't
** Changed in: squid3 (Ubuntu)
Status: New => Incomplete
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
package squid 3.5.12-1ubuntu7.2 failed to install%Fupgrade: subprocess
installed post-installation script returned error exit status 1
To manage notifications about this bug go to:
ubuntu-bugs mailing list