I'd like some opinions on how to handle release-upgrades. Because dbus is generally pulled in through `Depends: default-dbus- system-bus | dbus-system-bus`, just changing the provider of default- dbus-system-bus won't cause upgraders to install dbus-broker.
server-cloud-minimal is the only seed explicitly listing `dbus`; the obvious thing to do there would be to change the seed to list `dbus- broker` instead. Should we add dbus-broker to a bunch of seeds? Should this be a release-upgrade quirk? Other options? It's important to note that removal of `dbus` is not necessary; just installing `dbus-broker` will take over in priority at runtime, and `dbus` will then become garbage-collectable unless other packages from universe still have an explicit dependency on it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015538 Title: [MIR] dbus-broker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2015538/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
