Package: adequate Version: 0.4.3 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...):
previous commands:
apt-get install adequate
dpkg -r adequate
so the package is in config-files-remaining state
0m13.9s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpYdaMcQ',
'eatmydata', 'apt-get', '-y', 'install', 'adequate=0.4.3']
0m14.1s DUMP:
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
adequate
/bin/sh: 1: adequate: not found
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/12.4 kB of archives.
After this operation, 93.2 kB of additional disk space will be used.
E: Sub-process adequate --user nobody --apt-preinst returned an error code
(127)
E: Failure running script adequate --user nobody --apt-preinst
0m14.1s ERROR: Command failed (status=100): ['chroot',
'/tmp/piupartss/tmpYdaMcQ', 'eatmydata', 'apt-get', '-y', 'install',
'adequate=0.4.3']
Do you install some apt hook conffile that does in-adequately check whether
adequate is actually installed?
cheers,
Andreas
adequate_0.4.3.log.gz
Description: GNU Zip compressed data
