> For my Firewall/caching server, replaced a failing HDD and installed > 16.04.1. All OK.
Good that this is ok again. > Ideally, Squid should have started with "Squid" as its file naming > convention and then there would have been no problem. I couldn't agree more, but still lack the time machine to change such things :-) > Now I was able to check my File server backup files to see if it was me or > Squid naming everything with "Squid3". I have the original Squid install > conf file (pre 16.04.1); its definitely been Squid that named the various > files with "Squid3" and not just "Squid" Yes in the past all was "squid3" names. On the update it tries to adapt and handle things to become just "squid" to be like any new install would be. My former assumption was that you already had some dir named yourself /var/spool/squid - without the "3". That would have broken the transition. As I said while the maintainer scripts could try to catch that the possible combinations are so manyfold that any fix usually introduces one more error :-/ Thank you a lot for your report and your detailed feedback. I'm happy that your setup works again. Given my expectation of fixes for "auto config updates" I'd keep the bug on incomplete to allow it to expire. If you think this is an issue that has to be "fixed" please reset it to new. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625569 Title: 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: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1625569/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
