[Bug 1652476] Re: package 389-admin 1.1.43-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

This bug was fixed in the package 389-admin - 1.1.46-2 --- 389-admin (1.1.46-2) unstable; urgency=medium * Don't bump compat to 10, breaks the order of autoreconf and applying patches. -- Timo Aaltonen Sat, 07 Oct 2017 08:04:20 +0300 ** Changed in:

[Bug 1652476] Re: package 389-admin 1.1.43-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

--no-start would leave it stopped on upgrade adm.conf example is indeed useless, I'll purge it.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652476 Title: package 389-admin 1.1.43-1 failed to

[Bug 1652476] Re: package 389-admin 1.1.43-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

This wasn't exactly the section of postinst that was causing the issue. I have a workaround for it in debian/rules: override_dh_installinit: dh_installinit --name dirsrv-admin -- defaults 15 85 vs override_dh_installinit: dh_installinit --name dirsrv-admin --no-start -- defaults 15 85 And a

[Bug 1652476] Re: package 389-admin 1.1.43-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

auto-configuring it is not possible because it needs a dirsrv instance around in order to work the fix is to use an error-handler for postinst like for 389-ds-base, then it would still fail to start the service of course but that would not fail the install ** Changed in: 389-admin (Ubuntu)

[Bug 1652476] Re: package 389-admin 1.1.43-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

I can confirm this bug on Zesty. As far as I understand the situation, the following is the case. The package leases the service in a un-configured state. There is no /etc/dirsrv/admin-serv/adm.conf and /var/log/dirsrv/admin-serv/ does not exist. This is why the service doesn't start. The

[Bug 1652476] Re: package 389-admin 1.1.43-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Same on Zesty. Installing 389-admin on a clean install doesn't work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652476 Title: package 389-admin 1.1.43-1 failed to install/upgrade: subprocess

[Bug 1652476] Re: package 389-admin 1.1.43-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: 389-admin (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652476 Title:

[Bug 1652476] Re: package 389-admin 1.1.43-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652476 Title: package 389-admin 1.1.43-1 failed to install/upgrade: subprocess installed post-installation