When upgrading to trusty, this error has hit me, too.
After some investigation I figured that there are some flaws in
/usr/sbin/update-squidgard, which is called during the configure phase
on install/update.
1) update-squidguard calls a "su - proxy squidguard ..." at the end to rebuild
the database.
This fails with
Rebuild SquidGuard database - this can take a while.
This account is currently not available.
That's no surprise because the "proxy" user was created previously with
proxy:x:13:13:proxy:/bin:/usr/sbin/nologin
The invocation of "su" checks for a valid shell, which "/usr/sbin/nologin"
isn't.
2) update-squidguard tries to restart squid at the very end, but actually fails
to do so, because it checks for appropriate init.d files.
With squid3 (3.3.8-1ubuntu6) there aren't any, because this package is already
upstart enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313200
Title:
package squidguard 1.5-2 failed to install/upgrade: ErrorMessage:
subprocess installed post-installation script returned error exit
status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squidguard/+bug/1313200/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
