On Fri, Aug 17, 2018 at 10:59 AM Michael Biebl wrote:
> Am 17.08.2018 um 15:45 schrieb Michael Biebl:
> > Am 17.08.2018 um 15:37 schrieb Felipe Sateler:
> >
> >> Well, as long as we support the --skip-systemd-native, we can't drop the
> >> check :/
> >
> > I don't understand.
> > I thought the id
Am 17.08.2018 um 15:45 schrieb Michael Biebl:
> Am 17.08.2018 um 15:37 schrieb Felipe Sateler:
>
>> Well, as long as we support the --skip-systemd-native, we can't drop the
>> check :/
>
> I don't understand.
> I thought the idea was that dh_installsystemd would generate code to
> always pass --
Am 17.08.2018 um 15:37 schrieb Felipe Sateler:
> Well, as long as we support the --skip-systemd-native, we can't drop the
> check :/
I don't understand.
I thought the idea was that dh_installsystemd would generate code to
always pass --skip-systemd-native to invoke-rc.d?
--
Why is it that al
On Fri, Aug 17, 2018 at 10:33 AM Michael Biebl wrote:
> Am 17.08.2018 um 15:27 schrieb Felipe Sateler:
> > I'll revert the change to unbreak things soon. For the longer term,
> > maybe we can switch the check to
> >
> > /lib/systemd/systemd-sysv-install is-enabled $service
>
> I wouldn't bother i
Am 17.08.2018 um 15:27 schrieb Felipe Sateler:
> I'll revert the change to unbreak things soon. For the longer term,
> maybe we can switch the check to
>
> /lib/systemd/systemd-sysv-install is-enabled $service
I wouldn't bother introducing new code here and simply revert the change
to get the ol
Am 17.08.2018 um 15:24 schrieb Michael Biebl:
> The problem is, that dh_installsystemd enables the service *after* a
> start attempt has been made and
> systemctl is-enabled checks for the state of the native service unit.
>
> With dh_systemd_enable/start, the enable part was before the start.
> I
On Fri, Aug 17, 2018 at 10:24 AM Michael Biebl wrote:
> Am 17.08.2018 um 15:13 schrieb Felipe Sateler:
>
> > Hmm. Commit 6f95680ffc9b1605841eb7d3d8eb92c790e6c73a looks like the
> > culprit of the regression. But I'd like to understand why this happens.
> > Shouldn't update-rc.d have enabled the s
Am 17.08.2018 um 15:13 schrieb Felipe Sateler:
> Hmm. Commit 6f95680ffc9b1605841eb7d3d8eb92c790e6c73a looks like the
> culprit of the regression. But I'd like to understand why this happens.
> Shouldn't update-rc.d have enabled the service?
The lldpad or corosync package ship a native systemd uni
Am 17.08.2018 um 14:53 schrieb Valentin Vidic:
> On Fri, Aug 17, 2018 at 02:40:53PM +0200, Michael Biebl wrote:
>> Could you add "set -x" to /usr/sbin/invoke-rc.d, then re-install the
>> lldapd package and attach the output please.
>
> Sure, here it goes:
Thanks.
> + '[' -n 1 ']'
> + case ${ACTI
Control: severity -1 serious
On Fri, Aug 17, 2018 at 9:57 AM Valentin Vidic
wrote:
> On Fri, Aug 17, 2018 at 02:40:53PM +0200, Michael Biebl wrote:
> > Could you add "set -x" to /usr/sbin/invoke-rc.d, then re-install the
> > lldapd package and attach the output please.
>
> Sure, here it goes:
>
Processing control commands:
> severity -1 serious
Bug #906421 [init-system-helpers] invoke-rc.d: service not started from package
postinst anymore
Ignoring request to change severity of Bug 906421 to the same value.
--
906421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906421
Debian Bug
11 matches
Mail list logo
