Package: watcher-common
Version: 0.30.0-3
Severity: serious
Usertags: piuparts


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...):

1m32.3s DEBUG: Starting command: ['chroot', 
'/srv/', 'apt-get', '-y', 'install', 
1m45.6s DUMP: 
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following NEW packages will be installed:
  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/38.7 kB of archives.
  After this operation, 167 kB of additional disk space will be used.
  Selecting previously unselected package watcher-common.
  (Reading database ... 
(Reading database ... 19500 files and directories currently installed.)
  Preparing to unpack .../watcher-common_0.30.0-3_all.deb ...
  Unpacking watcher-common (0.30.0-3) ...
  Setting up watcher-common (0.30.0-3) ...
  mkdir: cannot create directory '/var/cache/watcher': File exists
  E: Sub-process /usr/bin/dpkg returned an error code (1)
1m45.6s ERROR: Command failed (status=100): ['chroot', 
'/srv/', 'apt-get', '-y', 'install', 



Attachment: watcher-common_0.30.0-3.log.gz
Description: application/gzip

Reply via email to