[00:41] -queuebot:#ubuntu-release- Unapproved: gnome-weather (jammy-proposed/universe) [41.0-3 => 41.0-3ubuntu1] (desktop-extra)
[00:45] <sarnold> heh, a few minutes ago in #kernelnewbies on oftc, https://validation.linaro.org/ https://www.lavasoftware.org/  "LAVA is an automated validation architecture primarily aimed at testing deployments of systems based around the Linux kernel on ARM devices" -- I wonder if it'd help this big pile of rpis?
[00:55] -queuebot:#ubuntu-release- New binary: unicorn-hat [arm64] (jammy-proposed/universe) [2.2.3-0ubuntu1] (no packageset)
[00:55] -queuebot:#ubuntu-release- New binary: unicorn-hat [armhf] (jammy-proposed/universe) [2.2.3-0ubuntu1] (no packageset)
[01:10] -queuebot:#ubuntu-release- Unapproved: gnome-weather (jammy-proposed/universe) [41.0-3 => 41.0-3ubuntu2] (desktop-extra)
[01:35] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Jammy Final] has been marked as ready
[02:03] <mwhudson> heh i worked on the first version of that
[02:05] <sarnold> :D
[02:07] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Jammy Final] has been marked as ready
[02:46] <plars> sil2100: waveform: jawn-smith: yes, we only have a cm4-lite
[02:48] <plars> mwhudson: heh, yeah I guess we might remember a bit about that :-D I'm not sure how useful it is for installing ubuntu images these days though. And last I heard, they never really got LMP working, so they still weren't really able to install full images
[02:50] <mwhudson> plars: oh gosh still not working? yikes
[02:51] <plars> mwhudson: just checking in on some things, then yeah, probably a bit. I never actually learned how to sleep very well when I was young. Now I'm old and still don't know how to sleep. *shrug*
[02:52] <mwhudson> plars: i mean the lmp thing :) but yes you should also not be online :)
[02:52]  * plars hides
[02:54] <plars> mwhudson: yeah, maybe they have a replacement now. Not sure. I talked to Dave about it a while back and it sounds like it never really worked out. To be fair, it's a complex problem and LMP was really ambitious
[02:55] <plars> and as much grief as we got for the partition based provisioning, it actually worked quite well for all the images they cared about. The only place it became a problem was for the bootloader itself
[04:58] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Jammy Final] has been marked as ready
[04:59] <RikMills> :D
[05:02] <cpaelzer> vorlon: I was using essentially all that worked from the list in https://wiki.debian.org/CopyrightReviewTools - and the one which flagged those was scan-copyrights (which wraps around licensecheck)
[05:02] <cpaelzer> vorlon: thanks for helping with your experience
[05:03] <cpaelzer> vorlon: I was later on checking other projects m4/* dir and it was a wild mix of every package had another statement about it in d/copyright
[05:03]  * cpaelzer is reading the backlog if there was a reference to how exactly is "should (tm)" be ...
[05:04] <cpaelzer> I found it, exception for autoconf output - thanks!
[05:06] <cpaelzer> this exception wasn't linked from anywhere in https://wiki.ubuntu.com/ArchiveAdministration#NEW_Processing so I wasn't aware
[05:06] <cpaelzer> is it - so far - documented somewhere or just experience?
[05:07] <cpaelzer> and in regard to finding a wild mix in others - this is what I found from a few that were checked out https://paste.ubuntu.com/p/8BkRPtQKxt/
[05:08] <cpaelzer> the real problem this case (I guess) was that the tool outputs "or" when unsure which doesn't fit the format, so again thanks vorlon for clarifying
[06:14] -queuebot:#ubuntu-release- Unapproved: ukui-settings-daemon (jammy-proposed/universe) [3.1.1.1-1 => 3.1.1.1-1ubuntu1] (ubuntukylin)
[06:20] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Jammy Final] has been updated (20220421)
[06:20] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Jammy Final] has been updated (20220421)
[06:20] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Jammy Final] has been updated (20220421)
[06:20] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity riscv64 [Jammy Final] has been updated (20220421)
[06:20] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Jammy Final] has been updated (20220421)
[06:41] <handsome_feng> Is it possible to accept ukui-settings-daemon before final release?
[07:00] <gjolly> cpaelzer: are the latest rebuilds related to the CM4 issue? I'd like to understand if we should rebuild the cloud-images we already have from yesterday.
[07:25] <cpaelzer> gjolly: sorry, but I can't answer you that
[07:25] <cpaelzer> paride: ^^ do you happen to know?
[07:32] <mwhudson> the server rebuilds are for a subiquity issue
[07:35] <gjolly> Ok so we should be good for cloud-images
[07:55] <bdmurray> jbicha, vorlon: I've talked to the security team about gnome-control-center and they think it is appropriate for -security
[07:58] <sil2100> waveform: I see there's a few remaining Pi's that still need testing, but I also wonder if those are actually doable
[07:59] <bdmurray> If they aren't doable we really should remove them from the tests
[08:01] <sil2100> Agreed
[08:18] <paride> gjolly, cpaelzer, hi, as mwhudso_n said the respin is only for the live-server images, to fix https://bugs.launchpad.net/ubuntu-power-systems/+bug/1969393
[08:28] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Jammy Final] has been marked as ready
[08:29] <waveform> sil2100, bdmurray, I'm unconvinced we should remove them; while I agree it's not great that there's several we currently can't test due to lacking hardware (mostly CM4 variants) I'd rather have documented that we *should* test but *can't*, rather than pretend we don't *need* to test them
[08:48] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Jammy Final] has been marked as ready
[09:10] <sil2100> waveform: regarding that, I see a raspi2 test case - is that testable?
[09:11] <waveform> sil2100, yes -- I'll try and get to that this morning
[09:11] <sil2100> Thanks ;)
[09:18] <bdmurray> waveform: they should at least move out of mandatory
[09:22] <waveform> bdmurray, I don't particularly like that idea either (because again, it doesn't represent what we'd ideally be doing), but if so then the list of CM4s we can't currently test is: all the CM4 stuff for the desktop (none of ours have sufficient eMMC storage to hold the desktop image), and all the CM4 stuff for the server *except* the 4GB models (both jawn-smith and I have 4GB models ... hmmm, just noticed the CM4 8GB model is actually missing on
[09:22] <waveform>  the server ISO test list, that's odd)
[09:34] <LocutusOfBorg> bot on ubuntu-release-party is dead...
[10:03] <ogra> LocutusOfBorg, i pinged in #ubuntu-irc ...
[10:03] <ogra> they should be able to sort it
[10:36] -queuebot:#ubuntu-release- Unapproved: gdm3 (jammy-proposed/main) [42.0-1ubuntu6 => 42.0-1ubuntu7] (desktop-core)
[10:46] <jbicha> sil2100: as discussed earlier in the week, please review gdm3 as a 0-day candidate
[10:51] -queuebot:#ubuntu-release- Builds: Ubuntu WSL [Jammy Final] has been updated (2201221921)
[11:00] <bdmurray> jbicha: does bug 1969524 need SRU'ing at all?
[11:05] -queuebot:#ubuntu-release- Unapproved: snapd (impish-proposed/main) [2.54.3+21.10.1ubuntu0.2 => 2.54.3+21.10.1ubuntu0.3] (desktop-core, ubuntu-server)
[11:06] -queuebot:#ubuntu-release- Unapproved: snapd (jammy-proposed/main) [2.55.3+22.04 => 2.55.3+22.04ubuntu1] (desktop-core, ubuntu-server)
[11:08] -queuebot:#ubuntu-release- Unapproved: gdm3 (jammy-proposed/main) [42.0-1ubuntu6 => 42.0-1ubuntu6.1] (desktop-core)
[11:10] <jbicha> bdmurray: no, that was a recent change in osinfo-db that had only been pushed to jammy. There is an underlying issue not in osinfo-db but this was an easy workaround
[11:19] <jbicha> please reject gdm3 42.0-1ubuntu6.1; we were overeager and uploaded the same fix twice. You can also reject gnome-weather 41.0-3ubuntu1 since I uploaded a better fix as ubuntu2
[11:23] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (jammy-proposed) [2.55.3+22.04ubuntu1]
[11:29] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (impish-proposed) [2.54.3+21.10.1ubuntu0.3]
[11:33] <bdmurray> jbicha: you didn't to bump the version number for gnome-weather
[11:35] <jbicha> I like using fresh version numbers. Is it annoying when version numbers are skipped?
[11:38] -queuebot:#ubuntu-release- Unapproved: rejected gdm3 [source] (jammy-proposed) [42.0-1ubuntu6.1]
[11:38] -queuebot:#ubuntu-release- Unapproved: rejected gnome-weather [source] (jammy-proposed) [41.0-3ubuntu1]
[11:40] <bdmurray> jbicha: I imagine avid changelog readers will wonder where ubuntu1 went
[11:41] <sil2100> waveform: any luck with the pi2 testing? ;)
[11:41] <jbicha> good point
[11:55] -queuebot:#ubuntu-release- Builds: Ubuntu WSL [Jammy Final] has been marked as ready
[12:01] <sil2100> \o/
[12:07] -queuebot:#ubuntu-release- New: accepted unicorn-hat-hd [source] (jammy-proposed) [0.0.4-0ubuntu1]
[12:07] -queuebot:#ubuntu-release- New: accepted unicorn-hat [arm64] (jammy-proposed) [2.2.3-0ubuntu1]
[12:07] -queuebot:#ubuntu-release- New: accepted unicorn-hat-mini [source] (jammy-proposed) [0.0.2-0ubuntu1]
[12:07] -queuebot:#ubuntu-release- New: accepted unicorn-hat [armhf] (jammy-proposed) [2.2.3-0ubuntu1]
[12:07] <waveform> sil2100, pi2 testing is done
[12:09] <plars> what was that? arm64 on your newer version of the pi2?
[12:11] <waveform> yes that's right -- worked out of the box (I *think* that's the first release where that happened -- we don't "officially" support arm64 on the pi2, but I like to include it in the test suite as it is a potentially important "enterprise" platform as it's easier to certify a board with no wifi/bt in certain conditions)
[12:11] -queuebot:#ubuntu-release- New binary: unicorn-hat-mini [arm64] (jammy-proposed/universe) [0.0.2-0ubuntu1] (no packageset)
[12:11] -queuebot:#ubuntu-release- New binary: unicorn-hat-mini [armhf] (jammy-proposed/universe) [0.0.2-0ubuntu1] (no packageset)
[12:11] <waveform> in the past it required some minor tinkering with the f-k database to specify the dtb for it, but now it "just works"
[12:11] <plars> waveform: if we don't officially support that, then should it be listed as a mandatory test?
[12:11] -queuebot:#ubuntu-release- New binary: unicorn-hat-hd [arm64] (jammy-proposed/universe) [0.0.4-0ubuntu1] (no packageset)
[12:11] <waveform> no, that one should almost certainly be "optional"
[12:12] <waveform> (no idea where that's altered though -- it's not in the source for the tests)
[12:12] -queuebot:#ubuntu-release- New binary: unicorn-hat-hd [armhf] (jammy-proposed/universe) [0.0.4-0ubuntu1] (no packageset)
[12:14] <bdmurray> waveform: if you send me an email I can sort it
[12:14] <bdmurray> waveform: I might lose track today
[12:15] <waveform> bdmurray, will do
[12:39] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Jammy Final] has been marked as ready
[12:39] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Jammy Final] has been marked as ready
[12:39] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Jammy Final] has been marked as ready
[12:39] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity riscv64 [Jammy Final] has been marked as ready
[12:39] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Jammy Final] has been marked as ready
[12:40] <bdmurray> waveform: What is the status of http://iso.qa.ubuntu.com/qatracker/milestones/432/builds/247134/testcases ? Can it be marked as ready?
[12:41] <waveform> bdmurray, yes
[12:41] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unmatched [Jammy Final] has been marked as ready
[12:42] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Jammy Final] has been marked as ready
[12:42] <rbasak> vorlon: I'm happy with the ua-tools upload for Jammy from an SRU perspective. However time for the usual QA by the ua-tools team is presumably impossible for a 0-day SRU. How should that work?
[12:42] <sil2100> waveform: ok, now final question for you for this release: can we mark the pi server images as ready? ;)
[12:42] <waveform> sil2100, yup
[12:42] <rbasak> Could we get it in jammy-proposed ASAP for example, so that they can start QA before release?
[12:42] <rbasak> eg. with a block-proposed tag
[12:43] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Jammy Final] has been marked as ready
[12:43] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Jammy Final] has been marked as ready
[12:53] <rbasak> Maybe a question for sil2100 if vorlon is still in his usual timezone
[12:53] <rbasak> ^
[12:54] <sil2100> Let me get back to you later after we're done with the releasey bits
[12:56] <bdmurray> rbasak: What does 0-day SRU mean to you?
[12:57] <rbasak> bdmurray: that's probably worth me clarifying, so I'm glad you're asking :)
[12:57] <rbasak> To me it's something placed in the -updates pocket on or around release time.
[12:57] <rbasak> Rather than the release pocket.
[12:57] <rbasak> The rest I'm unclear about - like who reviews (I'm told SRU team now though!) and how QA is done.
[12:58] <rbasak> I'd like for the final binaries to be tested, but that needs them built, and if we want them in -updates around release time, then I want the binaries in advance to be able to QA them I think.
[12:58] <rbasak> That's what I'm puzzled about.
[13:00] <bdmurray> Having things in -updates on or around release time is quite exceptional. As an example we just let snapd into -proposed now because it can completely break upgrades to Jammy. I'm not sure ua-tools fits into that category.
[13:01] <bdmurray> Even then we are planning on leaving snapd in -proposed until Monday and not enabling upgrades until after it is in -updates.
[13:01] <rbasak> bdmurray: I don't believe this was covered in my SRU team onboarding :-P
[13:01] <rbasak> OK so for ua-tools, you're proposing to accept into proposed after Jammy release, and then for it to wait until some time next before hitting updates?
[13:01] <rbasak> lucasmoura: does that work for you?
[13:02] <rbasak> (I think maybe 0-day is a misnomer then and that's the cause of my misunderstanding)
[13:03] <rbasak> some time next *week*
[13:03] <lucasmoura> @rbasak, just to confirm, the package would wait the 7 days before going to updates ?
[13:03] <rbasak> I think the 7 day rule is going to probably be flexed. But the exact delay is what I think we're discussing.
[13:04] <bdmurray> It doesn't have to wait 7 days if there is a burning reason for it to be out sooner.
[13:04] <bdmurray> Yes, I think 0-day SRU has become an overloaded term.
[13:04] <lucasmoura> I think the burning reason is just that we want to advertise the real-time kernel service as soon as we can
[13:07] <rbasak> So I had thought that what we'd all been talking about was releaseing ua-tools into -updates at around release time. It seems that was a misunderstanding. I guess we therefore now need to discuss and conclude what are expectations are on when it'll be acceptable to release to -updates, and how we're going to QA the final binaries in advance of that.
[13:07] <rbasak> what *our* expectations are.
[13:07] -queuebot:#ubuntu-release- Unapproved: systemd (impish-proposed/main) [248.3-1ubuntu8.5 => 248.3-1ubuntu8.6] (core, i386-whitelist)
[13:08] <rbasak> From an SRU review perspective, I reviewed the changes and I think they look benign from a packaging perspective. I think it's appropriate to mitigate regression risk using the ua-tools existing QA process with nothing additional to add.
[13:09] <rbasak> Though of course there's always risk of screwing up in an unexpected way, so I appreciate the caution in not wanting to regress users immediately after release, etc.
[13:09] <rbasak> Beyond that, I think I can leave the risk/reward between the lucasmoura (and his colleagues) and the release team to discuss?
[13:10] <paride> I just sponsored the ubuntu-advantage-tools upload to jammy
[13:10] <rbasak> Thanks!
[13:10] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (jammy-proposed/main) [27.7~22.04.1 => 27.8~22.04.1] (core)
[13:10] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Jammy Final] has been marked as ready
[13:10] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Jammy Final] has been marked as ready
[13:10] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Jammy Final] has been marked as ready
[13:10] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Jammy Final] has been marked as ready
[13:10] -queuebot:#ubuntu-release- Builds: Ubuntu Base riscv64 [Jammy Final] has been marked as ready
[13:10] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Jammy Final] has been marked as ready
[13:11] <rbasak> On my QA point above, I intend to imply that the built binaries should be tested in the normal way, which needs some delay between the queue accept and the release to -updates
[13:11] <lucasmoura> rbasak, yes, I agree. And regarding QA we can run all of our Jammy specific tests for this release before uploading to updates if needed
[13:11] <lucasmoura> But I agree that someone from release team should be onboard with that
[13:15] -queuebot:#ubuntu-release- Unapproved: systemd (focal-proposed/main) [245.4-4ubuntu3.16 => 245.4-4ubuntu3.17] (core, i386-whitelist)
[13:23] <bdmurray> jbicha: Do you know the status of the fix for bug 1969619? That's something that is 0-day appropriate.
[13:24] <jbicha> bdmurray: the fix is in jammy-proposed. Is there anything else you need?
[13:24] <bdmurray> Oh, I didn't realize it was in -proposed.
[13:25] <didrocks> bdmurray: sil2100: WSL image is ready to be published to microsoft store, tell me when you push the button on Ubuntu so that I can do the same on the Windows Store
[13:25] <sil2100> \o/
[13:25] <sil2100> didrocks: excellent! Thanks, we'll do!
[13:25]  * didrocks didn’t expect Microsoft certifcation to take hours instead of days for once :)
[13:27] <jbicha> bdmurray: I think it was suggested the gnome-control-center fix could be pushed to the -security pocket but I don't know what workflow that would need today
[13:33] <toabctl> sil2100, bdmurray please also ping virtus or me when we can release. then we'll push for the dockerhub jammy base container update
[13:40] <xnox> toabctl:  cpc-team contact assigned for this release is monitoring things....... you can check with them.
[13:40] <toabctl> ack
[13:40] <Beret> ack
[13:40] <Beret> (sorry, couldn't help trolling xnox)
[13:40] <xnox> Beret:  hahahhahahahhahahhahahhahahahhahahahhahahahhaha
[13:40] <Beret> :)
[13:40] <xnox> Beret:  love you too =)
[13:40] <bdmurray> Beret: that'll add 10 minutes to the release time
[13:41] <Beret> not the first time I've broke things
[13:42] <sil2100> ;)
[13:55] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Jammy Final] has been marked as ready
[13:58] <sil2100> \o/
[13:58] <sil2100> Starting the publishing!
[14:00] <dbungert> :tada:
[14:01] <jchittum> CPC is kicking
[14:06] <didrocks> publishing WSL!
[14:13] -queuebot:#ubuntu-release- New: accepted unicorn-hat-hd [arm64] (jammy-proposed) [0.0.4-0ubuntu1]
[14:13] -queuebot:#ubuntu-release- New: accepted unicorn-hat-mini [arm64] (jammy-proposed) [0.0.2-0ubuntu1]
[14:13] -queuebot:#ubuntu-release- New: accepted unicorn-hat-hd [armhf] (jammy-proposed) [0.0.4-0ubuntu1]
[14:13] -queuebot:#ubuntu-release- New: accepted unicorn-hat-mini [armhf] (jammy-proposed) [0.0.2-0ubuntu1]
[14:20] <madhens> I always feel like I'm in NASA mission control when I'm here on release day :)
[14:21] <bittin> :p
[14:21] <ogra> madhens, but you are not catherding your community in #ubuntu-release-party yet !
[14:22] <bittin> ogra: has the party started?
[14:22] <ogra> check yourself ? 😉
[14:23] <bittin> sure
[14:24]  * virtus is now woky
[14:26] <Eickmeyer> madhens: I've got 4 monitors with several windows open, a few tabs, and ready to hit "send" and "publish" on a few things once I see some "green lights" that I'm looking for, so it's very much mission control here right now. XD
[14:27] <madhens> Eickmeyer I wish I had four monitors! I'm making do with 2.
[14:29] <sil2100> didrocks: hey! So we're in the middle of releasing - the mirror syncs are still not enabled, but will enable those soon
[14:29] <sil2100> Once those are enabled, it will take like 1-1.5h for the mirrors to be syncs
[14:29] <sil2100> *synced
[14:30] <madhens> \o/
[14:33] <estan> \o/ release that thing. release that thing like there's no tomorrow.
[14:38] <didrocks> sil2100: ack, similar time for the Windows Store to publish the image, so I guess we are in sync :)
[14:42] <estan> is the mirror sync status available publicly somewhere btw? if i'm two seconds late in upgrading, i'll feel like i'm running horribly outdated software on my computer.
[14:42] <madhens> estan we'll be making the big Tweet once most of the mirrors are synced.
[14:44] <estan> excellent.
[14:49] <bdmurray> estan: upgrades will not be enabled for a couple of days though
[14:49] <bittin> not until 4th August
[14:51] <estan> ah yes, but if i'm eager i can pass -d to do-release-upgrade right?
[14:52] <bittin> yeah
[14:52] <estan> anyone know approx how long after release the docker image on docker hub is updated btw?
[14:52] <madhens> estan also feel free to join us in #ubuntu-release-party !
[14:54] <estan> ah, will do once i'm home. i don't run an IRC bouncer or screen session for IRC nowadays so will have to disconnect when i leave today. just came here to snoop a little :)
[14:55] <sil2100> didrocks: yay! Ok, so please continue o/ We're now running the mirror prober
[14:55] <bittin> o/ :)
[14:55] <didrocks> yeah, it’s all done, just waiting on propagation
[14:59] <bdmurray> You can use -d right now
[14:59] <madhens> didrocks Can you ping me here or  on MM so I can let marketing know to make the Tweet when enough of the mirrors are synced?
[14:59] <bdmurray> lucasmoura: there isn't SRU information in https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1968067
[15:04] <paride> bdmurray, the SRU bug is https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1969125
[15:08] <sil2100> laney: hey hey! A release-team-comember question - we're running the mirror prober now, and I didn't see the cdmirrors list going down
[15:08] <sil2100> It's all the same - is that normal? Previously it usually dropped to 0 and then was going up when when mirrors were getting in sync
[15:11] <JimBuntu> lotuspsychje! How dare you?! ;p
[15:12] <Eickmeyer> JimBuntu: Sure you got the right channel?
[15:12] <didrocks> madhens: I guess you wanted to ask sil2100 about this :) ^
[15:12] <paride> lucasmoura, well what bdmurray means AIUI is that as LP: #1968067 is mentioned in d/changelog, and therefore bug state will be updated by the upload, that bug needs the SRU info and a test case for verification
[15:13] <madhens> Haha sorry didrocks
[15:13] <sil2100> laney: ok, nvm, I see the mirrors dropping, Colin said it might have been the old run still in progress
[15:16] <bdmurray> lucasmoura: Yes, it ended up in Launchpad-Bugs-Fixed
[15:17] <laney> sil2100: yeah. IIRC it wasn't very easy to view the logs of that cron job
[15:18] <sil2100> laney: happy release daaay!
[15:19] <laney> it'd be better if you could, then we could track mirrors being removed and slowly readded
[15:19] <laney> yes :>
[15:19] <laney> 20220419
[15:19] <laney> it's some kind of miracle!
[15:19] <lucasmoura> @bdmurray, noted, we usually update the SRU bugs once we have the packages in proposed. Would providing the test results for the package we have in our staging ppa enough for this ?
[15:20] <bdmurray> sil2100: Could you remove grub-customizer 1969793 ?
[15:20] <lucasmoura> Because we already have automated tests for the upgrade scenarios that the bug is mentioning
[15:21] <bdmurray> lucasmoura: What I'm saying is the bug does not have the SRU template in it i.e. how will it be tested?
[15:21] <bdmurray> sil2100: bug 1969793
[15:21] <lucasmoura> Oh okay, fair enough. Updating it now
[15:28] <xnox> vorlon:  it appears to me that the upload of ubuntu-advantage-tools in jammy unapproved adds a beta feature for jammy; but it still declares that livepatch is not available for jammy
[15:29] <xnox> vorlon:  which i think may affect launching jammy ubuntu-pro images
[15:29] -queuebot:#ubuntu-release- Unapproved: ubiquity (jammy-proposed/main) [22.04.15 => 22.04.16] (ubuntu-desktop)
[15:35] <lucasmoura> @xnox, livepatch is indeed working on jammy. It was being blocked directly on the livepatch snap, but that was fixed yesterday
[15:36] <orndorffgrant> xnox: livepatch is declared as available for jammy by the contract server as of yesterday. You may be referring to our integration tests, which weren't yet updated to reflect that, but that doesn't affect the installed package
[15:39] <xnox> lucasmoura:  orndorffgrant: finishing VM install to verify that.
[15:39] <jchittum> we're just a little confused by the diff
[15:41] <orndorffgrant> I completely understand the confusion from the diff. This 27.8 was uploaded before the contract server started advertising esm/livepatch for jammy, which is why it has stale values.
[15:42] <xnox> orndorffgrant:  and it is expected that the new URLs mentioned in that upload, are 404 for now/still.
[15:42] <xnox> right?
[15:42] <xnox> Canonical livepatch enabled. so looks good for me indeed via my personal subscription.
[15:42] <lucasmoura> @bdmurray, I have added the SRU template for the bug you mentioned
[15:43] <orndorffgrant> We just escalated the url issue internally, and have been promised "it's scheduled to go live with the release"
[15:57] <xnox> ok
[16:26] <jchittum> release is now. as in Pro images are hitting the clouds now
[16:52] <xnox> vorlon:  the new feature of ubuntu-advantage-tools does not at all work for me, and results in an unbootable machine. I would pause accepting that upload until that is OK'ed or resolved somehow.
[16:54] <vorlon> xnox: because it's not signed, or because it fails to boot even when secureboot is disabled?
[17:14] <madhens> sil2100 is Marketing good to go on the Tweet and everything else?
[17:27] -queuebot:#ubuntu-release- Unapproved: evolution (jammy-proposed/universe) [3.44.0-1 => 3.44.0-1ubuntu1] (ubuntu-mate, ubuntukylin)
[17:27] <teward> *summons sil2100*
[17:27] <teward> *gives sil2100 a beer*
[17:30] <madhens> Okay, I saw the e-mail hit, so I gave marketing the green light. :)
[17:30] <madhens> Heya teward !
[17:30] <madhens> *gives teward a coffee*
[17:30] <teward> madhens: o/
[17:30] <teward> *pours the coffee into the magic liquor maker and out comes irish coffee*
[17:33] <xnox> vorlon:  just unsigned
[18:01] <Beret> Congrats all
[20:29] <lucasmoura> @xnox, vorlon We have updated the ua version 27.8 to address the changes we discussed today
[20:29] <lucasmoura> The MRs are also all updated
[20:30] <lucasmoura> I think we can release that new version into jammy proposed, but let us know if there is more we need to address here
[20:34] <vorlon> lucasmoura: I don't see this as an upload in the queue currently?
[20:35] <lucasmoura> No, this new version has not been uploaded to the queue yet
[20:35] <lucasmoura> usually, @paride performs that step for us, but he is already EOD
[20:35] <lucasmoura> Do you know someone that can upload the new package into the queue for us ?
[20:39] <vorlon> lucasmoura: in principle it could be sponsored by anyone in the ubuntu-sponsors team; I think sponsors are going to be scarce though, on account of this being release day
[20:39] -queuebot:#ubuntu-release- Unapproved: rejected ubuntu-advantage-tools [source] (jammy-proposed) [27.8~22.04.1]
[20:39] -queuebot:#ubuntu-release- Unapproved: gtksourceview5 (jammy-proposed/universe) [5.4.0-1 => 5.4.1-0ubuntu1] (no packageset)
[21:12] <lucasmoura> @vorlon, sergiodj just sponsored the package for us
[21:12] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (jammy-proposed/main) [27.7~22.04.1 => 27.8~22.04.1] (core)
[21:12] <sergiodj> there it is
[22:59] <jchittum> at this point clouds are mostly there. Azure has a long publication process (upwards of 36 hours). AWS Marketplace (for the free stuff!) will be done probably in the AM hours of EU tomorrow.
[22:59] <jchittum> free cloud images on AWS, GCE, and on cloud-images.ubuntu.com are all released
[22:59] <jchittum> even have AWS Govcloud!