ubuntu-389-directory-server team mailing list archive

[Brian Murray <brian@xxxxxxxxxx>]

Hello Jon, or anyone else affected,

Accepted 389-ds-base into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/389-ds-
base/1.2.10.4-0ubuntu3.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: 389-ds-base (Ubuntu Precise)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
389 Directory Server, which is subscribed to 389-ds-base in Ubuntu.
https://bugs.launchpad.net/bugs/1022718

Title:
  Non-interactive install of package fails

Status in “389-ds-base” package in Ubuntu:
  Fix Released
Status in “389-ds-base” source package in Precise:
  Fix Committed
Status in “389-ds-base” package in Debian:
  Fix Released

Bug description:
  [Impact]

  non-interactive installations of 389-ds-base fail

  [Test Case]

  try to install the package noninteractively

  [Regression Potential]

  none, the bug is caused by old packaging leftovers that should be
  removed

  --

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/1022718/+subscriptions