merge pacemaker 2.1.6 from Debian unstable

Bug #2029288 reported by Athos Ribeiro
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pacemaker (Ubuntu)
Fix Released
Undecided
Athos Ribeiro

Bug Description

This would be a second merge for the mantic cycle.

Related branches

Changed in pacemaker (Ubuntu):
assignee: nobody → Athos Ribeiro (athos-ribeiro)
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pacemaker - 2.1.6-1ubuntu1

---------------
pacemaker (2.1.6-1ubuntu1) mantic; urgency=medium

  * Merge with Debian unstable (LP: #2029288). 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
  * Drop changes:
    - d/p/Fix-output_and_clear_error.patch: Fix FTBFS erros due to
      glib's GError misuse.
      [Fixed in 2.1.6]

 -- Athos Ribeiro <email address hidden> Tue, 01 Aug 2023 17:42:01 -0300

Changed in pacemaker (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.