Comment 0 for bug 1022718

I'm using the Quantal version of this package, back-ported (myself) to a Precise system, however the same bug is present on Precise.

I'm attempting to install this package using Puppet, which uses the equivalent of the following command to do so:

  DEBIAN_FRONTEND=noninteractive APT_LISTBUGS_FRONTEND=none APT_LISTCHANGES_FRONTEND=none /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install 389-ds-base

This results in the following error:

dpkg: error processing 389-ds-base (--configure):
 subprocess installed post-installation script returned error exit status 30
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Errors were encountered while processing:
 389-ds-base
E: Sub-process /usr/bin/dpkg returned an error code (1)

When run under DEBCONF_DEBUG=developer, I get

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): --> 30 question skipped
dpkg: error processing 389-ds-base (--configure):
 subprocess installed post-installation script returned error exit status 30
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Errors were encountered while processing:
 389-ds-base
E: Sub-process /usr/bin/dpkg returned an error code (1)

As far as I can tell, the problem exists because the debconf key is specified as high priority, even though all it does is display a note, making this a packaging issue.