> b) This is a new package, and it also produces a new binary: meson-1.7. It > has appropriate > conflicts/replaces with bin:meson. But what happens to it on a > release-upgrade to noble++? Plucky and > later have bin:meson at 1.7.0.
Sorry, that's wrong. src:meson-1.7 is producing a bin:meson-1.7 binary. So that is not a concern. UPDATE: actually, I'm not sure. What happens if you have a noble system with bin:meson-1.7 installed, and release upgrade to plucky, which has bin:meson at version 1.7? My concern is getting stuck on bin:meson-1.7 from noble. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2126037 Title: Backport packages for 24.04.4 HWE stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/2126037/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
