[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

How to handle daemon-not-running bugs of debhelper compat level 11?

On Wed, 27 Mar 2019 20:12:00 +0000 Niels Thykier <niels@thykier.net> wrote:

> Related note (with my RT hat on): Please defer debhelper compat bumps
> for anything targeting buster as it is not considered a "minimal change".

Dear Release Team,

I recently realised that #887904 (dh_installsystemd will unmask services
*after* an attempt to start them) affects pacemaker (and probably every
other debhelper compat level 11 daemons with a native systemd unit).
The symptom:

apt install pacemeker => pacemaker is running, good;
apt remove  pacemaker => pacemaker is not running, good;
apt install pacemaker => pacemaker is still not running, NOT good;
service pacemaker start => pacemaker is running, good.

I think this is a bug, although probably not a policy violation.  What
should one do for buster?
1. Don't care,
2. try to fix this somehow on compat level 11 (how?),
3. switch to compat level 12 against the month-old request quoted above?

Please advise.

Ps.: This is a general question in the first place, though I'm asking it
in the context of security bug #927714: bundle the compat bump or not?
I'm planning to bundle two packaging fixups in the upload regardless.

announced a new upstream security release (2.0.2) as well, and
https://github.com/ClusterLabs/pacemaker/blob/2.0/ChangeLog looks short
enough, but the internal code reorganisation was significant, so that'll
go to experimental first.

Reply to: