[00:13]  * Eickmeyer wonders if schopin forgot to @pilot out.
[00:26] <Bert> kanashiro: this is marvelous news! :D Weird that launchpad hasn't emailed me about it. It's bed time here (actually very late already) but I will have a look tomorrow
[00:26] <Bert> thx a ton for all the effort already :)
[00:26] <kanashiro> Bert yw :)
=== guiverc2 is now known as guiverc
=== guiverc2 is now known as guiverc
[09:07] <Bert> kanashiro: super weird, I just got an email about your update on launchpad from hours ago
[09:08] <Bert> looks like it was generated with a delay and then somehow got stuck inside launchpad for a few hours too
[09:08] <Bert> very unusual
[09:08] <Bert> not sure if we should let them know about that?
[09:11] <Bert> kanashiro: is this the moment we have to add an SRU team or team member to the bug to get to the next step? or what actions can we take to help things progress?
[09:12] <Bert> we can schedule maintenance to attempt an upgrade from 20.04 to 22.04 once the packages are available through do-release-upgrade, but I expect we're still very far from that step
[11:31] <cjwatson> Bert: It was due to a kernel team script swamping notifications for a particular bug with several thousand switches of status back and forth in quick succession, resulting in an enormous notification queue.
[11:32] <cjwatson> I tried to cut it short yesterday but apparently only partially succeeded, and then had some other urgent fires to put out so couldn't dig further.
[11:32] <cjwatson> But it's cleared now.
[11:43] <Bert> cjwatson: aha, that explains! Glad to hear it's resolved though, that's the most important thing
[11:43] <Bert> much easier than chasing some edge case bug :)
[12:57] <mateus-morais> kanashiro: sorry, just seeing your ping now. I'll take a look at your comment today
=== lan3y is now known as laney
[18:15] <GunnarHj> enr0n: Did you ping anybody in the release team so they can approve it? I mean so it won't be hanging over the weekend...
[18:17] <enr0n> GunnarHj: just did
[18:17] <GunnarHj> Great!