Bug#680351: 389-ds-base: fails to install: 10 389-ds-base/setup doesn't exist
Package: 389-ds-base Version: 1.2.11.7-2 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 389-ds-base. (Reading database ... 9713 files and directories currently installed.) Unpacking 389-ds-base (from .../389-ds-base_1.2.11.7-2_amd64.deb) ... Setting up 389-ds-base (1.2.11.7-2) ... dpkg: error processing 389-ds-base (--configure): subprocess installed post-installation script returned error exit status 10 Errors were encountered while processing: 389-ds-base Since that is not really helpful, I'm setting some more debug options: # DEBCONF_DEBUG=developer dpkg --configure --pending Setting up 389-ds-base (1.2.11.7-2) ... debconf (developer): frontend started debconf (developer): frontend running, package name is 389-ds-base debconf (developer): starting /var/lib/dpkg/info/389-ds-base.config configure debconf (developer): -- INPUT high 389-ds-base/setup debconf (developer): -- 10 389-ds-base/setup doesn't exist dpkg: error processing 389-ds-base (--configure): subprocess installed post-installation script returned error exit status 10 Errors were encountered while processing: 389-ds-base This looks like a non-existing debconf template gets used. cheers, Andreas 389-ds-base_1.2.11.7-2.log.gz Description: GNU Zip compressed data
Bug#680351: [Pkg-fedora-ds-maintainers] Bug#680351: 389-ds-base: fails to install: 10 389-ds-base/setup doesn't exist
On 05.07.2012 12:23, Andreas Beckmann wrote: Package: 389-ds-base Version: 1.2.11.7-2 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 389-ds-base. (Reading database ... 9713 files and directories currently installed.) Unpacking 389-ds-base (from .../389-ds-base_1.2.11.7-2_amd64.deb) ... Setting up 389-ds-base (1.2.11.7-2) ... dpkg: error processing 389-ds-base (--configure): subprocess installed post-installation script returned error exit status 10 Errors were encountered while processing: 389-ds-base Since that is not really helpful, I'm setting some more debug options: # DEBCONF_DEBUG=developer dpkg --configure --pending Setting up 389-ds-base (1.2.11.7-2) ... debconf (developer): frontend started debconf (developer): frontend running, package name is 389-ds-base debconf (developer): starting /var/lib/dpkg/info/389-ds-base.config configure debconf (developer): -- INPUT high 389-ds-base/setup debconf (developer): -- 10 389-ds-base/setup doesn't exist dpkg: error processing 389-ds-base (--configure): subprocess installed post-installation script returned error exit status 10 Errors were encountered while processing: 389-ds-base This looks like a non-existing debconf template gets used. ugh, fixed in git.. thanks. Verified with piuparts this time :) -- t -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
