=== chris14_ is now known as chris14
=== chris14_ is now known as chris14
[03:07] <RAOF> Hm. oem-sutton-adelia-meta appears to be in a weird state of having source in universe and binaries in main.
[03:25] <vorlon> "oops"
[03:26] <vorlon> RAOF: fixed
[04:11] <RAOF> How did it even get into that state? Was that a change-overrides mishap?
[04:12] <vorlon> RAOF: probably not doing all the overrides at queue time that I meant to
[04:14] <RAOF> 👍️. Just curious!
[04:14]  * RAOF will fix it himself should there be a next time.
[07:03] <RAOF> Well, that has been an unusual amount of the “can this thing that's marked verification-done _actually_ be released” game!
[07:15] <tjaalton> RAOF: still reviewing? firmware-sof backport for lunar has a new upload and should be easier for the eyes
[07:27] <ricotz> hello SRU team, please let libreoffice/lunar transition to -updates, https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2037274
[07:27] -ubottu:#ubuntu-release- Launchpad bug 2037274 in libreoffice (Ubuntu Lunar) "[SRU] libreoffice 7.5.7 for lunar" [Medium, Fix Committed]
[07:27] <ricotz> it is blocking https://bugs.launchpad.net/ubuntu/jammy/+source/libreoffice/+bug/2039150
[07:27] -ubottu:#ubuntu-release- Launchpad bug 2039150 in libreoffice (Ubuntu Jammy) "[BPO] libreoffice 7.5.7 for jammy" [Medium, In Progress]
[08:51] -queuebot:#ubuntu-release- Unapproved: network-manager (mantic-proposed/main) [1.44.2-1ubuntu1 => 1.44.2-1ubuntu1.1] (desktop-core, i386-whitelist)
[08:56] <slyon> Hey ubuntu-sru! ^ this should be high priority for Mantic, see bug #2039503
[08:56] -ubottu:#ubuntu-release- Bug 2039503 in network-manager (Ubuntu Mantic) "package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10" [Critical, In Progress] https://launchpad.net/bugs/2039503
[09:03] <slyon> jbicha: FYI: I needed to cherry-pick some git-ubuntu commits for your latest merge, to restore git history in the packaging repository. ^
[10:40] -queuebot:#ubuntu-release- Unapproved: accepted network-manager [source] (mantic-proposed) [1.44.2-1ubuntu1.1]
[13:26] <slyon> bdmurray: I just did the SRU verification for bug #2039503 We should consider getting this into the -updates pocket before enabling the Mantic upgrades.
[13:26] -ubottu:#ubuntu-release- Bug 2039503 in network-manager (Ubuntu Mantic) "package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10" [Critical, Fix Committed] https://launchpad.net/bugs/2039503
[13:27] <mfo> Hi. While the development release isn't open, which upload rights are required for the latest stable release (since the upcoming development release will be based on it, but it's already a stable release) -- Core dev or SRU dev?  Thanks!
[13:28] <mfo> (This doesn't seem to be addressed in https://wiki.ubuntu.com/StableReleaseUpdates#Development_Release_Fixed_First )
[13:28] <slyon> mfo: AFAIK ~ubuntu-sru rights are needed to upload into stable series.
[13:29] <slyon> everybody else (including ~ubuntu-core-dev) need to wait for the archive to be re-opened before uploading into the "devel" series
[13:32] <mfo> slyon, thanks! ack, that helps, but i wonder whether there is / should be a different requirement in this period, since the latest -updates will get into devel (I have something to "SRU" to M, but don't want to break the rule for N if it's a corner case)
[13:35] <slyon> mfo: right, it's an edge case around Ubuntu releases where the archive is still frozen. I think many devs "stage" their changes for the "devel" series in a corresponding packaging repository, to be uploaded as soon as the archive re-opens, while uploading the SRU already (and stating that circumstance in the SRU bug report).
[13:36] <slyon> So did I with my NetworkManager SRU above. Uploading 1.44.2-1ubuntu1.1 (SRU), while staging the same change with version number 1.44.2-1ubuntu2 in the git packaging repository.
[13:38] <mfo> slyon, cool, the staging for devel part helps -- then I can ask a core dev to review/stage it, and proceed with SRUs.
[13:38] <mfo> slyon, thanks!
[13:38] <rbasak> mfo: if you want to upload an SRU for Mantic, then I wouldn't worry about the core-dev vs. SRU developer distinction in this transition period.
[13:39] <mfo> rbasak, ack; thanks!
[13:40] <slyon> mfo: you're welcome. I guess you could even "stage" your proposed change in a merge-proposal (e.g. against a git-ubuntu "ubuntu/devel" branch) on Launchpad. While uploading an SRU into the "mantic" UNAPPROVED queue for SRU review, using normal core-dev/motu upload rights.
[13:41] <rbasak> FWIW, the SRU team don't have control of the Mantic updates pocket yet.
[13:42] <mfo> slyon, +1
[13:43] <mfo> rbasak, ack; is there an official place to follow these changes/news, other than ubuntu-release/-devel lists?
[13:50] <rbasak> mfo: there's no other good place, sorry. This channel is perhaps best for discussion about it. It's a weird state that only occurs for a week or two every six months, and usually everyone just pauses, except for urgent stuff that can't wait for which we coordinate manually here.
[13:51] <rbasak> This time we did change one thing - with discussion between some SRU and release team members the final freeze announcement actually came with some instructions :-)
[13:52] <rbasak> In hindsight that didn't specifically cover what to do for the post-release period but I think the existing instructions will still work. We will just need to ask the release team once uploaded what they want to do about it.
[14:01] <mfo> rbasak, roger, thanks; this explanation is quite helpful. I mostly wanted to ensure an upload with my current (sru) upload rights wouldn't be unwelcome, and it looks like it's OK, and we just talk about it here, when it happens.  Thanks again!
[14:45] <tsimonq2> Codename, oh codename, where art thou?
[14:49] <xnox> tsimonq2: on holidays
[14:50] <tsimonq2> >:)
[14:53] <Eickmeyer> tsimonq2: 🚌
[15:54] -queuebot:#ubuntu-release- Unapproved: gnome-shell-extension-desktop-icons-ng (mantic-proposed/main) [46+really47.0.5-1 => 46+really47.0.7-0ubuntu1] (ubuntu-desktop)
=== deathcollege__ is now known as deathcollege
[19:09] -queuebot:#ubuntu-release- Unapproved: accepted libreoffice [source] (jammy-backports) [4:7.5.7-0ubuntu0.23.04.1~bpo22.04.1]
[20:14] -queuebot:#ubuntu-release- Unapproved: python-kubernetes (mantic-proposed/universe) [12.0.1-1ubuntu1 => 22.6.0-2] (no packageset) (sync)
[22:26] -queuebot:#ubuntu-release- Unapproved: openjdk-17 (mantic-proposed/main) [17.0.9~6ea-1 => 17.0.9+9-1] (i386-whitelist) (sync)
[22:27] -queuebot:#ubuntu-release- Unapproved: accepted openjdk-17 [sync] (mantic-proposed) [17.0.9+9-1]
[22:30] <_doko>  I accepted the openjdk-17 security upload for now. I'll check with security and sru how to propagate that to the mantic security/updates pockets