Package: needrestart Version: 0.4-1 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...):
0m22.3s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpwc6DQn',
'apt-get', '-y', 'install', 'needrestart=0.4-1']
0m22.8s DUMP:
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
needrestart
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/10.9 kB of archives.
After this operation, 124 kB of additional disk space will be used.
/bin/bash: /usr/lib/needrestart/dpkg-status: No such file or directory
Selecting previously unselected package needrestart.
(Reading database ... 8301 files and directories currently installed.)
Preparing to unpack .../needrestart_0.4-1_all.deb ...
E: Sub-process /usr/bin/dpkg exited unexpectedly
0m22.8s ERROR: Command failed (status=100): ['chroot',
'/tmp/piupartss/tmpwc6DQn', 'apt-get', '-y', 'install', 'needrestart=0.4-1']
cheers,
Andreas
needrestart_0.4-1.log.gz
Description: GNU Zip compressed data
