Thanks for the review! After carefully looking at it again, I realise these commits like:
+ [ James Page ] + * d/gbp.conf: Create stable/2024.1 branch. + * d/gbp.conf, .launchpad.yaml: Sync from cloud-archive-tools for + caracal. were never actually released to the archive (still in UNRELEASED state). They are not part of the Watcher package themselves, but they're necessary for the Launchpad CI to function correctly on the branch. (Specifically, `.launchpad.yaml` needs `series: noble` instead of `series: devel` for the CI to work). That's why I incorporated these unreleased changes into my SRU, so that we now have a CI that passes (in stable/2024.1). But I agree the CI change there is actually not relevant to the Watcher package. So I make another branch to base my patch on top of the latest release as here: https://code.launchpad.net/~minhquangngoho/ubuntu/+source/watcher/+git/watcher/+ref/sru/lp2122551/noble where the corresponding debdiff is as attached. We can see that the CI now failed because some CI tests didn't pass. So I'm not sure whether we can still accept that, and which approach is the correct one... Please let me know, thanks! ** Patch added: "lp2122551_noble.demo.patch" https://bugs.launchpad.net/ubuntu/+source/watcher/+bug/2122551/+attachment/5926919/+files/lp2122551_noble.demo.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2122551 Title: [SRU] Backport feature for disabling migration to Noble and Plucky To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2122551/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
