Merge Pacemaker from unstable for t64 changes
Bug #2056077 reported by
Athos Ribeiro
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pacemaker (Ubuntu) |
Fix Released
|
Undecided
|
Athos Ribeiro | ||
Bug Description
The only changes will be the t64 ones. Hence, it should be OK to merge this with no FFe.
Related branches
~athos-ribeiro/ubuntu/+source/pacemaker:merge-lp2056077-noble
Merged
into
ubuntu/+source/pacemaker:debian/sid
at
revision 4b22d2ab766a8b1f8e25f3a4edb37cf8c1ae10e5
- Canonical Server packageset reviewers: Pending requested
- Canonical Server Reporter: Pending requested
- git-ubuntu import: Pending requested
-
Diff: 905 lines (+676/-6)4 files modifieddebian/changelog (+659/-0)
debian/control (+10/-5)
debian/rules (+6/-0)
debian/tests/pacemaker (+1/-1)
| Changed in pacemaker (Ubuntu): | |
| assignee: | nobody → Athos Ribeiro (athos-ribeiro) |
| status: | New → In Progress |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in pacemaker (Ubuntu): | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
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-
And also suggest resource-
- 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-
- d/control: make pacemaker-cli-utils depend on resource-
resource-
main (it also pulls in resource-
universe).
- d/control: depend on pcs and suggest crmsh
- Ignore test results on armhf for now
-- Gianfranco Costamagna <email address hidden> Tue, 26 Mar 2024 09:18:27 +0100