daemons/execd/pacemaker_remote.in | 4 4 + 0 - 0 !
etc/init.d/pacemaker.in | 4 4 + 0 - 0 !
2 files changed, 8 insertions(+)

 enable redirecting /etc/init.d/$script calls to systemd

daemons/execd/pacemaker_remote.in | 4 2 + 2 - 0 !
etc/init.d/pacemaker.in | 4 2 + 2 - 0 !
2 files changed, 4 insertions(+), 4 deletions(-)

 enable the init scripts on multi-user runlevels

Upstream does not find this a good idea (see 5b5acab vs fc11a46 and also
https://github.com/ClusterLabs/pacemaker/pull/656), but Debian runs
installed daemons by default.

agents/alerts/Makefile.am | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 alerts: make the scripts executable
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Signed-off-by: Ferenc Wgner <wferi@niif.hu>

cts/cts-exec.in | 2 1 + 1 - 0 !
lib/pacemaker/pcmk_sched_primitive.c | 4 2 + 2 - 0 !
2 files changed, 3 insertions(+), 3 deletions(-)

 fix typos: resouce -> resource

agents/stonith/fence_legacy.in | 9 0 + 9 - 0 !
mk/man.mk | 12 7 + 5 - 0 !
python/pacemaker/buildoptions.py.in | 8 0 + 8 - 0 !
3 files changed, 7 insertions(+), 22 deletions(-)

 remove references to the build directory

These break reproducibility.  Running programs from the source
directory can be solved by setting environment variables.

cts/cts-attrd.in | 10 0 + 10 - 0 !
cts/cts-cli.in | 8 0 + 8 - 0 !
cts/cts-exec.in | 10 0 + 10 - 0 !
cts/cts-fencing.in | 10 0 + 10 - 0 !
cts/cts-regression.in | 10 0 + 10 - 0 !
cts/cts-scheduler.in | 10 0 + 10 - 0 !
cts/support/cts-support.in | 10 0 + 10 - 0 !
7 files changed, 68 deletions(-)

 cts: do not capture the build directory

python/pacemaker/Makefile.am | 3 3 + 0 - 0 !
python/tests/Makefile.am | 3 3 + 0 - 0 !
2 files changed, 6 insertions(+)

 python: clean up the __pycache__ directories

agents/stonith/Makefile.am | 2 2 + 0 - 0 !
doc/sphinx/Makefile.am | 1 1 + 0 - 0 !
python/Makefile.am | 2 1 + 1 - 0 !
3 files changed, 4 insertions(+), 1 deletion(-)

 find libcrmcommon without embedding the build path

The Sphinx call was particularly insidious, because its failure did
not abort the build.