Hello Heitor, or anyone else affected,
Accepted openldap into cosmic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/openldap/2.4.46
+dfsg-5ubuntu1.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
** Tags added: sts-sponsor-ddstreet
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1821343
Title:
slapd process failure is not detected by systemd
Status in openldap package in Ubuntu:
** Patch added: "lp1821343-xenial.debdiff"
https://bugs.launchpad.net/debian/+source/openldap/+bug/1821343/+attachment/5254688/+files/lp1821343-xenial.debdiff
** Patch removed: "lp1821343-disco.debdiff"
** Patch added: "lp1821343-bionic.debdiff"
https://bugs.launchpad.net/debian/+source/openldap/+bug/1821343/+attachment/5254687/+files/lp1821343-bionic.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
** Patch added: "lp1821343-cosmic.debdiff"
https://bugs.launchpad.net/debian/+source/openldap/+bug/1821343/+attachment/5254686/+files/lp1821343-cosmic.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
This bug was fixed in the package openldap - 2.4.47+dfsg-3ubuntu2
---
openldap (2.4.47+dfsg-3ubuntu2) disco; urgency=medium
* Fix sysv-generator unit file by customizing parameters (LP: #1821343)
- d/slapd-remain-after-exit.conf: Override RemainAfterExit to allow
correct
Sponsored in disco.
** Changed in: openldap (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1821343
Title:
slapd process failure is not
debdiff v2 with fixed author information
** Patch added: "v2-lp1821343-disco.debdiff"
https://bugs.launchpad.net/debian/+source/openldap/+bug/1821343/+attachment/5254440/+files/v2-lp1821343-disco.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which
** Description changed:
[Impact]
Systemd service reports slapd as active, even though it may have failed
[Description]
The slapd package for OpenLDAP is shipped with a SysV-style init script
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service
by generating
@slashd I don't think we need anything special for systemd in the
debian/{control,rules} files, since we're not shipping full systemd
support with this. The slapd service is still handled by systemd-sysv-
generator(8), so there's no service units that we need to include or
activate in dh_systemd
** Changed in: openldap (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1821343
Title:
slapd process failure is not detected by systemd
Status in
[sts-sponsor note]
I am concerned about just adding the service unit, and not making your package
work
with systemd, especially for maintainer scripts (may break package upgrade...
would be good to test and add this to the [test case].
May I suggest you look at debian/control and debian/rules
** Bug watch added: Debian Bug tracker #926657
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926657
** Also affects: openldap (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926657
Importance: Unknown
Status: Unknown
** Patch added: "lp1821343-disco.debdiff"
I've been doing some research on how we could implement a proper systemd
unit file for slapd, and came up with interesting results.
There are a number of options that we can pass to the slapd service that will
give us lots of troubles on an "idiomatic" service file. To give some examples:
- The
The sysv init script does some funky parsing of configuration files that
might give us some trouble in an independent service file. I'll check if
we can't work around that and do away with the sysv init script
altogether, otherwise we might as well go with the drop-in override
since the new
> Do you need a whole service file for this? I thought you could achieve
> the same with a drop-in that just overrides the required keys
why would we do a SRU to hack in an override when it's just as easy to
do a SRU to actually create a correct service file so no override hack
is needed?
--
The attachment "debdiff for disco" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if
17 matches
Mail list logo
