Hello Andreas, long time no see! Thanks for replying. I need to figure out a new workflow for this, so thanks for the guidance.
> - BPO bug template[1] See https://bugs.launchpad.net/xenial-backports/+bug/1686022 This has been good enough for many years, and the approval shouldn't evaporate just because I dropped my core-dev status. > - confirmation it builds and autopkgtests, if any, were run (a PPA would suffice, with autopkgtests triggered on it) I created a PPA: https://launchpad.net/~pitti/+archive/ubuntu/cockpit- backports/+packages The auto-generated debdiffs aren't useful for sponsoring (wrong base version and changelog upload target differs between backports and PPAs). I don't know how to trigger autopkgtests on a PPA, but they do run/pass locally. > - I don't know if ~ubuntu-backporters is still a thing, but that wiki page says they should be subscribed I subscribed them. It looks like there isn't much of a backports team left -- e.g. https://launchpad.net/lucid-backports still exists, but no https://launchpad.net/noble-backports or https://launchpad.net/jammy- backports > - the actual diff. It sounds like it is just boilerplate, come up with a version, changelog entry, point at the bug, etc. But if that is done, then it really becomes sponsoring, otherwise I will be the backporter, and that's not the case :) Right! I attached them. ** Changed in: cockpit (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2099668 Title: Please backport cockpit 333 into oracular/noble/jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cockpit/+bug/2099668/+subscriptions -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
