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.

** Summary changed:

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

** Description changed:

  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:
  [EMAIL PROTECTED]:/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.

-- 
[SRU] [can-not-install]  postinst failure
https://bugs.launchpad.net/bugs/90932
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to