pacemaker 2.0 (and its dependencies) will first need merged into Eoan.
I've added a separate task for that from the Disco backport task.
Regarding backporting pacemaker 2.0 to Disco via SRU, the amount of
change from pacemaker 1.1.18 to 2.0.1 is not insignificant, and includes
not only new features (over a dozen changes) but also around a dozen
deprecated features that get dropped in 2.0. SRU policy likes to see
minimal or no chance of regressions, and because of these changes it
might be challenging to guarantee that in this case.
However, you're right that pcs lists a Breaks for pacemaker < 2.0, which
creates this awkward situation. I'm not sure what the best way to
address that might be.
** Changed in: pacemaker (Ubuntu Eoan)
Status: Incomplete => Confirmed
** Changed in: pacemaker (Ubuntu Disco)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1825992
Title:
Upgrade to version 2.0 to satisfy pcs dependency
Status in pacemaker package in Ubuntu:
Confirmed
Status in pacemaker source package in Disco:
New
Status in pacemaker source package in Eoan:
Confirmed
Bug description:
Is there a way we could upgrade the version to 2.0? The pcs package
requires a version of pacemaker that is greater than or equal to 2.0,
and there is already a debian version packaged for v2. Installing the
Ubuntu package for pcs will delete the pacemaker package as there is
no version of pacemaker that is greater than 2.0.
I can help with build/testing and packaging for 2.0 based on the
existing debian deb if needed.
https://pkgs.org/download/pacemaker
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1825992/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help : https://help.launchpad.net/ListHelp
