For Resolute I think it would be reasonable to do the 2.6 -> universe, 5.0 -> main switch, but I understand timing is tight.
Uploading a Mir package that drops the port to libxml++-5.0 for Resolute would be easy. Alternatively, demoting libmirwayland-bin and libmirwayland-dev to universe would be acceptable. ** Description changed: libxml++-5.0 is a source-rename + new upstream version of libxml++2.6. Upstream releases multiple API-incompatible versions of libxml++; the deprecated 2.6 API currently in Ubuntu main, 3.0, 4.0, and 5.0. These are parallel-installable. Debian is seeking to move users off libxml++2.6, and as a part of that the Mir package in Debian has migrated to libxml++-5.0, and now syncd to Ubuntu. Mir is the only rdepend of libxml++2.6 in main; we should demote libxml++2.6 to universe and bring libxml++-5.0 to main. A diff of the 2.6 and 5.0 source packages shows no changes other than 2.6 -> 5.0 renamings, watch file updates, etc. The source code diff between the 2.6 the 5.0 packages is largely Glib::ustring -> ustring renames and trivial C++ idiom updates (adding - noexcept, std::move(), converting enum to enum class, etc). + noexcept, std::move(), converting enum to enum class, etc). There are + some additional APIs, in parallel to some existing APIs being marked + deprecated, but this is no more than what you might expect from a new + upstream version; it is very substantially the same code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2146982 Title: [MIR] libxml++-5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml++-5.0/+bug/2146982/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
