[Bug 2099668] Re: Please backport cockpit 333 into oracular/noble/jammy

2025-03-25 Thread Thomas Ward
** Changed in: cockpit (Ubuntu Jammy) Assignee: (unassigned) => Zixing Liu (liushuyu-011) ** Changed in: cockpit (Ubuntu Noble) Assignee: (unassigned) => Zixing Liu (liushuyu-011) ** Changed in: cockpit (Ubuntu Oracular) Assignee: (unassigned) => Zixing Liu (liushuyu-011) ** Chang

[Bug 2099668] Re: Please backport cockpit 333 into oracular/noble/jammy

2025-03-24 Thread Thomas Ward
** Changed in: cockpit (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: cockpit (Ubuntu Noble) Status: New => Fix Committed ** Changed in: cockpit (Ubuntu Oracular) Status: New => Fix Committed ** Changed in: cockpit (Ubuntu Jammy) Assignee: Zixing Liu (liushu

[Bug 2099668] Re: Please backport cockpit 333 into oracular/noble/jammy

2025-03-24 Thread Zixing Liu
** Also affects: cockpit (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: cockpit (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: cockpit (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification be

[Bug 2099668] Re: Please backport cockpit 333 into oracular/noble/jammy

2025-03-24 Thread Thomas Ward
also Martin, yes, there is a new BPO template *AND* bug prefix to use. I'll make an exception *this time* for it and just let it through once I upload/sponsor (had some Major Level Crap to deal with that took ultimate priority), but for *future* requests you should follow the template that Andreas

[Bug 2099668] Re: Please backport cockpit 333 into oracular/noble/jammy

2025-03-15 Thread Thomas Ward
Nope you did nothing bad, you were perfectly in the right. As I said, unless another sponsor gets to it I'll sponsor your uploads, though that kind of 'self-approves' which is fine since we have precedent to approve cockpit due to quality of uploads and need of the package. As for the developer u

[Bug 2099668] Re: Please backport cockpit 333 into oracular/noble/jammy

2025-03-15 Thread Martin Pitt
Thanks Thomas! Right, I'm aware of the 2023 changes, and there has indeed been some hubbub (like me continuing to self-approve while I shouldn't have any more). But as far as I understood, I followed the process since then -- uploading the backports and letting the backports team approve them from

[Bug 2099668] Re: Please backport cockpit 333 into oracular/noble/jammy

2025-03-15 Thread Thomas Ward
> - I don't know if ~ubuntu-backporters is still a thing, but that wiki page says they should be subscribed Andreas, the Backporters team is the people who now approve backports in the system. It is *no longer* the team that does uploads, testing, etc. as the entire backports process changed durin

[Bug 2099668] Re: Please backport cockpit 333 into oracular/noble/jammy

2025-03-15 Thread Thomas Ward
> 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 Martin, Circa 2023, the Backports process was **redesigned entirely**, an

[Bug 2099668] Re: Please backport cockpit 333 into oracular/noble/jammy

2025-03-15 Thread Martin Pitt
Re-subscribing ~ubuntu-sponsors, which was somehow unsubscribed. This should hopefully make it appear on http://sponsoring-reports.ubuntu.com/ . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2099668 T

[Bug 2099668] Re: Please backport cockpit 333 into oracular/noble/jammy

2025-02-22 Thread Martin Pitt
** Patch added: "oracular debdiff" https://bugs.launchpad.net/ubuntu/+source/cockpit/+bug/2099668/+attachment/5859385/+files/cockpit_oracular.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2

[Bug 2099668] Re: Please backport cockpit 333 into oracular/noble/jammy

2025-02-22 Thread Martin Pitt
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

[Bug 2099668] Re: Please backport cockpit 333 into oracular/noble/jammy

2025-02-22 Thread Martin Pitt
** Patch added: "jammy debdiff" https://bugs.launchpad.net/ubuntu/+source/cockpit/+bug/2099668/+attachment/5859383/+files/cockpit_jammy.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2099668

[Bug 2099668] Re: Please backport cockpit 333 into oracular/noble/jammy

2025-02-22 Thread Martin Pitt
** Patch added: "noble debdiff" https://bugs.launchpad.net/ubuntu/+source/cockpit/+bug/2099668/+attachment/5859384/+files/cockpit_noble.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2099668

[Bug 2099668] Re: Please backport cockpit 333 into oracular/noble/jammy

2025-02-21 Thread Andreas Hasenack
I'm reading https://wiki.ubuntu.com/UbuntuBackports, and it looks like some steps are missing: - BPO bug template[1] - confirmation it builds and autopkgtests, if any, were run (a PPA would suffice, with autopkgtests triggered on it) - I don't know if ~ubuntu-backporters is still a thing, but tha