[SRU] [can-not-install] postinst failure

[Michael Vogt]

Binary package hint: ldap2dns

Found while doing a install test:

Setting up ldap2dns (0.3.1-3) ...
/

ldap2dns has been installed.

To set up services, please see the documentation at:
http://ldap2dns.tiscover.com/ or
/usr/share/doc/ldap2dns/README.txt.gz

To Configure ldap2dns for use with djbdns:
Run ldap2tinydns-conf in your tinydns directory, something like:
root@host:/var/tinydns# ldap2tinydns-conf

Then tell svscan about the new service:
ln -s /var/tinydns/ldap2tinydns /var/lib/svscan

dpkg: error processing ldap2dns (--configure):
 subprocess post-installation script returned error exit status 128
Errors were encountered while processing:
 ldap2dns
E: Sub-process /usr/bin/dpkg returned an error code (1)

It should not fail but handle the situation gracefully

TEST CASE:
This issues shows up during postinst phase, the only step required to reproduce this is install ldap2dns package.
Fix is straightforward: just upgrade to the new version and exit status 128 will no longer appear.

[Michael Vogt (mvo)]

Binary package hint: ldap2dns

Found while doing a install test:

Setting up ldap2dns (0.3.1-3) ...
/

ldap2dns has been installed.

To set up services, please see the documentation at:
http://ldap2dns.tiscover.com/ or
/usr/share/doc/ldap2dns/README.txt.gz

To Configure ldap2dns for use with djbdns:
Run ldap2tinydns-conf in your tinydns directory, something like:
root@host:/var/tinydns# ldap2tinydns-conf

Then tell svscan about the new service:
ln -s /var/tinydns/ldap2tinydns /var/lib/svscan

dpkg: error processing ldap2dns (--configure):
 subprocess post-installation script returned error exit status 128
Errors were encountered while processing:
 ldap2dns
E: Sub-process /usr/bin/dpkg returned an error code (1)

It should not fail but handle the situation gracefully

[Carlos Perelló Marín (carlos)]

6 months later, the problem is still there.

[Luca Falavigna (dktrkranz)]

Attached debdiff should fix this bug.

[Maurizio Moriconi (bugman)]

The fix from Luca works. This is the log from hardy tarball:

http://pastebin.ubuntu.com/1281/

[Luca Falavigna (dktrkranz)]

ldap2dns (0.3.1-3ubuntu1) hardy; urgency=low

  * Do not include /usr/share/debconf/confmodule in postinst (LP: #90932)
  * Update Maintainer field in debian/control

 -- Luca Falavigna <email address hidden> Wed, 24 Oct 2007 13:31:32 +0200

[Luca Falavigna (dktrkranz)]

Debdiff for gutsy-proposed.

[Luca Falavigna (dktrkranz)]

Debdiff for feisty-proposed.

[Luca Falavigna (dktrkranz)]

Debdiff for edgy-proposed.

[Luca Falavigna (dktrkranz)]

Dapper version is fine for me.

[Luca Falavigna (dktrkranz)]

Even if versioning should be correct, a more elegant way to achieve the same reseluts is provided by using release numbers as part of the version:
0.3.1-3ubuntu0.7.10 for Gutsy
0.3.1-3ubuntu0.7.04 for Feisty
0.3.1-3ubuntu0.6.10 for Edgy

This approach has been already accepted for bug #131946.

[Luca Falavigna (dktrkranz)]

Tags: patch

Attached patch, taken against Ubuntu version, should fix this issue.
Thank you.

[Luca Falavigna (dktrkranz)]

tags 333448 + patch
tags 374454 + patch
tags 374723 + patch
thanks

[Luca Falavigna (dktrkranz)]

Uploaded to gutsy-proposed using 0.3.1-3ubuntu0.7.10 as version.
Uploaded to feisty-proposed using 0.3.1-3ubuntu0.7.04 as version.
Uploaded to edgy-proposed using 0.3.1-3ubuntu0.6.10 as version.

[Martin Pitt (pitti)]

Accepted into edgy/feisty/gutsy-proposed, please test.

[Andrea Colangelo (warp10)]

0.3.1-3ubuntu0.7.10 installs fine for me.

[Daniel Schwitzgebel (schwitzd)]

0.3.1-3ubuntu0.7.04 work for me

[Daniel Schwitzgebel (schwitzd)]

0.3.1-3ubuntu0.6.10 and 0.3.1-3ubuntu0.7.10
work for me

[Salvatore Palma (palma-salvatore)]

Works for me on Edgy, Feisty and Gutsy.

[Luca Falavigna (dktrkranz)]

Minimum aging period of seven days elapsed and two persons confimed fix is good.
Tagging verification-motu-done as per http://wiki.ubuntu.com/StableReleaseUpdates (previous policy)

[Martin Pitt (pitti)]

Copied to edgy/feisty-/gutsy-updates.