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 service is started by automatic
dh_helpers code, and that is why the package doesn't install.
389-admin.postinst
#!/bin/sh
set -e
# Automatically added by dh_systemd_enable
if deb-systemd-helper debian-installed dirsrv-admin.service; then
# This will only remove masks created by d-s-h on package removal.
deb-systemd-helper unmask dirsrv-admin.service >/dev/null || true
if deb-systemd-helper --quiet was-enabled dirsrv-admin.service; then
# Create new symlinks, if any.
deb-systemd-helper enable dirsrv-admin.service >/dev/null ||
true
fi
fi
Removing that automated code is one way. Let the user enable the service once
he has been set it up correctly. setup-ds-admin is as far as I know the command
to use for creating this config.
However, that is not expected behaviour in debian. The 'correct' fix would be
to pre-configure the service in a way that allows it to start sucesfully. I
don't know this software enough to make a judgment if that is feasible.
--
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 script returned error exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/389-admin/+bug/1652476/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
