Package: vlock Version: 2.2.2-6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts
Hi, during a test with piuparts I noticed your package failed to install, remove (but not purge), and install again. Before the second installation the package is in config-files-remaining state. The configuration is remaining from the last version that was successfully configured - which is the same version that is going to be installed again. Like a plain failure on initial install this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): 0m27.8s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpvoT99A', 'apt-get', '-y', 'install', 'vlock=2.2.2-6'] 0m29.0s DUMP: Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: vlock debconf: delaying package configuration, since apt-utils is not installed 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/36.7 kB of archives. After this operation, 120 kB of additional disk space will be used. dpkg: unrecoverable fatal error, aborting: unknown group 'vlock' in statoverride file E: Sub-process /usr/bin/dpkg returned an error code (2) 0m29.0s ERROR: Command failed (status=100): ['chroot', '/tmp/piupartss/tmpvoT99A', 'apt-get', '-y', 'install', 'vlock=2.2.2-6'] cheers, Andreas
vlock_2.2.2-6.log.gz
Description: application/gzip