...using the upstream patches overhauling toolchain hardening (Fedora
natively uses -fstack-protector-strong so this effectively relaxed
stack protection is the only effect as hardened flags are already
used by default:
https://fedoraproject.org/wiki/Changes/Harden_All_Packages)
Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
... for full details, see included ChangeLog file or
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.15
- Adapt spec file more akin to upstream version:
. move xml schema files + PCMK-MIB.txt (81ef956), logrotate configuration
file (ce576cf; drop it from -remote package as well), attrd_updater
(aff80ae), the normal resource agents (1fc7287), and common directories
under /var/lib/pacemaker (3492794) from main package under -cli
. simplify docdir build parameter passing and drop as of now
redundant chmod invocations (e91769e)
... Pacemaker-1.1.15-rc3, for full details, see included ChangeLog file or
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.15-rc3
- Drop fence_pcmk (incl. man page) from the package (no use where no
CMAN)
- Drop license macro emulation for cases when not supported natively
(several recent Fedora releases do not need that)
...Pacemaker-1.1.15-rc1, for full details, see included ChangeLog file or
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.15-rc1
- Adapt spec file more akin to upstream version (also to reflect recent
changes like ability to built explicitly without Publican-based docs)
Note that patch disabling original built-in notification mechanism is
no longer needed as the same is achieved natively in the sources,
and there's brand new, more convoluted (and allegedly compatible)
implementation of the same.
...beyond Pacemaker-1.1.14
(commit 5a6cdd1), but restore old-style notifications to the state at
Pacemaker-1.1.14 point release (disabled)
- Definitely get rid of Corsync v1 (Flatiron) hypothetical support
- Remove some of the spec file cruft, not required for years
(BuildRoot, AutoReqProv, "clean" scriptlet, etc.) and adapt the file
per https://github.com/ClusterLabs/pacemaker/pull/965
... introduced with Fedora 23 Mass Rebuild.
It will likely happen again as the incrementing script, rpmdev-bumpspec,
doesn't account for "integer will be yielded from the macro expansion"
(not that it can do it in any simple way, and even if it could,
propagation of the increment back to the origin is pure sci-fi now).
Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
