The triaging is not correct here. The problem is that on this system
someone has manually created a clamav user as a non-system user. That
(correctly) causes the postinst to fail because it can't correct the
situation. The user needs to do so.
The call in the postinst is:
adduser --system
DpkgTerminalLog.txt shows:
Configurando samba4 (4.0.0~alpha18.dfsg1-4ubuntu2) ...
Unknown parameter encountered: max log size
Ignoring unknown parameter max log size
...
Unknown parameter encountered: guest ok
Ignoring unknown parameter guest ok
/var/lib/dpkg/info/samba4.postinst: 14:
reading clamav-base.postinst, it seems that on new install, it tries to add
user.
It does not check if the user exists first.
So this is either expected failure, in order to avoid re-using an unexpected
ID, or clamav should not create the user if it already exists.
I think it should not create the user if it already exists. I'll look
at improving this in the next upload to Debian.
** Changed in: clamav (Ubuntu)
Assignee: (unassigned) = Scott Kitterman (kitterman)
--
You received this bug notification because you are a member of Ubuntu
Server Team,
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/1015414
Title:
package clamav-base 0.97.3+dfsg-2.1ubuntu1 failed to install/upgrade:
sub-processo script post-installation instalado
