This bug was fixed in the package pacemaker - 2.1.6-5ubuntu1
---------------
pacemaker (2.1.6-5ubuntu1) noble; urgency=medium
* Merge with Debian unstable (LP: #2056077). Remaining changes:
- 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
- d/control: make pacemaker-cli-utils depend on resource-agents-base
resource-agents is now a transitional package and it should not be in
main (it also pulls in resource-agents-extra which should be in
universe).
- d/control: depend on pcs and suggest crmsh
- Ignore test results on armhf for now
-- Gianfranco Costamagna <locutusofb...@debian.org> Tue, 26 Mar 2024
09:18:27 +0100
** 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/2056077
Title:
Merge Pacemaker from unstable for t64 changes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/2056077/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
