[03:15] -queuebot:#ubuntu-release- Unapproved: uvtool (hirsute-proposed/universe) [0~git169-0ubuntu1 => 0~git169-0ubuntu2] (no packageset)
[03:17] -queuebot:#ubuntu-release- Unapproved: accepted uvtool [source] (hirsute-proposed) [0~git169-0ubuntu2]
[03:28] -queuebot:#ubuntu-release- Unapproved: unity-api (hirsute-proposed/universe) [8.7+17.04.20170404-0ubuntu4 => 8.7+17.04.20170404-0ubuntu5] (no packageset)
[03:29] -queuebot:#ubuntu-release- Unapproved: accepted unity-api [source] (hirsute-proposed) [8.7+17.04.20170404-0ubuntu5]
[05:16] <vorlon> apw: I am unclear how this happened, but fsprotect is newly uninstallable in hirsute because it depends on the aufs-dkms virtual package which is no longer being provided.  https://people.canonical.com/~ubuntu-archive/proposed-migration/hirsute_uninst.txt  Should we be dropping fsprotect due to its dependency?
[05:43] -queuebot:#ubuntu-release- Unapproved: gnome-system-monitor (hirsute-proposed/main) [40.0-1 => 40.0-2] (ubuntu-desktop) (sync)
[07:07] -queuebot:#ubuntu-release- Unapproved: scrappie (hirsute-proposed/universe) [1.4.2-4 => 1.4.2-7] (no packageset) (sync)
[07:07] -queuebot:#ubuntu-release- Unapproved: accepted scrappie [sync] (hirsute-proposed) [1.4.2-7]
[07:09] -queuebot:#ubuntu-release- Unapproved: nvidia-cuda-toolkit (hirsute-proposed/multiverse) [11.2.1-2 => 11.2.2-1] (no packageset) (sync)
[07:10] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-cuda-toolkit [sync] (hirsute-proposed) [11.2.2-1]
[07:11] <luna> morning
[07:51] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (groovy-proposed) [1.190.4]
[08:01] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (focal-proposed) [1.187.11]
=== Awayney is now known as Laney
[08:02] <apw> vorlon, likely, i'll poke someone to have a look-see
[08:03] -queuebot:#ubuntu-release- Unapproved: rejected fwupd-signed [source] (bionic-proposed) [1.10~ubuntu18.04.5]
[08:03] -queuebot:#ubuntu-release- Unapproved: rejected fwupd [source] (bionic-proposed) [1.2.13-0~18.04.1]
[08:34] -queuebot:#ubuntu-release- Unapproved: accepted pciutils [source] (focal-proposed) [1:3.6.4-1ubuntu0.20.04.1]
[09:00] <didrocks> doko: as you released an upstream version for ubuntu-report, mind doing an upstream PR against the github repo? Thanks
[09:01] <luna> New test daily images out 06 to test
[09:09] <RikMills> ubuntu-archive: please reject qbittorrent from hirsute NEW
[09:20] <doko> didrocks: now filed 1922685
[09:22] <didrocks> doko: sorry if I was unclear, I was suggesting a pull request against https://github.com/ubuntu/ubuntu-report/pulls
[09:26] <doko> didrocks: why do you talk about an upsteam version, the package is packaged as "native"
[09:28] <didrocks> doko: well, it’s a new .z version, so it fits into the upstream repo (which is native as it has a debian/ directory)
[09:28] -queuebot:#ubuntu-release- New: rejected qbittorrent [source] (hirsute-proposed) [4.2.5-0.1build]
[09:29] <apw> RikMills, ^
[09:29] <RikMills> thanks
[09:29] <ricotz> hello :), I wondering about https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640 -- is this meant to be fixed? afaict I am still seeing this problem -- https://paste.debian.net/plain/1192470
[09:29] <ubot5> Ubuntu bug 1920640 in ubuntu-keyring (Ubuntu Hirsute) "EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) <email address hidden>" [Critical,Fix released]
[09:34] -queuebot:#ubuntu-release- Unapproved: apt (hirsute-proposed/main) [2.2.2 => 2.2.2ubuntu1] (core, i386-whitelist)
[10:02] <Laney> juliank: looks like maybe port leakage on bos02
[10:05] -queuebot:#ubuntu-release- Unapproved: accepted apt [source] (hirsute-proposed) [2.2.2ubuntu1]
[10:06] <Laney> did some cleanup, maybe it'll start behaving better now
[10:07] <juliank> Laney: hopefully
[10:07] <doko> what about these boost* tests started on Apr 2?
[10:08] <doko> also chiark-tcl
[10:08] <juliank> doko: they were not started on apr 2, but submitted
[10:10] <juliank> doko: they were not able to run so far
[10:11] <doko> that's odd, because 1000+ triggered tests were able to run after these
[10:11] <juliank> they'ven ot been lucky and always stumbled
[10:11] <doko> then lets wait
[10:11] <juliank> everytime they tried to run, they could not find free ports in the cloud
[10:12] <juliank> I should revert my workaround to reuse security groups now
[10:12] <juliank> IS believes they cleaned up all the stuck open ports
[10:12] <Laney> this script is deleting LOTS of stuff
[10:12] <Laney> it's still running
[10:13] <Laney> honestly, can't leave this cloud for a minute :p
[10:13] <juliank> Laney: the problem (if it's the one from backlog) is the inline "if nova list" which takes ages
[10:13] <Laney> yeah
[10:13] <Laney> but it usually cleans up like 10 max
[10:13] <juliank> Laney: Anyhow, I should revert my reuse security group workaround so our workers delete and recreate groups again
[10:14] <Laney> and this is way beyond that now
[10:14] <Laney> cool
[10:14] <Laney> ah there it's done
[10:14] <juliank> Because that failed due to the stuck ports before
[10:14] <juliank> (the deleting)
[10:14] <Laney> was this all because of that outage like 10 days ago?
[10:14] <juliank> but then the workers started with the workaround, but individual runs could fail with port quota exceeded
[10:15] <juliank> Laney: believe so yes, and it's not resolved yet entirely, lots of ports are stuck in deleting state the ticket says
[10:15] <juliank> https://portal.admin.canonical.com/C130276
[10:15] <Laney> urgh I have to 2FA everywhere now
[10:16] <Laney> 369677
[10:16] <Laney> lol
[10:16] <Laney> quick, compromise my account in the next 10 seconds
[10:16] <apw> a good job those only last 30s
[10:16] <Laney> I'm not fit to be back at work
[10:17] <Laney> juliank: some in bos01 too it seems, guess I should do the other regions
[10:17]  * Laney does London too
[10:18] <Laney> yeah ok, this is a good idea
[10:19] <juliank> Laney: I disabled security group reuse and SIGHUPed the workers so we'll see failing worker units again now
[10:19] <juliank> instead of infinite retries due to exceeded ports
[10:19] <Laney> nod
[10:21] -queuebot:#ubuntu-release- Unapproved: zsys (hirsute-proposed/main) [0.5.7 => 0.5.8] (ubuntu-desktop)
=== didrocks999 is now known as didrocks
[10:34] -queuebot:#ubuntu-release- Unapproved: rejected zsys [source] (hirsute-proposed) [0.5.8]
[10:34] -queuebot:#ubuntu-release- Unapproved: zsys (hirsute-proposed/main) [0.5.7 => 0.5.8] (ubuntu-desktop)
[10:37] -queuebot:#ubuntu-release- Unapproved: ubiquity (hirsute-proposed/main) [21.04.13 => 21.04.14] (desktop-core)
[10:42] <juliank> Laney: Maybe we should write a port cleanup python script and run that daily too :D
[10:43] <Laney> I thought about doing it from the cleanup script
[10:43] <juliank> +1
[10:43] <Laney> but it's really racy
[10:43] <Laney> need to figure out how to eliminate or at least minimise that
[10:43] <juliank> we're exceeding our cpu core quota on lcy it just said
[10:44] <Laney> yeah that happens with big tests
[10:44] <Laney> we don't shut off 3 small ones so they try to run and get denied
[10:44] <Laney> it should sort itself out with retrying
[10:44] <juliank> right
[10:44] <juliank> well in this case, the reverse
[10:44] <juliank> :D
[10:45] <juliank> (want 1 core, but 50 of 50 used because big test already running :D)
[10:45] <Laney> yeah same problem happens both ways around
[10:45] -queuebot:#ubuntu-release- Unapproved: xfwm4 (focal-proposed/universe) [4.14.1-0ubuntu1 => 4.14.5-1ubuntu0.20.04.1] (i386-whitelist, ubuntustudio, xubuntu)
[10:45] <Laney> 49 small tests, or 12.5 big ones
[10:45] <Laney> or any combination in between, you can get quota issues
[10:45] <juliank> Wondering if there should be one quota aware worker controller that just spawns ephemeral units for running a single test
[10:46] <juliank> to avoid quota issues :D
[10:46] <Laney> heh
[10:47] <Laney> you could have autopkgtest(-cloud) check the usage before trying to start instances
[10:47] <Laney> it is possible to know that it will fail
[10:47] <Laney> but that again is racy :(
[10:47] <juliank> the problem with retries is that other stuff that's lower on the queue runs earlier
[10:47] <juliank> which is awkward as we saw with the large ruby stuff
[10:48] <juliank> um
[10:48] <juliank> boost*
[10:48] <juliank> but once we have multiple workers that will be even harder, so meh
[10:48] <Laney> it's basically too naive the way we do it really
[10:48] <Laney> kinda just about works with our scale
[10:48] <Laney> but we're not far off where you want to manage this smarter It hink
[10:49] <juliank> You need worker-controller-meta -> worker-controller -> worker
[10:49] <Laney> /o\
[10:49] <juliank> So then you run two controllers and one meta controller
[10:49] <apw> you could just have a quota unit allocator, which you ask for N elements from over amqp
[10:49] <juliank> the meta controller is really just load balancing between them
[10:49] <Laney> dear me
[10:50] <Laney> I would think that the workers would somehow need to be aware of each other
[10:50] <apw> and let its queuing handle ordering from the workers
[10:50] <Laney> and think like, no, I'll wait with this large test in my hands, let the others do some small ones now
[10:50] <juliank> It could check before taking the item from the queue
[10:50] <Laney> and then later they're like ok thanks, it's your turn, we will wait a bit
[10:50] <juliank> I think that would make things nicer
[10:51] <juliank> It would behave similar to now, except that stuff doesn't get reshuffeled
[10:51] <juliank> as mentioned, it's a bit of a race though
[10:51] <Laney> it's kinda desirable that the workers hold onto their requests
[10:51] <Laney> it helps avoid starvation in some circumstancves
[10:52] <Laney> the tmpfail handling takes advantage of that too, it means other requests can make progress
[10:54]  * Laney checks on prod-proposed-migration
[11:04] -queuebot:#ubuntu-release- Unapproved: flash-kernel (hirsute-proposed/main) [3.104ubuntu2 => 3.104ubuntu3] (core)
[11:29] <juliank> Laney: It does not seem super happy still: https://paste.ubuntu.com/p/MKwGWScVZV/
[11:30] <juliank> Laney: I deleted all unused ports on bos01, but did not manage to get autopkgtest@bos01-ppc64el-7.service working agai
[11:30] <juliank> n
[11:35] <juliank> I have no idea how to figure out which ports or servers belong to that security group, it's madness
[11:43] <Laney> juliank: I ran cleanup-instances and it is deleting LOTS of stuff from today
[11:43] <Laney> why is that?
[11:44] <juliank> Laney: something is broken somewhere
[11:44] <juliank> Laney: I also see failures autopkgtest@bos02-arm64-12
[11:44] <juliank> tr: extra operand 'x'
[11:44] <juliank> in nova cleanup script
[11:44] <juliank> Laney: But I believe we might have deleted to many ports or stuff, I don't know
[11:44] <Laney> could be
[11:45] <Laney> anyway at least some of these secgroups were because of those orphaned instances
[11:47] <juliank> Laney: everything seems to fail in setup script now with the tr 'x' error
[11:47] <Laney> never seen that before
[11:47] <Laney> what does it mean?
[11:47] <juliank> Laney: it's not clear
[11:47] <Laney> is it all clouds or just one?
[11:47] <juliank> https://paste.ubuntu.com/p/wfkrG29cgM/
[11:48] <juliank> Laney: both bos ones at least
[11:48] <juliank> lcy too
[11:48] <juliank> there is like a failure per second or so
[11:49] <Laney> bah
[11:49] <Laney> gimme 2 minutes
[11:50] <Laney> so good to be back at work :D
[11:54] -queuebot:#ubuntu-release- New binary: linux-signed-oracle [amd64] (xenial-proposed/main) [4.15.0-1069.77~16.04.1] (kernel)
[11:58] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle [amd64] (xenial-proposed) [4.15.0-1069.77~16.04.1]
[12:03] <Laney> juliank: see the diff in autopkgtest/
[12:03] <Laney> any idea why that might have broken?
[12:09] <juliank> Laney: weird, did we switch shells or something?
[12:10] <juliank> jak@jak-x230:~:master$ echo AB | tr '[[:upper:]]' '[[:lower:]]'
[12:10] <Laney> hope not ...
[12:10] <juliank> ab
[12:10] <juliank> jak@jak-x230:~:master$ echo AB | tr [[:upper:]] [[:lower:]]
[12:10] <juliank> dd
[12:10] <juliank> jak@jak-x230:~:master$
[12:10] <juliank> That said
[12:11] <juliank> $ echo tr [[:upper:]] [[:lower:]]
[12:11] <juliank> tr [[:upper:]] d
[12:11] <juliank> what is going on aargh
[12:11] <juliank> why is shell so cruel
[12:12] <juliank> $ echo tr [[:upper:]] [[:lower:]]
[12:12] <juliank> tr [[:upper:]] x
[12:13] <Laney> what
[12:13] <juliank> $ echo [[:lower:]]
[12:13] <juliank> x
[12:13] <juliank> what?
[12:13] <cjwatson> unquoted that's going to depend on the contents of your current directory, surely
[12:14] <juliank> cjwatson: oh I see it expands to a file in pwd, if there is one with a single lowercase character
[12:14] <juliank> Laney: ^
[12:15] <juliank> I deleted the single letter files now :D
[12:15] <cjwatson> ... not exactly the right fix :)
[12:18] <Laney> what shell thing is happening there?
[12:18] <Laney> sorry I feel mildly dense but I'm not seeing something :p
[12:19] <cjwatson> [...] may be expanded by the shell.  you want it not to be because you want it to be interpreted by tr instead, so it must be quoted.
[12:19] <Laney> ok I don't know about shells expanding [] I think
[12:19] <cjwatson> they're just kinds of globs
[12:20] <Laney> OH!
[12:20] <cjwatson> but it's confusing because by default the shell expands patterns that don't match any files to themselves
[12:20] <cjwatson> so you only notice if your cwd contains files that match the patterns in question
[12:21] <cjwatson> same way unquoted ? would expand to any single-character file names in your cwd if they exist, but otherwise to ?
[12:21] <cjwatson> one of the many landmines in sh
[12:22] <Laney> I didn't know about classes in globs I think
[12:22] <Laney>                      Within [ and ], character classes can be specified using the syntax [:class:], where class is one of the following classes defined in the POSIX standard:
[12:22] <Laney>                      alnum alpha ascii blank cntrl digit graph lower print punct space upper word xdigit
[12:23] <cjwatson> even if that weren't the case, you'd still have a similar landmine, just restricted to files with names '[', ':', 'l', 'o', 'w', 'e', 'r', or ']' :-)
[12:27] <Laney> heh
[12:27] <Laney> I might have stood a chance of figuring that one out
[12:29] -queuebot:#ubuntu-release- Unapproved: pygments (hirsute-proposed/main) [2.7.1+dfsg-2 => 2.7.1+dfsg-2ubuntu1] (i386-whitelist, ubuntu-server)
[12:31] -queuebot:#ubuntu-release- Unapproved: barbican (hirsute-proposed/main) [2:12.0.0~rc1-0ubuntu2 => 2:12.0.0~rc2-0ubuntu1] (openstack)
[12:31] -queuebot:#ubuntu-release- Unapproved: octavia (hirsute-proposed/universe) [1:8.0.0~rc1-0ubuntu1 => 1:8.0.0~rc2-0ubuntu1] (openstack)
[12:42] <Laney> juliank: it's looking better with ports now, still a few broken though
[12:42] <Laney> going to lunch so if you can look at that please do
[12:49] <RikMills> sil2100: I have a KDE plasma bugfix and translation update release to do in bileto later. I want to just build the whole stack with the new tars, even for the few that the only change is a version bump. I hope that is ok?
[12:49] <RikMills> for hirsute
[12:50] -queuebot:#ubuntu-release- Unapproved: python-django (hirsute-proposed/main) [2:2.2.19-1 => 2:2.2.19-1ubuntu1] (no packageset)
[13:04] <juliank> Still down seem to be autopkgtest@bos01-ppc64el-7.service, autopkgtest@bos01-ppc64el-14.service, autopkgtest@bos01-ppc64el-15.service, autopkgtest@bos02-ppc64el-5.service
[13:05] <juliank> Still something stuck in the cloud somewhere that prevents security group deletion
[13:05] <juliank> It's not unused instances
[13:11] -queuebot:#ubuntu-release- Unapproved: python3.10 (hirsute-proposed/universe) [3.10.0~a4-2 => 3.10.0~a7-1ubuntu1] (i386-whitelist)
[13:11] -queuebot:#ubuntu-release- Unapproved: accepted python3.10 [source] (hirsute-proposed) [3.10.0~a7-1ubuntu1]
[13:16] -queuebot:#ubuntu-release- Unapproved: procps (focal-proposed/main) [2:3.3.16-1ubuntu2 => 2:3.3.16-1ubuntu2.1] (core, i386-whitelist)
[13:16] -queuebot:#ubuntu-release- Unapproved: procps (groovy-proposed/main) [2:3.3.16-5ubuntu2 => 2:3.3.16-5ubuntu2.1] (core, i386-whitelist)
[13:24] -queuebot:#ubuntu-release- Unapproved: python3-stdlib-extensions (hirsute-proposed/main) [3.9.2-1ubuntu1 => 3.9.4-0ubuntu1] (core, i386-whitelist)
[13:25] -queuebot:#ubuntu-release- Unapproved: accepted pygments [source] (hirsute-proposed) [2.7.1+dfsg-2ubuntu1]
[13:25] -queuebot:#ubuntu-release- Unapproved: yelp (focal-proposed/main) [3.36.0-1 => 3.36.2-0ubuntu1] (ubuntu-desktop)
[13:26] -queuebot:#ubuntu-release- Unapproved: accepted barbican [source] (hirsute-proposed) [2:12.0.0~rc2-0ubuntu1]
[13:26] -queuebot:#ubuntu-release- Unapproved: accepted python-django [source] (hirsute-proposed) [2:2.2.19-1ubuntu1]
[13:26] -queuebot:#ubuntu-release- Unapproved: accepted octavia [source] (hirsute-proposed) [1:8.0.0~rc2-0ubuntu1]
[13:26] -queuebot:#ubuntu-release- Unapproved: accepted python3-stdlib-extensions [source] (hirsute-proposed) [3.9.4-0ubuntu1]
[13:26] -queuebot:#ubuntu-release- Unapproved: accepted cinder [source] (hirsute-proposed) [2:18.0.0~b1-0ubuntu2]
[13:38] -queuebot:#ubuntu-release- Unapproved: gnome-disk-utility (focal-proposed/main) [3.36.1-1ubuntu1 => 3.36.3-0ubuntu1] (ubuntu-desktop)
[13:43] -queuebot:#ubuntu-release- Unapproved: curl (hirsute-proposed/main) [7.74.0-1ubuntu1 => 7.74.0-1ubuntu2] (core, i386-whitelist)
[13:50] -queuebot:#ubuntu-release- Unapproved: ldb (hirsute-proposed/main) [2:2.2.0-3ubuntu1 => 2:2.2.0-3ubuntu2] (core, i386-whitelist)
[14:37] -queuebot:#ubuntu-release- Unapproved: gnome-control-center (focal-proposed/main) [1:3.36.5-0ubuntu1 => 1:3.36.5-0ubuntu2] (ubuntu-desktop)
[14:39] -queuebot:#ubuntu-release- New binary: python3.10 [s390x] (hirsute-proposed/universe) [3.10.0~a7-1ubuntu1] (i386-whitelist)
[14:40] -queuebot:#ubuntu-release- New binary: python3.10 [amd64] (hirsute-proposed/universe) [3.10.0~a7-1ubuntu1] (i386-whitelist)
[14:41] -queuebot:#ubuntu-release- New: accepted python3.10 [amd64] (hirsute-proposed) [3.10.0~a7-1ubuntu1]
[14:41] -queuebot:#ubuntu-release- New: accepted python3.10 [s390x] (hirsute-proposed) [3.10.0~a7-1ubuntu1]
[14:44] <Laney> juliank: nice change in gradient on the graphs though :>
[14:50] -queuebot:#ubuntu-release- New binary: python3.10 [ppc64el] (hirsute-proposed/universe) [3.10.0~a7-1ubuntu1] (i386-whitelist)
[14:52] -queuebot:#ubuntu-release- New binary: python3.10 [i386] (hirsute-proposed/universe) [3.10.0~a7-1ubuntu1] (i386-whitelist)
[14:56] -queuebot:#ubuntu-release- New: accepted python3.10 [i386] (hirsute-proposed) [3.10.0~a7-1ubuntu1]
[14:56] -queuebot:#ubuntu-release- New: accepted python3.10 [ppc64el] (hirsute-proposed) [3.10.0~a7-1ubuntu1]
[15:00] <Laney> is there any particular reason thunderbird didn't get accepted?
[15:37] <sil2100> Laney: I had a question about the change, I see that Olivier answered it but I didn't have time to read it
[15:37] <sil2100> Since I wasn't sure if this can be treated as a feature or not
[15:50] -queuebot:#ubuntu-release- Unapproved: kopanocore (hirsute-proposed/universe) [8.7.0-7.1 => 8.7.0-7.1ubuntu1] (no packageset)
[15:51] <hellsworth> sil2100: hey we have a couple of LO SRU bugs hanging out waiting for action. Both 6.4.7 (focal) and 7.0.5 (groovy) have been uploaded to proposed and here are the two bugs, respectively: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1906684 and https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1913353
[15:51] <ubot5> Ubuntu bug 1906684 in libreoffice (Ubuntu Focal) "[SRU] libreoffice 6.4.7 for Focal" [High,In progress]
[15:51] <ubot5> Ubuntu bug 1913353 in libreoffice (Ubuntu Groovy) "[SRU] libreoffice 7.0.5 for groovy" [High,In progress]
[15:52] -queuebot:#ubuntu-release- Unapproved: accepted kopanocore [source] (hirsute-proposed) [8.7.0-7.1ubuntu1]
[15:56] <sil2100> hellsworth: hey! I'll handle those this week for sure o/ I had a question regarding the nature of the synces in the queues, but I see that Rico answered my question already
[15:56] <sil2100> So I'm unblocked on those
[15:56] <hellsworth> great thanks so much :)
[15:56] <sil2100> Latest they'll be done during my shift on Thursday, but I'll see if I can take a look earlier!
[15:56] <hellsworth> many thanks
[15:59] <Laney> sil2100: alrighty
[16:04] <ricotz> sil2100, thank you
[16:22] <juliank> Laney: Yeah, nice progress :-)
[16:56] <teward> can a release team member accept nvidia-settings in hirsute?  It is a necessary fix to unbreak an FTBFS in xfce4-sensors-plugin which was discovered in doko's test rebuild (and also in Debian).  It contains a patch included from Debian to fix the issue.
[17:00] <doko> teward: not release team, but accepted to fix the ftbfs
[17:00] <teward> doko: thank you kindly!
[17:00] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-settings [source] (hirsute-proposed) [460.56-0ubuntu2]
=== ijohnson is now known as ijohnson|lunch
[17:21] <rbalint> Laney, juliank it looks like as if arm64 tests triggered by glibc in hirsute disappeared and many failed due to infra issues
[17:23] <Laney> Which disappeared?
[17:24] <Laney> I know about the failures, we borked autopkgtest for a bit earlier, see scrollback
[17:26] <Laney> will retry them :>
[17:31] <rbalint> Laney, i see a lot of arm64 tests in progress, but it may be just a delay in the results showing up
[17:33] <rbalint> Laney, thanks if you can restart the lost ones
[17:34] <Laney> If there's any lost we'll see that in the morning
[17:36] <rbalint> RAOF, bdmurray, the autopkgtest runners don't have a very long queue, could you please accept glibc for focal or groovy?
[18:05] <GunnarHj> Anybody who can accept gnome-shell-extension-desktop-icons-ng in the hirsute queue? (It's a no-change rebuild and the first step in a series of measures to make sense of the translations.)
[18:11] <rbasak> I don't have those powers, but it's nice to see yours being put to good use. Thank you :)
[18:17] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell-extension-desktop-icons-ng [source] (hirsute-proposed) [0.15.0-0ubuntu2]
[18:34] <GunnarHj> rbasak: Yeah, that was the first one, and it worked. Btw, I saw that my personal packageset was still there this morning. Maybe you plan to clean it up later.
[18:37] <GunnarHj> Thanks "queuebot" for accepting it. :)
[18:57] <rbasak> GunnarHj: I thought I'd already removed that. Where did you see it?
[19:05] <GunnarHj> rbasak: https://people.canonical.com/~ubuntu-archive/packagesets/hirsute/personal-gunnarhj
[19:06] <rbasak> Interesting
[19:06] <bdmurray> GunnarHj: You are welcome
[19:06] <rbasak> I have deleted that, which sort of shows up if you look at the timestamps on https://people.canonical.com/~ubuntu-archive/packagesets/hirsute/
[19:06] <rbasak> GunnarHj: I appreciate you mentioning it :)
[19:07] <rbasak> I guess the timestamp difference demonstrates that it's gone but this "report" can't handle packageset deletions.
[19:08] <GunnarHj> rbasak: Got it. Missed that date stamp.
[19:10] <rbasak> I think maybe https://bazaar.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/trunk/view/head:/packageset-report needs fixing.
[19:11] <GunnarHj> Sounds plausible.
[19:28] <luna> Reinstalled my desktop with todays Hirsute beta today :)
=== ijohnson|lunch is now known as ijohnson
[20:37] -queuebot:#ubuntu-release- Unapproved: alsa-lib (focal-proposed/main) [1.2.2-2.1ubuntu2.3 => 1.2.2-2.1ubuntu2.4] (core, i386-whitelist)
[20:37] -queuebot:#ubuntu-release- Unapproved: caftools (hirsute-proposed/multiverse) [2.0.3-1 => 2.0.3-1ubuntu1] (no packageset)
[20:37] -queuebot:#ubuntu-release- Unapproved: python3-defaults (hirsute-proposed/main) [3.9.2-2 => 3.9.4-1] (core, i386-whitelist)
[20:37] -queuebot:#ubuntu-release- Unapproved: speech-dispatcher-contrib (hirsute-proposed/multiverse) [0.10.2-2 => 0.10.2-2ubuntu1] (i386-whitelist)
[20:37] -queuebot:#ubuntu-release- Unapproved: alsa-lib (groovy-proposed/main) [1.2.3.2-1ubuntu3.1 => 1.2.3.2-1ubuntu3.2] (core, i386-whitelist)
[20:37] -queuebot:#ubuntu-release- Unapproved: senlin (hirsute-proposed/universe) [1:10.0.0+git2021012713.f9941275-0ubuntu1 => 1:11.0.0~rc1-0ubuntu1] (openstack)
[20:37] -queuebot:#ubuntu-release- Unapproved: placement (hirsute-proposed/main) [1:4.0.0+git2021012713.fa95ef87-0ubuntu1 => 1:5.0.0~rc1-0ubuntu1] (openstack)
[20:38] -queuebot:#ubuntu-release- Unapproved: accepted caftools [source] (hirsute-proposed) [2.0.3-1ubuntu1]
[20:38] -queuebot:#ubuntu-release- Unapproved: accepted speech-dispatcher-contrib [source] (hirsute-proposed) [0.10.2-2ubuntu1]
[20:51] -queuebot:#ubuntu-release- Unapproved: smbc (hirsute-proposed/universe) [1.2.2-4build3 => 1.2.2-4ubuntu1] (no packageset)
[20:53] -queuebot:#ubuntu-release- Unapproved: accepted smbc [source] (hirsute-proposed) [1.2.2-4ubuntu1]
[21:00] -queuebot:#ubuntu-release- Unapproved: accepted placement [source] (hirsute-proposed) [1:5.0.0~rc1-0ubuntu1]
[21:00] -queuebot:#ubuntu-release- Unapproved: accepted senlin [source] (hirsute-proposed) [1:11.0.0~rc1-0ubuntu1]
[21:00] -queuebot:#ubuntu-release- Unapproved: accepted python3-defaults [source] (hirsute-proposed) [3.9.4-1]
[21:10] <bryyce> ubuntu-archive: Could you remove mash:armhf in hirsute?  (LP: #1922802)
[21:10] <ubot5> Launchpad bug 1922802 in mash (Ubuntu) "Please remove mash:armhf from hirsute" [Undecided,New] https://launchpad.net/bugs/1922802
[21:10] <bryyce> (Debian has dropped armhf as a supported arch)
[21:11] <sarnold> oh wow
[21:12] <sarnold> did we follow suit or are we carrying armhf forward on our own?
[21:13] <bryyce> sarnold, there are no rdepends on armhf; the usual things that need mash don't have armhf builds themselves.  So... guess makes most sense to follow suit.
[21:14] <bryyce> there is a meta package med-bio that's arch all that depends on it
[21:15] <bryyce> (there's a number of med-bio related packages stuck in -proposed, I'm hoping tackling some of the leafs helps unblock others)
[21:16] <sarnold> ah I think I misunderstood :) I thought you meant they dropped armhf entirely
[21:16] <bryyce> sarnold, oh!  yeah that would be notable, heh
[21:16] <bryyce> bad parenthetical on my part, sorry
[21:16] <sarnold> yeah :)
[21:17] <sarnold> hehe, yeah, in context it makes a lot more sense than "debian dropped an entire arch and only one package needs fixing" :)
[21:29] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-cuda-toolkit [source] (hirsute-proposed) [11.2.2-1ubuntu1]
[21:35] <bdmurray> rbalint: the existing groovy glibc SRU is tagged block-proposed. Do you know what the status of that is? Additionaly, given that there is a glibc in -proposed do you know how I'm supposed to view the Launchpad-Bugs-Fixed for a bileto ticket?
[22:44] -queuebot:#ubuntu-release- Unapproved: sipxtapi (hirsute-proposed/universe) [3.3.0~test18+dfsg.1-0.1 => 3.3.0~test18+dfsg.1-0.1ubuntu1] (no packageset)
[22:45] -queuebot:#ubuntu-release- Unapproved: accepted sipxtapi [source] (hirsute-proposed) [3.3.0~test18+dfsg.1-0.1ubuntu1]
[22:45] -queuebot:#ubuntu-release- Unapproved: phpdox (hirsute-proposed/universe) [0.12.0-4ubuntu1 => 0.12.0-5] (no packageset) (sync)
[22:46] -queuebot:#ubuntu-release- Unapproved: accepted phpdox [sync] (hirsute-proposed) [0.12.0-5]