This bug was fixed in the package pacemaker - 2.1.2-1ubuntu1
---------------
pacemaker (2.1.2-1ubuntu1) jammy; urgency=medium
* Merge with Debian unstable (LP: #1946885). Remaining changes:
- Make crmsh the default management tool for now (LP #1862947)
- d/control: make pacemaker binary recommend fence-agents-base
- d/control: make pacemaker-resource-agents depend on resource-agents-base.
And also suggest resource-agents-extra with non-curated agents.
- d/t/pacemaker: corosync uses uname -n to define the default node name.
Previously the default node name was hardcoded in the config file as
node1.
- d/rules: Fix FTBFS in ppc64el compiling with gcc10: Don't treat
format-overflow warnings as errors
* Dropped:
- d/rules: Forcibly switch from ftime to clock_gettime, since building
with ftime now results in deprecation errors
[in 2.1.2 by upstream]
-- Lucas Kanashiro <[email protected]> Thu, 02 Dec 2021 15:41:12
-0300
** Changed in: pacemaker (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946885
Title:
Merge pacemaker from Debian unstable for 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1946885/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
