Looking at upstream, there's not a ton that I worry about missing in noble. The only one is a fix for a memory leak that I think would make sense to cherrypick[0].
Otherwise, I don't think it is worth the risk to upgrade the package this late in the cycle, and instead effort would be better utilized to work on helping debian for the next ubuntu release on things such as the service/socket systemd interactions that I've put on hold[1]. Any objections to not doing the merge for this cycle? Or should I prioritize testing the package and try to squeeze it in? [0] - https://github.com/openSUSE/multipath-tools/commit/b10a8fbd9da42f81687516cd345fd1ceeb60921f [1] - https://salsa.debian.org/linux-blocks-team/multipath-tools/-/merge_requests/14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040360 Title: [FFE ] Merge multipath-tools from Debian unstable for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/2040360/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
