[Debian-ha-maintainers] Pacemaker packaging
Ferenc Wagner
wferi at niif.hu
Fri Sep 11 14:39:49 UTC 2015
Hi,
I almost went through the packaging of Pacemaker 1.1.13. A couple of
questions arose:
1. Richard put in Lintian overrides like this:
# init.d scripts not registered with update-rc.d since other components are meant to start/stop pacemaker
# and friends at system boot
pacemaker-remote binary: script-in-etc-init.d-not-registered-via-update-rc.d
What are those "other components"? What happens under systemd?
2. Richard also put in Lintian overrides like this:
# False positive; is as intended by upstream
pkg-config-bad-directive
Richard, could you please point us to your communications with
upstream forming the base of the above comment? Declarations like
with_upstart=@SUPPORT_UPSTART@
with_systemd=@SUPPORT_SYSTEMD@
don't seem particularly useful to me.
3. Do we want to provide numbered dev packages, like liblrmd1-dev? I
don't think we want to support several API versions concurrently, so
I dropped the numbers from the dev package names for now.
4. Lintian is not happy about the init script for pacemaker_remote
providing pacemaker_remoted (note the final d). Should we just
remove the d and thus synchronize to pacemaker_remote.service?
5. I dropped the CTS stuff from here as well, just like from Corosync.
This made the pacemaker-dev (probably long misnamed) package
disappear with all the Python stuff, too. Objections?
More will come later, but let's start with the above...
--
Thanks,
Feri.
More information about the Debian-ha-maintainers
mailing list