[00:00] -queuebot:#ubuntu-release- New binary: opencascade [s390x] (kinetic-proposed/universe) [7.6.3+dfsg1-2] (no packageset) [00:03] -queuebot:#ubuntu-release- New binary: opencascade [ppc64el] (kinetic-proposed/universe) [7.6.3+dfsg1-2] (no packageset) [00:04] vorlon: I merged the nvidia fix to ubuntu/jammy [00:05] bdmurray: ack [00:06] bdmurray: string fix pushed [00:06] bdmurray: and I'll go ahead and rebase it [00:06] vorlon: I changed the changelog entry - sorry [00:09] vorlon: How do you want to proceed with the upload / sru-review? [00:10] bdmurray: well cross-reviewing the SRU would be a little weird, are we better off leaving it for Europe to review? [00:11] vorlon: Yeah, that sounds reasonable. Do you want to the pre-build and upload? [00:12] bdmurray: I can, yes [00:12] vorlon: ack, thanks. I'm gonna run to the store then [00:12] bdmurray: before you go [00:13] bdmurray: I see you approved it /before/ I updated the strings and rebased, do you care about re-reviewing? [00:13] \o/ [00:13] any problems ought to be caught in the SRU queue but maybe we don't want to wait that long [00:13] sil2100: ohai [00:14] sil2100: do you have time for reviewing this if I upload it now? Then bdmurray can get to the store [00:14] vorlon: sure [00:15] sil2100: ok. I still have to write the SRU template but maybe I can get the code uploaded for your review first [00:15] vorlon: I'd seen the updated strings but not the changelog change. Anyway I still approve [00:19] bdmurray: you go to the store, I'll do the sru-review part since it never hurts to have a third pair of eyes on it [00:20] sil2100: fwiw a little delayed, pre-build.sh was not run before final commit on either of our branches and I'm cleaning up linting errors [00:24] de-linted, now waiting for pre-build to finish [00:27] I'm ready o/ [00:35] -queuebot:#ubuntu-release- Unapproved: rejected openconnect [source] (jammy-proposed) [8.20-1ubuntu0.1] [00:42] SRU template for LP: #1977493 written before pre-build has completed. :P [00:42] Launchpad bug 1977493 in ubuntu-release-upgrader (Ubuntu) "Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-modules" [Medium, Triaged] https://launchpad.net/bugs/1977493 [00:43] seems like it's being unpleasantly slow to download indices via apt [00:43] for demotions.py [00:44] got faster when I disconnected from the VPN but still taking forever. An 'apt update' here is trivially fast in comparison [00:45] ah it has to download Contents, maybe that's why? [00:46] still - not reasonable [00:48] I don't remember if I ever ran pre-build on ubuntu-release-upgrader, so not sure how long it was usually taking [00:49] sil2100: it's running, it's being obscenely slow, I don't have a good way to debug the performance issues right now; so I'm going afk for a little bit to eat dinner. I expect to be back in < 30m [00:50] perf top can be helpful for a quick 'what the heck is this doing' kindof view, if you weren't planning on it and don't have anything better set up [00:51] hm, okay, this might be a bit too late for me, since it's already 3 at night here [00:51] gn8 sil2100 :) [00:52] If anything I can always review+accept it tomorrow morning [00:53] o/ [01:38] -queuebot:#ubuntu-release- New binary: opencascade [arm64] (kinetic-proposed/universe) [7.6.3+dfsg1-2] (no packageset) [01:45] vorlon: its generating demotions for every upgrade path which might not be necessary given things aren't getting demoted in jammy? [01:46] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (jammy-proposed/main) [1:22.04.12 => 1:22.04.13] (core) [01:48] -queuebot:#ubuntu-release- New binary: opencascade [armhf] (kinetic-proposed/universe) [7.6.3+dfsg1-2] (no packageset) [02:18] Hrm. OEM would like to release linux-firmware 1.187.33 into focal-updates so they can spin an image today. This fixes #1981922, which also applies to jammy, and has an SRU ready to be released into jammy-updates. [02:18] However: 22.04.1 point release freeze. [02:19] RAOF: I think it's ok to release to focal before releasing to jammy [02:19] the SRU is *present* in jammy-proposed, so it's not going to fall off the radar [02:20] Yup. [02:21] My concern was that the point release is also where we start suggesting upgrades, so we could fix someone's suspend/resume, then suggest they upgrade to 22.04 which will break their suspend/resume. [02:21] But as long as we release the jammy-proposed one promptly, there's not a huge window for that. [02:21] -queuebot:#ubuntu-release- New: accepted opencascade [arm64] (kinetic-proposed) [7.6.3+dfsg1-2] [02:21] RAOF: right, so I think this should be on the list for us to release in jammy as soon as images are finalized [02:21] -queuebot:#ubuntu-release- New: accepted opencascade [armhf] (kinetic-proposed) [7.6.3+dfsg1-2] [02:21] -queuebot:#ubuntu-release- New: accepted dh-nss [amd64] (kinetic-proposed) [1] [02:21] -queuebot:#ubuntu-release- New: accepted opencascade [amd64] (kinetic-proposed) [7.6.3+dfsg1-2] [02:21] -queuebot:#ubuntu-release- New: accepted opencascade [s390x] (kinetic-proposed) [7.6.3+dfsg1-2] [02:21] -queuebot:#ubuntu-release- New: accepted junit5-system-exit [amd64] (kinetic-proposed) [1.1.2-1] [02:22] -queuebot:#ubuntu-release- New: accepted opencascade [ppc64el] (kinetic-proposed) [7.6.3+dfsg1-2] [02:22] RAOF: also, hi! if you would like to review the ubuntu-release-upgrader SRU in the jammy-proposed queue, perhaps this would accelerate us being ready to turn on upgrades :) [02:22] vorlon: Do we have such a list somewhere? (I'm not across the entirety of the release process) [02:22] Certainly, sir! [02:22] RAOF: AFAIK the list is currently empty and the variable has been deleted ;P [02:23] Top hole! [02:23] RAOF: however, bdmurray is on the lever for turning on upgrades, so flagging it to him ^^ [02:30] bdmurray: do you know if anyone looked at why jammy desktop images are oversized? [02:38] vorlon: Does `.pytest_cache` really want to be added in that upload? [02:38] RAOF: nope. feel free to reject and I'll reupload [02:39] did git tell me this was added ? of course not [02:39] There also seems to be a bunch of .pyc shipped elsewhere, but that appears to be the case with the package in the archive, too? [02:40] -queuebot:#ubuntu-release- Unapproved: rejected ubuntu-release-upgrader [source] (jammy-proposed) [1:22.04.13] [02:40] hah spectacular [02:40] Python packaging must have changed since last I touched it. [02:41] the .pyc should not be shipped in the actual binary packages, and their presence in the source tarball are a side effect of us not using gbp for the builds because it's terrible? [02:42] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (jammy-proposed/main) [1:22.04.12 => 1:22.04.13] (core) [02:42] __pycache__ is in .gitignore, which is sensible. but debuild -i -I does not clean it and neither does anything else. gbp would, but gbp is awful [02:43] * RAOF hasn't really had a problem with gbp, but I've also not tried to do anything remotely fancy. [02:43] -queuebot:#ubuntu-release- Unapproved: rejected ubuntu-release-upgrader [source] (jammy-proposed) [1:22.04.13] [02:44] maybe they've cleaned it up and I should give it another chance [02:45] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (jammy-proposed/main) [1:22.04.12 => 1:22.04.13] (core) [02:45] RAOF: ^^ hopefully that's clean [02:47] Much nicer! [02:48] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-release-upgrader [source] (jammy-proposed) [1:22.04.13] [02:48] I wonder if we should have some SRU tooling around checking translations? There's a lot of diff there, and any signal (translations that are now missing, mostly) is really difficult to extract. [04:29] RAOF: by missing translations, do you mean regressed translations? I would grep for '^-msgstr "[^"]|^\+#.*fuzzy' (which, effectively, I did) [04:29] Hm, yeah. That'd do it. [04:31] * RAOF ponders adding that to `sru-review` [04:31] After getting stuff from the shops. [06:19] Will have that livecd-rootfs fix uploaded by about Europe EOD. [09:07] Anyone knows of a way to point do-release-upgrade from focal to the upgrader in jammy-proposed? -p will currently fail as Jammy isn't available yet, -d will point to jammy-updates, and those flags are mutually exclusive. [09:39] -queuebot:#ubuntu-release- New: accepted dotnet6 [source] (jammy-proposed) [6.0.107-0ubuntu2~22.04.1] [09:47] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-515 [amd64] (kinetic-proposed/restricted) [515.65.01-0ubuntu2] (i386-whitelist) [09:53] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-515 [arm64] (kinetic-proposed/restricted) [515.65.01-0ubuntu2] (i386-whitelist) [09:53] schopin: yeah, it's tricky, I don't know the details but we did ask Brian about some test-cases for those as he was usually doing them. Please see the test case Steve wrote no https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1977493 as inspiration [09:53] Launchpad bug 1977493 in Ubuntu on IBM z Systems "Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-modules" [Medium, Fix Committed] [09:59] sil2100: thanks, I'll amend my test cases and will do a proper verif (I've used the git tree so far) [10:07] schopin: thank you :) [10:07] Yeah, I'd like as much testing of the ubuntu-release-upgrader package as possible [10:11] hmm, one scenario I haven't tested yet is nvidia machine using nouveau. I'll add it to my list :) [10:42] hey. Can we release google-guest-agent SRU, please? cf: LP: #1959392. [10:42] Launchpad bug 1959392 in google-guest-agent (Ubuntu Jammy) "Please update to 20220622.00 upstream release" [Undecided, Fix Committed] https://launchpad.net/bugs/1959392 [10:43] racb: ^^ (since you're on duty today) [10:53] Will this affect the point release? === guiverc2 is now known as guiverc [11:02] -queuebot:#ubuntu-release- Unapproved: rejected ceph-iscsi [source] (focal-proposed) [3.4-0ubuntu2.2] [11:25] -queuebot:#ubuntu-release- Unapproved: accepted nova [source] (bionic-proposed) [2:17.0.13-0ubuntu5] [11:54] -queuebot:#ubuntu-release- Unapproved: rejected net-snmp [source] (focal-proposed) [5.8+dfsg-2ubuntu2.4] [12:04] -queuebot:#ubuntu-release- New binary: dotnet6 [amd64] (jammy-proposed/universe) [6.0.107-0ubuntu2~22.04.1] (no packageset) [12:05] -queuebot:#ubuntu-release- Unapproved: protobuf-c (focal-proposed/universe) [1.3.3-1ubuntu0.1 => 1.3.3-1ubuntu0.2] (i386-whitelist, kubuntu) [12:06] -queuebot:#ubuntu-release- Unapproved: rejected protobuf-c [source] (focal-proposed) [1.3.3-1ubuntu0.1] [12:10] -queuebot:#ubuntu-release- Unapproved: accepted protobuf-c [source] (focal-proposed) [1.3.3-1ubuntu0.2] [12:32] -queuebot:#ubuntu-release- Unapproved: accepted xdg-desktop-portal [source] (focal-proposed) [1.6.0-1ubuntu2] [12:43] -queuebot:#ubuntu-release- Unapproved: accepted net-snmp [source] (focal-proposed) [5.8+dfsg-2ubuntu2.5] [13:11] -queuebot:#ubuntu-release- Unapproved: accepted python-magnumclient [source] (focal-proposed) [2.11.0-0ubuntu6] [14:28] schopin: "nvidia machine using nouveau" should look the same as any non-nvidia system to the upgrader [14:30] rbasak, utkarsh2102: google-guest-agent doesn't affect the point release because although google-guest-agent is included in a cloud image, cloud images are released continuously and do not participate in the point releases [15:09] -queuebot:#ubuntu-release- New: accepted dotnet6 [amd64] (jammy-proposed) [6.0.107-0ubuntu2~22.04.1] [15:38] Maybe we should just make a meta-release-lts-development-proposed file [15:47] Hello! I noticed that hugo in Ubuntu kinetic is stuck at 0.92.2-1 when it has been at 0.101.0-1 in Debian since the end of June / early July. [15:48] The new version is in kinetic-proposed [15:49] https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#hugo [15:49] Missing build dependencies: golang-github-aws-aws-sdk-go-dev (>= 1.43.5) from Launchpad [15:49] It seems to be due to the fact that newer versions of golang-github-aws-aws-sdk-go, which hugo 0.101.0-1 depends on, is not being sync'ed from Debian, [15:50] bdmurray: Thank you for your quick response, and thanks in advance from looking into it. :-) [15:53] jawn-smith is on +1 migration today and might be able to look into hugo not migrating [15:53] well he's TIL on the package in question [15:53] So +2 reasons for him to look at it! [15:53] I'll get on that! === tumbleweed_ is now known as tumbleweed [15:55] Thank you so much bdmurray vorlon jawn-smith! :-D [15:55] By the way, what does "TIL" mean? (Sorry for my newbie question!) [15:55] "Touched it last" [15:57] Oh, haha! That's cute! I'll remember that and maybe start using that term at work with my colleagues! Thanks! [15:58] (Not to be confused with Today I Learned, would suggest #debian-til on OFTC :) ) [15:59] Speaking of migration, I am a bit concerned about the regressions with golang-golang-x-net, and it is causing regressions on Debian too... https://tracker.debian.org/pkg/golang-golang-x-net Hope that won't cause too much trouble. [16:00] tsimonq2: Haha! Nice! [16:01] jawn-smith: Wow! golang-1.19 1.19-1! Thank you so much for the upload! Hurray! (I've been away and just started catching up. :-) ) [16:02] Sure np! I'm working on getting it uploaded to Ubuntu today as well [16:03] (We use Hugo a loooooot for $dayjob, so if something ends up not working lmk :) ) [16:04] Will do. I suspect this might be related to the deprecation of SHA1 in Go >= 1.18. If I'm right it's a test-only patch [16:10] tsimonq2: Woohoo! So happy Hugo is an integral part of your $dayjob! [16:12] jawn-smith: Great insight! So happy that you are on top of these things! [16:20] -queuebot:#ubuntu-release- Builds: Ubuntu WSL [Jammy 22.04.1] (2218669216) has been added [16:35] -queuebot:#ubuntu-release- Unapproved: accepted dnspython [source] (focal-proposed) [1.16.0-1ubuntu1] [18:37] could we build libavif and its dependency libgav1 on i386? it's wanted by libgd2. Let me know if there's a better place I should make this request. [18:51] foka, tsimonq2: Got hugo successfully built. [18:52] Guys, I just realized something. Ubuntu Studio and Kubuntu originally had the "Get New Stuff" feature work (at least I know it worked for me). But lately I've been seeing many reports about an "Invalid number of concurrent steams" error when trying to use that feature, and I got it myself once. I think we should check that, I'm going to be testing it shortly. [18:52] jawn-smith: Hurray! That was quick! Thank you so much! [18:53] arraybolt3: That's a feature specific to the plasma desktop, probably best to talk about that in #kubuntu-devel:libera.chat . [18:53] Eickmeyer: True, but I think it's a regression in 22.04.1 from 22.04. [18:54] Thus why I brought it here. [18:56] arraybolt3: Awesome, and I know everyone appreciates the heads-up. Let's narrow-down a component there, and I'm sure RikMills would also like to narrow it down as well. [18:56] 👍️ Once the test is done I'll take it to -devel (mid-Kylin test right now and this system is finicky with multiple VM installs at once). [19:01] jawn-smith: Thank you so much! [19:01] You're welcome! [19:01] Eickmeyer: I'm at the stage where the bug is reproducible on my local system and I'm iterating. Shouldn't be too much longer. [19:19] tsimonq2: ack [19:20] OK, panic averted, the bug is in the original 22.04 ISO of Kubuntu. [19:25] phew [19:26] Wimpy: hello helloooo [19:26] sil2100: What's weird is the feature worked once in Ubuntu Studio 22.04 when I very first installed it, so Idk what happened (maybe something changed on KDE's servers that broke it). [19:27] Wimpy: do you think you and the MATE team would have some time for Ubuntu Mate testing? :) [19:35] arraybolt3: Awesome, glad it's nothing on our end. [19:48] \o/ [19:50] Eickmeyer: The thing I'm currently struggling with is manually blacklisting all of the dependencies pulled in by those two packages. You don't happen to have a list on you? I'm zsyncing your Jammy daily now to see what all gets removed when removing those two. [19:51] I have the syntax down and in the right place, though. [19:52] Simon Quigley: The problem is that even if it's manually blacklisted in the seed, it'll get pulled-in by the old metapackage in -release, even if it's been fixed in -updates. [19:52] So, I'm not following you. [19:53] There's a grep-dctrl command that actually pulls the package list from the task [19:54] I'm manually adding a conditional for ubuntustudio-dvd which adds those two packages to the arguments to not include [19:54] However, it still pulls in all of those dependencies [19:54] I'm not talking about the task blacklist here. Deeper than that [19:54] I see. [19:56] oh I know! [19:56] lxd container, try to install it and see what it pulls in [19:56] v4l2loopback-dkms depends: dkms [19:56] v4l2loopback-utils depends: sudo, gstreamer1.0-tools, v4l-utils; recommends: v4l2loopback-dkms | v4l2loopback-modules [19:56] Simon Quigley: ^ [19:56] Fairly simple depends, actually. [19:58] dkms gstreamer1.0-tools libv4l-0 libv4l2rds0 libv4lconvert0 linux-headers-5.15.0-43 linux-headers-5.15.0-43-generic linux-headers-generic v4l-utils v4l2loopback-dkms v4l2loopback-utils [19:58] Not worrying about Linux headers [19:58] Not worrying about gstreamer [19:58] Yeah, literally what I just wrote. [19:58] So just the rest [19:58] Looks like we concur :) [19:58] kek [19:59] kek [19:59] anyway [20:03] hey folks, I posted some videos about Kylin staying in Chinese. I'd love to hear how you all got it to switch to English though :) [20:03] https://bugs.launchpad.net/ubuntukylin/+bug/1983418 [20:03] Launchpad bug 1983418 in Ubuntu Kylin "Installer does not change language" [Undecided, New] [20:06] Eickmeyer: I'll be back in a few to test my fix. Probably just going to try swapping out the squashfs in the Jammy daily. Fun stuff. [20:06] ew. [20:06] (Building the squashfs with my prototype fix now) [20:07] jbicha: pointed out my mistake and I've marked the bug invalid. so sorry. [20:07] hellsworth: Thanks regardless, we were just talking about it in #lubuntu-devel :) [20:23] jbicha: right place to ask; in general please tag ubuntu-archive for surch requests so it doesn't get missed [20:24] jbicha: also you seem to need an MIR? [20:24] vorlon: livecd-rootfs> Would you happen to be around in a few hours to help fast-track this SRU? May be too late for European folks. [20:25] (I'll fill it out and upload it like a normal SRU.) [20:25] jbicha: so maybe you should do a first pass on the MIR first, since if the MIR gets rejected I'll just end up having to delete the i386 binaries again [20:26] tsimonq2: yes. upload eta? [20:26] ~=< 2h [20:26] vorlon: libgd-dev is in component-mismatches-proposed for demotion to universe. Not sure why the -dev has dependencies the library doesn't though. [20:53] jbicha: aha, demoting then [21:05] tsimonq2: I don't think I'm comfortable fast-tracking anything into .1 one day before release [21:05] JFYI [21:06] So I hope you don't want to get it into a respin? [21:06] sil2100: To be fair, this change only affects Ubuntu Studio and is per the request of their release manager. Eickmeyer may be able to chime in. [21:07] sil2100: this was entirely about getting a respin of UbuntuStudio [21:07] If the fix works as intended (I'm testing it right now), and the only flavor it affects agrees, I'm confused on what the holdup is. [21:07] So long as this fixes the problem with the v4l2loopback-* packages still getting pulled-in, yes. [21:09] sil2100: livecd-rootfs misbuilds UbuntuStudio and causes inclusion of packages that have been removed from the seed/metapackage, and causes install failures on any modern PCs in the default configuration; obviously an upload sooner would have been better, but the respin is justified [21:09] I know the problem, but as the lead for .1 I would like to be involved in making the decision [21:09] ack [21:10] So it seems that we 'dodged a bullet' since the security team was asking me in the morning if they can start releasing security updates, and since I did not plan any respins, I was close to saying 'go ahead' [21:10] But I told them to wait till tomorrow just-in-case [21:11] have you already snapshotted the archive? [21:11] Yes [21:12] Just chiming in to say I'll be happy to put Simon Quigley's work through the furnace to see if it holds up under Lubuntu's test suite on my hardware. [21:13] (I'm sure there's plenty of other testers who will be involved, too.) [21:14] "Guys, I just realized something...." <- This fix for that is in Qt, and it has been in the archive updates pocket for weeks [21:14] s/This/The/ [21:14] Okay, maybe I did overreact a bit here, since I do have confidence in Studio testing, but I *hate it* that once again we're dealing with last-minute-point-release fixes, fast-tracking those one day before release [21:15] Rik Mills: So it's already fixed and everyone's just not updating? I reported it after yet another user in #kubuntu asked about it. [21:15] sil2100: I could save the current images as a fallback, let the SRU through, take a separate snapshot with just livecd-rootfs added, and the final decision could be made based on test results? [21:16] hm, do we need to snapshot livecd-rootfs? [21:16] sil2100: the point of the snapshot is reproducibility of the point release :) [21:16] Since sadly we did get a new linux-riscv kernel into -updates yesterday, by accident of the kernel team [21:16] So we'd have to tinker the snapshot manually somehow to not include the new riscv kernel [21:16] should we roll that back, accept livecd-rootfs, snapshot, roll linux-riscv forward? [21:17] arraybolt3[m]: LP: #1980210 [21:17] Launchpad bug 1980210 in qtbase-opensource-src (Ubuntu Jammy) "[SRU] Unable download from store.kde.org with error 'invalid number of concurrent streams'" [High, Fix Released] https://launchpad.net/bugs/1980210 [21:17] sil2100: Oh, believe me, me too. I'm not sure if you saw my email but: https://lists.ubuntu.com/archives/ubuntu-release/2022-August/005454.html [21:17] Sorry, those were linux-starfive kernels actually [21:18] RikMills[m]: \o/ and I won't raise another alarm after a user report without verifying it myself. [21:19] sil2100: let me know how you'd like to proceed; regardless I have time for the SRU review [21:19] (and targeted respins etc) [21:19] Please allow me to be a little bit bitter right now [21:20] sil2100: here have a negroni [21:21] tsimonq2: I saw the e-mail, but I did not see anyone from the release team nor SRU team officially 'ACKing' a fast-track of a package so late in the .1 cycle, at least not via e-mail (and I don't remember the case on IRC at least, but maybe my memory is weary) [21:21] Just to be clear: I'm fine with going ahead with it *right now* [21:22] sil2100: I did discuss on IRC with them that livecd-rootfs was the right way to get it fixed; I did not communicate any deadlines, sorry [21:23] What I'm bitter about is the process in how this was handled. The release team is responsible for the point-release preparations, so any out-of-process actions should require an explicit ACK, especially that the build process is very fragile and we need to keep everything in sync [21:24] I apologize if there was any miscommunication on my end as well, I know I discussed it with vorlon but I haven't kept up with who holds which hats these days. [21:24] I did not see anyone reaching out to the release team asking: "Is it fine for me to prepare the fix and us fast-tracking it?", this seemed more like "Okay, I'll prep the changes and we'll fast-track it" [21:24] If vorlon did make an explicit call about that, then it's on me for missing that [21:26] Okay, I stop being bitter now. Let's get this change prepared, reviewed and see where to go from there [21:27] I assumed it was a foregone conclusion that the existing UbuntuStudio image was unreleasable for 22.04.1 as-is with the current bug, now that the bug in question was known; and failed to communicate it explicitly [21:29] I'm not going to just throw a diff at you guys and expect magic to happen, I'm still finishing my testing, but here's what I'm thinking tentatively: https://pastebin.com/MV23Zd4X [21:29] My understanding is that it was going to be slightly hacky regardless. [21:31] FWIW, I'm sorry this wasn't caught sooner. [21:31] vorlon: well, this was *not* a regression. 22.04 had the same problem and this was the first report I have heard of it [21:32] This is why even though it is a critical bug, I did not consider it a release blocker. It should have been fixed, yes, and we tried to do it with the simple meta change which was anyway fast-tracked, but we didn't [21:32] tsimonq2: uh that is not at all clear to me and not what I was expecting; I was expecting an 'apt-get autoremove purge -y v4l2loopback-$thing' somewhere towards the end of the build [21:33] I guess this is the part of the code that Laney pointed you to earlier; but still it's a lot hackier than I was expecting [21:33] I'd really prefer some workaround that has a minimal regression potential. The last thing we want is to introduce a regression on top of the fix [21:33] vorlon: This just ensures they aren't even installed in the first place, which uses less compute power. That's the way I'd look at it at least. [21:34] I could explicitly do it for the ubuntustudio-video task? [21:34] tsimonq2: I think that's premature optimization, vs the cost of humans trying to read the code [21:34] vorlon: Fair point. I'll continue iterating and get back to you shortly [21:53] vorlon: Am I at least on the right track? https://pastebin.com/Y5TUpNYZ [21:54] ah, I see the error it's giving me... still [21:56] tsimonq2: I'm not sure because I think remove_package is only used on images that have multiple squashfs layers and remove packages in some of them, so I cannot vouch for the behavior of that code [21:56] yeah that's what I'm figuring out [21:56] I recently added a code change in kinetic to remove a package from cloud images and I did it in a chroot hook rather than touching any of that [21:57] Jammy or Kinetic? [21:57] ah sorry [21:57] * tsimonq2 learns how to read and slows down... [22:00] -queuebot:#ubuntu-release- Packageset: Added libavif to i386-whitelist in kinetic [22:00] -queuebot:#ubuntu-release- Packageset: Added libgav1 to i386-whitelist in kinetic [22:00] -queuebot:#ubuntu-release- Unapproved: limnoria (jammy-backports/universe) [2022.3.17-1 => 2022.6.23-1~bpo22.04.1] (no packageset) [22:05] vorlon: https://pastebin.com/6uminbBu much more like your fix [22:07] tsimonq2: do you need to mark the script executable? [22:08] also 'exit 0' is superfluous [22:08] ack to the latter, looking into the former, thanks [22:09] tsimonq2: the existing ones in the tree for ubuntu-cpc are, and that's not by accident [22:09] vorlon: None of the groups in this particular section do that, though. I can do it just in case? [22:09] tsimonq2: also, syntax error in the pastebin, missing space before ]! [22:09] ack [22:10] (I noticed as I made the same mistake already in exactly livecd-rootfs code ;p ) [22:10] https://pastebin.com/Z3kQMqmW [22:11] sil2100: Experience is a good teacher, thanks ;) [22:11] -queuebot:#ubuntu-release- Unapproved: dh-python (focal-backports/universe) [4.20191017ubuntu7 => 5.20220403~bpo20.04.1] (i386-whitelist, ubuntu-desktop) [22:24] queuebot: Snitches get stitches. [22:28] tsimonq2: I'm afk for approximately the next hour, can review an upload or etc when I get back [22:28] Gracias [22:35] -queuebot:#ubuntu-release- Unapproved: yt-dlp (focal-backports/universe) [2022.03.08.1-1~bpo20.04.1 => 2022.07.18-1~bpo20.04.1] (no packageset) [22:56] ubuntu-archive: https://code.launchpad.net/~jbicha/+junk/sync-blacklist [23:03] Simon Quigley: I just gave your SRU the seal of approval from my end via comment. [23:07] tsimonq2: did you do a test build with this change? [23:07] sil2100: Just finished... rolling an ISO to check. [23:08] (Not uploaded quite yet.) [23:09] Remember that livecd-rootfs is on VCS! Would be good to have an MP for that for review purposes, for the ubuntu/jammy branch [23:09] Already working off of Git :) [23:10] Good thought though [23:10] vorlon: ...did you also want an MP for this to review first, or does that last diff look okay? [23:14] tsimonq2: I think either way an MP would be good, since we'd need this in git before we upload to the queue. And it's a very convenient place to do reviews and iterate, better than working off pastebins IMO ;) [23:14] fair enough [23:17] Okay, so from my quick look this feels okay, but I'd like Steve to ACK it before we proceed. I know that this is basically a workaround, but I personally prefer just putting hooks in the hooks directory for the given project. But then again, we never had any hooks for ubuntustudio like this, so it might be a bit more invasive [23:17] If you take a look a few lines above in the code, Ubuntu Kylin does almost an identical thing [23:17] It's just that I'm always terrified when our auto/config grows yet another conditional [23:17] Yes, and I'm saying that I don't like it ;p [23:18] I don't either but it's better than the first iteration :P [23:18] But that's a matter of preference, which is why I'd just like Steve to +1 it [23:20] -queuebot:#ubuntu-release- New binary: autoflake [amd64] (kinetic-proposed/none) [1.4-1] (no packageset) [23:20] -queuebot:#ubuntu-release- New binary: jschema-to-python [amd64] (kinetic-proposed/none) [1.2.3-2] (no packageset) [23:20] -queuebot:#ubuntu-release- New binary: org-present [amd64] (kinetic-proposed/none) [0.1+git20220109.c0f1f36-2] (no packageset) [23:20] -queuebot:#ubuntu-release- New binary: chibicc [amd64] (kinetic-proposed/none) [0+git20220719+ds-1] (no packageset) [23:20] -queuebot:#ubuntu-release- New binary: org-make-toc [amd64] (kinetic-proposed/none) [0.5-1] (no packageset) [23:21] I'd be more hands-on with this process, but this happened yesterday and I'm still dealing with the fallout, and, unfortunately, it's taking priority: https://t.co/XEgtFeTiIN [23:22] Eickmeyer[m]: holy crap [23:22] -queuebot:#ubuntu-release- New binary: emacs-svg-lib [amd64] (kinetic-proposed/none) [0.2.5+ds-1] (no packageset) [23:22] -queuebot:#ubuntu-release- New binary: hazwaz [amd64] (kinetic-proposed/none) [0.0.1-1] (no packageset) [23:22] -queuebot:#ubuntu-release- New binary: python-aio-pika [amd64] (kinetic-proposed/none) [8.0.3-1] (no packageset) [23:22] -queuebot:#ubuntu-release- New binary: raku-json-fast [amd64] (kinetic-proposed/none) [0.17-1] (no packageset) [23:22] -queuebot:#ubuntu-release- New binary: raku-readline [amd64] (kinetic-proposed/none) [0.1.5-6] (no packageset) [23:22] -queuebot:#ubuntu-release- New binary: rust-resolv-conf [amd64] (kinetic-proposed/none) [0.7.0-1] (no packageset) [23:22] -queuebot:#ubuntu-release- New binary: specreduce-data [amd64] (kinetic-proposed/none) [0+git2021.11.18-2] (no packageset) [23:22] -queuebot:#ubuntu-release- New binary: writeroom-mode [amd64] (kinetic-proposed/none) [3.11-1] (no packageset) [23:22] -queuebot:#ubuntu-release- New binary: gnome-shell-extension-runcat [amd64] (kinetic-proposed/none) [18-2] (no packageset) [23:22] -queuebot:#ubuntu-release- New binary: python-xxhash [amd64] (kinetic-proposed/none) [3.0.0-1] (no packageset) [23:22] -queuebot:#ubuntu-release- New binary: rust-async-mutex [amd64] (kinetic-proposed/none) [1.4.0-1] (no packageset) [23:22] -queuebot:#ubuntu-release- New binary: tqftpserv [amd64] (kinetic-proposed/none) [0.0+git20200207-1] (no packageset) [23:22] -queuebot:#ubuntu-release- New binary: isochron [amd64] (kinetic-proposed/none) [0.9~rc4-1] (no packageset) [23:22] -queuebot:#ubuntu-release- New binary: rust-tokio-openssl [amd64] (kinetic-proposed/none) [0.6.3-1] (no packageset) [23:22] -queuebot:#ubuntu-release- New binary: raku-json-optin [amd64] (kinetic-proposed/none) [0.0.1-1] (no packageset) [23:22] -queuebot:#ubuntu-release- New binary: orage [amd64] (kinetic-proposed/none) [4.16.0-1] (no packageset) [23:22] -queuebot:#ubuntu-release- New binary: pyproject-metadata [amd64] (kinetic-proposed/none) [0.6.1-1] (no packageset) [23:22] -queuebot:#ubuntu-release- New binary: pgpainless [amd64] (kinetic-proposed/none) [1.3.2-1] (no packageset) [23:23] tsimonq2: okay, so I'd propose something like this - once you prepare the MP, let's build the new package in a clean bileto PPA, bin-sync it into the queue once it's built at the same time run a livefs build against the PPA [23:24] -queuebot:#ubuntu-release- New binary: qt6ct [ppc64el] (kinetic-proposed/none) [0.5-2] (no packageset) [23:24] Sounds good! [23:24] Since I'd like to run a quick manifest diff to make sure the only thing that changed in the live system is the package - all before Steve is back [23:24] -queuebot:#ubuntu-release- New binary: openmesh [amd64] (kinetic-proposed/none) [9.0-1] (no packageset) [23:24] -queuebot:#ubuntu-release- New binary: vte2.91 [amd64] (kinetic-proposed/main) [0.69.90-2] (ubuntu-desktop) [23:24] -queuebot:#ubuntu-release- New binary: qt6ct [s390x] (kinetic-proposed/none) [0.5-2] (no packageset) [23:25] It's a bit wasteful, but I prefer to be safe than sorry [23:26] eh, still need to play around with the linux-starfive kernel packages [23:26] Since I thought maybe we can somehow alter the snapshot, but that actually feels a bit more complicated than just moving the kernel back to -proposed temporarily [23:26] -queuebot:#ubuntu-release- New binary: openmesh [ppc64el] (kinetic-proposed/none) [9.0-1] (no packageset) [23:27] -queuebot:#ubuntu-release- New binary: python-xxhash [ppc64el] (kinetic-proposed/none) [3.0.0-1] (no packageset) [23:27] -queuebot:#ubuntu-release- New binary: orage [ppc64el] (kinetic-proposed/none) [4.16.0-1] (no packageset) [23:27] I totally agree, running this ISO through a test just to make sure first [23:27] -queuebot:#ubuntu-release- New binary: isochron [s390x] (kinetic-proposed/none) [0.9~rc4-1] (no packageset) [23:27] -queuebot:#ubuntu-release- New binary: python-xxhash [s390x] (kinetic-proposed/none) [3.0.0-1] (no packageset) [23:27] -queuebot:#ubuntu-release- New binary: raku-json-fast [ppc64el] (kinetic-proposed/none) [0.17-1] (no packageset) [23:28] -queuebot:#ubuntu-release- New binary: raku-json-optin [s390x] (kinetic-proposed/none) [0.0.1-1] (no packageset) [23:28] -queuebot:#ubuntu-release- New binary: tqftpserv [ppc64el] (kinetic-proposed/none) [0.0+git20200207-1] (no packageset) [23:28] -queuebot:#ubuntu-release- New binary: vte2.91 [s390x] (kinetic-proposed/main) [0.69.90-2] (ubuntu-desktop) [23:28] -queuebot:#ubuntu-release- New binary: orage [s390x] (kinetic-proposed/none) [4.16.0-1] (no packageset) [23:28] -queuebot:#ubuntu-release- New binary: raku-json-optin [ppc64el] (kinetic-proposed/none) [0.0.1-1] (no packageset) [23:28] -queuebot:#ubuntu-release- New binary: vte2.91 [ppc64el] (kinetic-proposed/main) [0.69.90-2] (ubuntu-desktop) [23:28] -queuebot:#ubuntu-release- New binary: qt6ct [armhf] (kinetic-proposed/none) [0.5-2] (no packageset) [23:28] -queuebot:#ubuntu-release- New binary: rust-async-mutex [ppc64el] (kinetic-proposed/none) [1.4.0-1] (no packageset) [23:29] -queuebot:#ubuntu-release- New binary: qt6ct [arm64] (kinetic-proposed/none) [0.5-2] (no packageset) [23:29] -queuebot:#ubuntu-release- New binary: raku-readline [ppc64el] (kinetic-proposed/none) [0.1.5-6] (no packageset) [23:29] -queuebot:#ubuntu-release- New binary: rust-resolv-conf [ppc64el] (kinetic-proposed/none) [0.7.0-1] (no packageset) [23:29] -queuebot:#ubuntu-release- New binary: raku-json-fast [s390x] (kinetic-proposed/none) [0.17-1] (no packageset) [23:29] -queuebot:#ubuntu-release- New binary: rust-tokio-openssl [ppc64el] (kinetic-proposed/none) [0.6.3-1] (no packageset) [23:29] -queuebot:#ubuntu-release- New binary: raku-readline [s390x] (kinetic-proposed/none) [0.1.5-6] (no packageset) [23:29] -queuebot:#ubuntu-release- New binary: rust-async-mutex [s390x] (kinetic-proposed/none) [1.4.0-1] (no packageset) [23:30] -queuebot:#ubuntu-release- New binary: rust-tokio-openssl [s390x] (kinetic-proposed/none) [0.6.3-1] (no packageset) [23:31] -queuebot:#ubuntu-release- New binary: openmesh [s390x] (kinetic-proposed/none) [9.0-1] (no packageset) [23:31] -queuebot:#ubuntu-release- New binary: tqftpserv [s390x] (kinetic-proposed/none) [0.0+git20200207-1] (no packageset) [23:31] -queuebot:#ubuntu-release- New binary: rust-resolv-conf [s390x] (kinetic-proposed/none) [0.7.0-1] (no packageset) [23:34] vorlon: shit, we might have another problem re: snapshotting [23:34] -queuebot:#ubuntu-release- New binary: vte2.91 [armhf] (kinetic-proposed/main) [0.69.90-2] (ubuntu-desktop) [23:35] vorlon: apparently, looking at jammy-changes, we also had new nvidia drivers published (?!) after the release candidates got built [23:35] -queuebot:#ubuntu-release- New binary: chibicc [riscv64] (kinetic-proposed/none) [0+git20220719+ds-1] (no packageset) [23:36] vorlon: and those are pulled into the pool for our desktop images, so the snapshot will != with what we have in ubuntu [23:36] -queuebot:#ubuntu-release- New binary: isochron [riscv64] (kinetic-proposed/none) [0.9~rc4-1] (no packageset) [23:37] vorlon: is there a way to easily modify the indexes to just pull in one package? aka. modifying the snapshot. Or maybe leave the snapshot as-is but simply leave a mention 'please also pull in livecd-rootfs version XXX' [23:38] vorlon: and just so it's clear: I had not given a green light for the nvidia stuff landing in -updates/-security, it was done without my knowledge [23:42] -queuebot:#ubuntu-release- New binary: vte2.91 [arm64] (kinetic-proposed/main) [0.69.90-2] (ubuntu-desktop) [23:43] -queuebot:#ubuntu-release- New binary: python-xxhash [riscv64] (kinetic-proposed/none) [3.0.0-1] (no packageset) [23:44] tsimonq2: how's the MP going? [23:44] < 5 mins [23:44] I'd like to get things moving ASAP, I actually had everything planned to release earlier tomorrow, and this is really breaking my night [23:46] -queuebot:#ubuntu-release- New binary: tqftpserv [riscv64] (kinetic-proposed/none) [0.0+git20200207-1] (no packageset) [23:47] I'll start pre-publishing the desktop images regardless [23:48] jbicha: wrt sync-blacklist, is there also a lp bug somewhere requesting removal? [23:48] -queuebot:#ubuntu-release- New binary: rust-async-mutex [riscv64] (kinetic-proposed/none) [1.4.0-1] (no packageset) [23:48] https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4886/+packages [23:48] Thank you [23:49] Of course. MP is pushing now [23:49] -queuebot:#ubuntu-release- New binary: isochron [arm64] (kinetic-proposed/none) [0.9~rc4-1] (no packageset) [23:49] -queuebot:#ubuntu-release- New binary: isochron [armhf] (kinetic-proposed/none) [0.9~rc4-1] (no packageset) [23:49] vorlon: one of the 2 extensions just hit the binary NEW queue; the other is still in unapproved Debian NEW. I didn't file bugs [23:49] sil2100: aren't the snapshots using the signed indices files from the archive? I think we want to just roll back the -updates changes [23:50] jbicha: please file a bug for the one already in the archive [23:50] -queuebot:#ubuntu-release- New binary: python-xxhash [armhf] (kinetic-proposed/none) [3.0.0-1] (no packageset) [23:50] -queuebot:#ubuntu-release- New binary: rust-resolv-conf [riscv64] (kinetic-proposed/none) [0.7.0-1] (no packageset) [23:50] -queuebot:#ubuntu-release- New binary: qt6ct [riscv64] (kinetic-proposed/none) [0.5-2] (no packageset) [23:50] vorlon: we'd need to revert quite a lot of packages from both -updates and -security [23:50] -queuebot:#ubuntu-release- New: accepted isochron [arm64] (kinetic-proposed) [0.9~rc4-1] [23:50] -queuebot:#ubuntu-release- New: accepted python-xxhash [armhf] (kinetic-proposed) [3.0.0-1] [23:50] -queuebot:#ubuntu-release- New: accepted qt6ct [riscv64] (kinetic-proposed) [0.5-2] [23:50] -queuebot:#ubuntu-release- New: accepted rust-resolv-conf [riscv64] (kinetic-proposed) [0.7.0-1] [23:50] -queuebot:#ubuntu-release- New: accepted isochron [armhf] (kinetic-proposed) [0.9~rc4-1] [23:50] -queuebot:#ubuntu-release- New: accepted rust-async-mutex [riscv64] (kinetic-proposed) [1.4.0-1] [23:50] -queuebot:#ubuntu-release- New: accepted python-xxhash [riscv64] (kinetic-proposed) [3.0.0-1] [23:50] -queuebot:#ubuntu-release- New: accepted tqftpserv [riscv64] (kinetic-proposed) [0.0+git20200207-1] [23:51] -queuebot:#ubuntu-release- New: accepted chibicc [riscv64] (kinetic-proposed) [0+git20220719+ds-1] [23:51] -queuebot:#ubuntu-release- New: accepted openmesh [s390x] (kinetic-proposed) [9.0-1] [23:51] -queuebot:#ubuntu-release- New: accepted raku-readline [s390x] (kinetic-proposed) [0.1.5-6] [23:51] -queuebot:#ubuntu-release- New: accepted rust-resolv-conf [s390x] (kinetic-proposed) [0.7.0-1] [23:51] -queuebot:#ubuntu-release- New: accepted tqftpserv [s390x] (kinetic-proposed) [0.0+git20200207-1] [23:51] -queuebot:#ubuntu-release- New: accepted vte2.91 [armhf] (kinetic-proposed) [0.69.90-2] [23:51] -queuebot:#ubuntu-release- New: accepted isochron [riscv64] (kinetic-proposed) [0.9~rc4-1] [23:51] -queuebot:#ubuntu-release- New: accepted rust-async-mutex [s390x] (kinetic-proposed) [1.4.0-1] [23:51] -queuebot:#ubuntu-release- New: accepted vte2.91 [arm64] (kinetic-proposed) [0.69.90-2] [23:51] -queuebot:#ubuntu-release- New: accepted raku-json-fast [s390x] (kinetic-proposed) [0.17-1] [23:51] -queuebot:#ubuntu-release- New: accepted rust-tokio-openssl [s390x] (kinetic-proposed) [0.6.3-1] [23:51] -queuebot:#ubuntu-release- New: accepted orage [s390x] (kinetic-proposed) [4.16.0-1] [23:51] -queuebot:#ubuntu-release- New: accepted qt6ct [arm64] (kinetic-proposed) [0.5-2] [23:51] -queuebot:#ubuntu-release- New: accepted raku-json-optin [s390x] (kinetic-proposed) [0.0.1-1] [23:51] -queuebot:#ubuntu-release- New: accepted rust-async-mutex [ppc64el] (kinetic-proposed) [1.4.0-1] [23:51] -queuebot:#ubuntu-release- New: accepted rust-tokio-openssl [ppc64el] (kinetic-proposed) [0.6.3-1] [23:51] -queuebot:#ubuntu-release- New: accepted vte2.91 [ppc64el] (kinetic-proposed) [0.69.90-2] [23:51] -queuebot:#ubuntu-release- New: accepted python-xxhash [s390x] (kinetic-proposed) [3.0.0-1] [23:51] -queuebot:#ubuntu-release- New: accepted raku-readline [ppc64el] (kinetic-proposed) [0.1.5-6] [23:51] -queuebot:#ubuntu-release- New: accepted tqftpserv [ppc64el] (kinetic-proposed) [0.0+git20200207-1] [23:51] sil2100: are you concerned about the amount of work or the risk of breaking something? [23:51] -queuebot:#ubuntu-release- New: accepted qt6ct [armhf] (kinetic-proposed) [0.5-2] [23:51] -queuebot:#ubuntu-release- New binary: orage [armhf] (kinetic-proposed/none) [4.16.0-1] (no packageset) [23:51] -queuebot:#ubuntu-release- New: accepted rust-resolv-conf [ppc64el] (kinetic-proposed) [0.7.0-1] [23:52] vorlon: both! [23:52] -queuebot:#ubuntu-release- New: accepted isochron [s390x] (kinetic-proposed) [0.9~rc4-1] [23:52] -queuebot:#ubuntu-release- New: accepted openmesh [ppc64el] (kinetic-proposed) [9.0-1] [23:52] -queuebot:#ubuntu-release- New: accepted python-xxhash [ppc64el] (kinetic-proposed) [3.0.0-1] [23:52] -queuebot:#ubuntu-release- New: accepted raku-json-fast [ppc64el] (kinetic-proposed) [0.17-1] [23:52] -queuebot:#ubuntu-release- New: accepted vte2.91 [amd64] (kinetic-proposed) [0.69.90-2] [23:52] -queuebot:#ubuntu-release- New binary: orage [arm64] (kinetic-proposed/none) [4.16.0-1] (no packageset) [23:52] -queuebot:#ubuntu-release- New: accepted openmesh [amd64] (kinetic-proposed) [9.0-1] [23:52] -queuebot:#ubuntu-release- New: accepted qt6ct [s390x] (kinetic-proposed) [0.5-2] [23:52] -queuebot:#ubuntu-release- New: accepted vte2.91 [s390x] (kinetic-proposed) [0.69.90-2] [23:52] -queuebot:#ubuntu-release- New: accepted orage [ppc64el] (kinetic-proposed) [4.16.0-1] [23:52] -queuebot:#ubuntu-release- New binary: rust-tokio-openssl [riscv64] (kinetic-proposed/none) [0.6.3-1] (no packageset) [23:52] -queuebot:#ubuntu-release- New: accepted raku-json-optin [ppc64el] (kinetic-proposed) [0.0.1-1] [23:52] sil2100: do you want to delegate it to me so it's my fault if we break something, and get some sleep? :) [23:52] -queuebot:#ubuntu-release- New: accepted gnome-shell-extension-runcat [amd64] (kinetic-proposed) [18-2] [23:52] -queuebot:#ubuntu-release- New: accepted isochron [amd64] (kinetic-proposed) [0.9~rc4-1] [23:52] -queuebot:#ubuntu-release- New: accepted pgpainless [amd64] (kinetic-proposed) [1.3.2-1] [23:52] -queuebot:#ubuntu-release- New: accepted qt6ct [ppc64el] (kinetic-proposed) [0.5-2] [23:52] -queuebot:#ubuntu-release- New: accepted raku-readline [amd64] (kinetic-proposed) [0.1.5-6] [23:52] https://code.launchpad.net/~tsimonq2/ubuntu/+source/livecd-rootfs/+git/livecd-rootfs/+merge/427786 [23:52] -queuebot:#ubuntu-release- New: accepted hazwaz [amd64] (kinetic-proposed) [0.0.1-1] [23:52] -queuebot:#ubuntu-release- New: accepted pyproject-metadata [amd64] (kinetic-proposed) [0.6.1-1] [23:52] -queuebot:#ubuntu-release- New: accepted specreduce-data [amd64] (kinetic-proposed) [0+git2021.11.18-2] [23:52] -queuebot:#ubuntu-release- New: accepted orage [amd64] (kinetic-proposed) [4.16.0-1] [23:52] -queuebot:#ubuntu-release- New: accepted raku-json-fast [amd64] (kinetic-proposed) [0.17-1] [23:53] -queuebot:#ubuntu-release- New: accepted emacs-svg-lib [amd64] (kinetic-proposed) [0.2.5+ds-1] [23:53] -queuebot:#ubuntu-release- New: accepted python-xxhash [amd64] (kinetic-proposed) [3.0.0-1] [23:53] -queuebot:#ubuntu-release- New: accepted rust-async-mutex [amd64] (kinetic-proposed) [1.4.0-1] [23:53] -queuebot:#ubuntu-release- New: accepted rust-tokio-openssl [amd64] (kinetic-proposed) [0.6.3-1] [23:53] -queuebot:#ubuntu-release- New: accepted writeroom-mode [amd64] (kinetic-proposed) [3.11-1] [23:53] -queuebot:#ubuntu-release- New: accepted python-aio-pika [amd64] (kinetic-proposed) [8.0.3-1] [23:53] -queuebot:#ubuntu-release- New: accepted rust-resolv-conf [amd64] (kinetic-proposed) [0.7.0-1] [23:53] -queuebot:#ubuntu-release- New: accepted raku-json-optin [amd64] (kinetic-proposed) [0.0.1-1] [23:53] -queuebot:#ubuntu-release- New: accepted tqftpserv [amd64] (kinetic-proposed) [0.0+git20200207-1] [23:53] sil2100: what's the last package that was included in the candidate images? ubuntustudio-meta? [23:53] ubuntu-archive: bug 1983525 [23:53] Bug 1983525 in gnome-shell-extension-runcat (Ubuntu) "Please remove gnome-shell-extension-runcat" [Undecided, New] https://launchpad.net/bugs/1983525 [23:53] -queuebot:#ubuntu-release- New: accepted autoflake [amd64] (kinetic-proposed) [1.4-1] [23:53] -queuebot:#ubuntu-release- New: accepted jschema-to-python [amd64] (kinetic-proposed) [1.2.3-2] [23:53] -queuebot:#ubuntu-release- New: accepted org-present [amd64] (kinetic-proposed) [0.1+git20220109.c0f1f36-2] [23:53] -queuebot:#ubuntu-release- New: accepted chibicc [amd64] (kinetic-proposed) [0+git20220719+ds-1] [23:53] -queuebot:#ubuntu-release- New: accepted org-make-toc [amd64] (kinetic-proposed) [0.5-1] [23:54] vorlon: yes, I think that's the last one [23:54] vorlon: so you want to revert all those to -proposed just to get the snapshot? [23:54] sil2100: ok. it's a large set and annoying but I'm willing to do the work to revert them all to -proposed, yes [23:54] also have you flagged apw yet about the fact that this broke point release freeze? [23:56] I must say that I got aware of the nvidia stuff landing only just now, I only knew about the accidental linux-starfive release from klebers earlier. So I didn't flag him yet [23:56] And I have no idea why apw actually published those [23:56] I know linux-starfive was accidental as the bug was not marked as blocked for proposed [23:57] vorlon: can't we just leave the current snapshot and add a note next to it to update livecd-rootfs to this-and-that version? ;p Since we're the only consumers of the snapshots, right? [23:58] there's been an nvidia CRD planned for august 2 for a few weeks :( probably the folks who work on that are heads-down on it, and not aware of the release cycle needs