It's because of this part: On Sat, Dec 11, 2010 at 06:48:34PM +0100, Lucas Nussbaum wrote: > > Preparing to replace snmpd 5.4.1~dfsg-12 (using > > .../snmpd_5.4.3~dfsg-1_amd64.deb) ... > > invoke-rc.d: policy-rc.d denied execution of stop. > > Unpacking replacement snmpd ...
resulting in: > > Setting up snmpd (5.4.3~dfsg-1) ... > > Installing new version of config file /etc/snmp/snmpd.conf ... > > Installing new version of config file /etc/init.d/snmpd ... > > Installing new version of config file /etc/default/snmpd ... > > userdel: user snmp is currently logged in > > /usr/sbin/deluser: `/usr/sbin/userdel snmp' returned error code 8. Exiting. > > dpkg: error processing snmpd (--configure): > > subprocess installed post-installation script returned error exit status 1 and it occurs because the package was upgraded in a chroot, where services are not allowed to stop or start. I tested it in the closest thing I have to a real machine, a Xen VM running i386 and the upgrade went perfectly. So, Lucas/RT: how much does it matter that a chroot fails because of the above error and can the bug be downgraded or closed? Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
signature.asc
Description: Digital signature
