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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825992
Title:
Upgrade to version 2.0 to satisfy pcs dependency
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1825992/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
