hope to get it fixst
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670410
Title:
package squid 3.5.12-1ubuntu7.3 failed to install/upgrade: subprocess
installed post-installation script returned
I just had this same issue occur with an upgrade from trusty to xenial.
Wouldn't even let me uninstall the squid package from the newly upgraded
system until I created the directory '/var/spool/squid3', then the
package worked and I could uninstall/reinstall.
Luckily it was in a virtual machine,
[Expired for squid3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: squid3 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670410
On 07.03.2017 [01:03:43 -], Stephen Parry wrote:
> No, but I may have had problems with the rename during a previous
> upgrade. When I looked at the server there was quite a mess of squid
> versus squid3 named directories. What is the release history for squid
> versus squid3 naming?
No, but I may have had problems with the rename during a previous
upgrade. When I looked at the server there was quite a mess of squid
versus squid3 named directories. What is the release history for squid
versus squid3 naming?
On 07/03/2017 00:49, Nish Aravamudan wrote:
> I believe the
I believe the package scripts are attemping to handle the default case,
where /var/spool/squid3 was renamed to /var/spool/squid. Did you use a
custom directory?
** Changed in: squid3 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670410
Title:
package squid 3.5.12-1ubuntu7.3 failed to install/upgrade: subprocess
installed
