Package: cinder-api
Version: 2:8.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package cinder-api.
  (Reading database ... 
(Reading database ... 22057 files and directories currently installed.)
  Preparing to unpack .../cinder-api_2%3a8.0.0-1_all.deb ...
  Unpacking cinder-api (2:8.0.0-1) ...
  Processing triggers for systemd (229-4) ...
  Setting up cinder-api (2:8.0.0-1) ...
  Will not register  endpoint this time (no user request for it).
  dpkg: error processing package cinder-api (--configure):
   subprocess installed post-installation script returned error exit status 10
  Processing triggers for systemd (229-4) ...
  Errors were encountered while processing:
   cinder-api

Is debconf involved here? piuparts runs with DEBIAN_FRONTEND=noninteractive

Similar problems in manila-api.


cheers,

Andreas

Attachment: cinder-api_2:8.0.0-1.log.gz
Description: application/gzip

Attachment: cinder-api_2:8.0.0-1.log.gz
Description: application/gzip

Reply via email to