This is arguably a reasonable combination (although with slight differences) of 'FTBFS' and 'Autopkgtest failures' (i.e., 'for successful build/test run') acceptable per SRU policy (included below), thus should not need staging.
And even though this SRU (openvswitch) is directed at fixing/preventing a build-time error in another, upcoming SRU (ovs), it does address run-time issues in openvswitch (see patch). This run-time issue/fix has build-time tests added in this SRU, so tests are covered (added that to 'Test Plan' section); e.g., the patch context lines show 'ofproto-dpif - continuation with patch port' which is tested in the build log of current version in noble-proposed: `1251: ofproto-dpif - continuation with patch port ok` For reference, the patch adds the build-time test: `ofproto-dpif - continuation with meters` ... """ Other safe cases [0] FTBFS(Fails To Build From Source) can also be considered. [...] Usually those bugs should only be SRUed in conjunction with another bug fix. Autopkgtest failures should also normally be SRUed only in conjunction with other high-priority fixes affecting users at runtime, optionally by staging them. As an exception, when an SRU of one package will introduce a regression in the autopkgtests of another package, it is appropriate to do an autopkgtest-only SRU of the other package. Staging low priority uploads [1] SRUs for bugs which do not affect users at runtime are inappropriate to force users to apply. There is a cost to our users (and our mirror network) for downloading updates of packages, which should be balanced against the utility of the update to the user downloading it. However, if such an update otherwise complies with SRU policy, it can be staged to be bundled with a future SRU or security update. """ [0] https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases [1] https://wiki.ubuntu.com/StableReleaseUpdates#Staging_low_priority_uploads [2] https://launchpadlibrarian.net/727042740/buildlog_ubuntu-noble-amd64.openvswitch_3.3.0-1ubuntu2_BUILDING.txt.gz ** Description changed: [ Impact ] There is a bug in Open vSwitch which is required for successful build and test run for OVN 24.03.2. (Bug 2066908: [SRU] ovn 24.03.2 point release) [ Test plan ] - Build and test the OVN 24.03.2 package. + - Build and test the OVN 24.03.2 package. + - Check openvswitch build log for new test (must pass/'ok') + `ofproto-dpif - continuation with meters` [ Regression Potential ] Minimal, the fix has been available for some time upstream already and has been deemed safe to backport all the way to Open vSwitch 2.17 by the upstream maintainers. [ Other Info ] The bug has been fixed upstream, and there is a patch available for branch-3.3 [0]. 0: https://github.com/openvswitch/ovs/commit/c560f6ca3257dd3b64e01a4a244b02b90216858b ** Changed in: openvswitch (Ubuntu Noble) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066906 Title: [noble] Missing fix for continuations with associated metering. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2066906/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
