[00:04] <vorlon> https://bazaar.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/trunk/revision/1502 because I'm sick of the inconsistency
[00:13] -queuebot:#ubuntu-release- Packageset: Added sip6 to i386-whitelist in impish
[01:17] -queuebot:#ubuntu-release- New binary: vitis-ai [arm64] (impish-proposed/universe) [1.3.2-0ubuntu7] (no packageset)
[01:40] -queuebot:#ubuntu-release- New: accepted vitis-ai [arm64] (impish-proposed) [1.3.2-0ubuntu7]
[02:54] <lous1F> gorilla, hippo, ...?
[03:09] <guiverc> lous1F, this isn't a support/discussion room; you can read the impish schedule here - https://discourse.ubuntu.com/t/impish-indri-release-schedule/18540 ; if you have questions please use #ubuntu-discuss, #ubuntu+1, #ubuntu-next etc
[03:20] <lous1F> I was wondering what the next animal will be called. not really a support question.
[03:22] <lous1F> in·dri
[03:22] <lous1F> A large, short-tailed Madagascan lemur which jumps from tree to tree in an upright position and rarely comes to the ground.
[07:29] -queuebot:#ubuntu-release- Unapproved: readline (bionic-proposed/main) [7.0-3 => 7.0-4ubuntu1.18.04.1] (core)
[09:53] <cjwatson> vorlon: https://launchpad.net/ubuntu/+archive/primary/+files/shim-signed_1.37~18.04.9_source.changes works now; I see elsewhere that there was a discovery overnight that the librarian sync from PS4 to PS5 hadn't been quite entirely as complete as we thought it was, and this was fixed
[10:54] -queuebot:#ubuntu-release- New sync: ayatana-indicator-messages (impish-proposed/primary) [0.8.2-1]
[10:54] -queuebot:#ubuntu-release- New sync: lomiri-url-dispatcher (impish-proposed/primary) [0.1.0-4]
[10:54] <RikMills> Wimpy: ^^^^ ball in your court from here
[10:55] <Wimpy> Cheers RikMills. Much appreciated.
[10:55] <RikMills> yw
[14:04] <jawn-smith> Hello archive admins. I've created a bug to remove a package that is FTBFS with glibc 2.34
[14:04] <jawn-smith> https://bugs.launchpad.net/ubuntu/+source/aspectc++/+bug/1941806
[14:05] <jawn-smith> It has no reverse dependencies and seemingly not many users. It is fairly active upstream so once it is fixed it can be re-uploaded
[14:50] <sil2100> jawn-smith: let me take a look o.
[14:50] <sil2100> o/
[14:50] <tjaalton> hmm, is it just me or did 20.04.3 still have some oem-5.6 stuff on it?
[14:50] <jawn-smith> thanks sil2100!
[14:54] <sil2100> tjaalton: not sure! I only got a +1 from the QA team after testing the OEM stuff and Brian was browsing through teh manitests (but I guess those are not visible there?)
[15:00] <tjaalton> sil2100: seems to be due to some nvidia dependencies.. linux-modules-nvidia-450-oem-20.04 etc provide nvidia-dkms-NNN
[15:06] <tjaalton> xnox: ^ could this be due to the mess with oem-20.04?
[15:07] <xnox> tjaalton:  we add packages based on globs. and we didn't remove -5.6 from the archive (it's still there in release & updates, but not updated anymore) maybe we need to tweak regexp of what we include on the iso, or some such.
[15:07] <xnox> tjaalton:  the oem-20.04 mess => yeah still need to sort that out.
[15:09] <tjaalton> right
[15:10] <vorlon> bdmurray: hum, I think I'm going to back out this change to bin/daily-checks; first, I don't see the need to report in megabytes instead of more accurately in bytes; secondly, because it's rounding in some cases it could report "oversized by 0 megabytes" which is useless; and thirdly, this is misusing "megabytes" contrary to the Ubuntu units policy, where it should either be using decimal mega or
[15:10] <vorlon> calling it "mibi"
[15:31] <cjwatson> If it's going to approximate it then it should at least have a sort of zooming approximation, where it reports large numbers in MiB and smaller numbers in bytes
[15:32] <cjwatson> (to avoid the "0 megabytes" problem)
[17:46] <ginggs> vorlon: after some trial and error, I managed to confirm llvm-toolchain-12's autopkgtests still fail in -release. it only started to pass in -proposed in the last two weeks https://autopkgtest.ubuntu.com/packages/l/llvm-toolchain-12/impish/arm64
[17:46] <ginggs> the version in focal -updates also passes
[17:47] <ginggs> so do we want a 'force-badtest llvm-toolchain-12/1:12.0.1-1/arm64' hint for this one?
[17:48] <ginggs> i don't think force-reset-test will work in this case
[18:19] <vorlon> ginggs: that sounds good to me
[18:20] <vorlon> ginggs: I'll add the hint, no need for an mp
[18:20] <ginggs> vorlon: thanks :)
[18:28] -queuebot:#ubuntu-release- Packageset: Added openjdk-18 to i386-whitelist in impish
[18:30] <vorlon> sil2100, laney: what do you think about LP: #1941905?  Do you think we should add redirects for such things to old-releases.u.c if someone asks for a specific point release URL, or should we continue pointing them to the current media instead?
[18:30] <vorlon> bdmurray: ^^ I guess everyone is EOW so I'll include you too :)
[18:31] <vorlon> it seems releases.u.c does have a RedirectPermanent for previous point releases
[18:31] <vorlon> so probably best to make cdimage.u.c do the same
[18:32] <vorlon> ugh now I'm in a rathole of things being http instead of https :)
[18:36] <laney> vorlon: Redirects feel good to me, should be documented in the process docs if they're a manual thing (think they are?)
[18:37] <vorlon> yeah I think they are manual
[18:37] <vorlon> would be good to automate, but for now documentation will do :)
[19:13] <sil2100> +1