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

[Martin Pitt]

Ack, thanks Thomas! Well, hopefully the devel-permissions@ PPU thread
concludes soon, then I don't need to bother you any more.

** Summary changed:

- Please backport cockpit 333 into oracular/noble/jammy
+ [BPO] Please backport cockpit 333 into oracular/noble/jammy

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2099668

Title:
  [BPO] Please backport cockpit 333 into oracular/noble/jammy

Status in cockpit package in Ubuntu:
  Invalid
Status in cockpit source package in Jammy:
  Fix Committed
Status in cockpit source package in Noble:
  Fix Committed
Status in cockpit source package in Oracular:
  Fix Committed

Bug description:
  Cockpit has a standing backport approval since
  https://bugs.launchpad.net/xenial-backports/+bug/1686022 . For the
  last couple of years I have uploaded them myself, as I had been an
  Ubuntu core developer from ~ 2004 until a few months ago. I
  voluntarily left archive admin and core-dev teams as I haven't
  exercised these privileges in several years now, so they are just a
  potential danger.

  However, I didn't realize that with leaving core-dev I would also lose
  my upload permissions of cockpit (plus associated packages
  cockpit-{machines,podman} and hopefully soon cockpit-files).

  So let's try the sponsor approach for a while. We still test all
  cockpit upstream PRs on Ubuntu 22.04 LTS, 24.04 LTS, and the latest
  stable release (oracular at the moment), so please upload no-change
  backports of the current version (333) to backports.

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cockpit/+bug/2099668/+subscriptions