On Thu, Feb 14, 2013 at 12:09:35AM +0000, brian m. carlson wrote: > On Thu, Feb 14, 2013 at 12:04:50AM +0000, Colin Watson wrote: > > I need the output with DEBCONF_DEBUG=developer set in the environment, > > please (generally useful for anything even speculatively > > debconf-related). > > Setting up man-db (2.6.3-3) ... > debconf (developer): frontend started > debconf (developer): frontend running, package name is man-db > debconf (developer): starting /var/lib/dpkg/info/man-db.config configure > 2.6.3-3 > debconf (developer): <-- VERSION 2.0 > debconf (developer): --> 0 2.0 > debconf (developer): <-- INPUT medium man-db/install-setuid > debconf (developer): --> 30 question skipped > dpkg: error processing man-db (--configure): > subprocess installed post-installation script returned error exit status 30 > Errors were encountered while processing: > man-db
Hm, and yet the code is: db_input medium man-db/install-setuid || true So there's no reason why this should cause a failure, and it should have carried on to GO. Time for bigger guns: could you run the whole thing under 'strace -f -s4096 -o man-db.trace' and attach the resulting man-db.trace file, please? Thanks, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
