[00:42] -queuebot:#ubuntu-release- Unapproved: mutter (kinetic-proposed/main) [43.0-1ubuntu3 => 43.0-1ubuntu4] (desktop-core, desktop-extra)
[00:42] <jbicha> vorlon: ^ new mutter
[00:45] <jbicha> vorlon: we might hit autopkgtest failures on armhf for the same issue
[00:45] <jbicha> I guess migration-reference would cover that
[00:55] <vorlon> ack
[00:56] <vorlon> jbicha, Trevinho: has anyone *actually* tested new mutter with old mesa binaries to confirm that it's a mesa regression rather than - say - a regression in mutter compilation?
[00:57] <vorlon> armel> heh
[00:58] <vorlon> I'm good with the debdiff but want to make sure we're not ignoring an actual regression in the new mutter binaries before accepting
[00:59] <jbicha> I don't have any armhf hardware. Maybe I'm misunderstanding what you're asking though?
[00:59] <vorlon> you have canonistack
[01:00] <vorlon> Trevinho was already doing tests there; I was hoping he would've taken my suggestion to test against the previous mesa binaries and report back
[01:01] <sarnold> (does canonistack have armhf? I thought it was all aarch64 that sometimes wears a costume)
[01:08] <vorlon> sarnold: so is launchpad
[01:08] <sarnold> same question there :)
[01:08] <vorlon> armhf containers work fine in canonistack
[01:11] <vorlon> jbicha: so, I'm not accepting this into the release pocket without dispositive proof that it's a wrong mesa and not a misbuilt mutter, which the current data can't rule out.  If Trevinho has timed out and you're not able to reproduce it, I will try to see if I can get a reproducer myself, but that will have to wait until after dinner here so pushes back the point at which we can start spinning
[01:11] <vorlon> candidate images
[01:11] <vorlon> I am accepting it into -proposed so it can build and autopkgtest, but not unblocking it without the above
[01:11] -queuebot:#ubuntu-release- Unapproved: accepted mutter [source] (kinetic-proposed) [43.0-1ubuntu4]
[01:38] <jbicha> ok, I'm not able to look into it more tonight either
[03:12] <vorlon> apparently my shell is just lousy with env var booby traps
[03:12] <vorlon> server image builds really happening now
[03:45] <vorlon> xnox: block allwinner "for now" - there's not much later.  LP: #1992859
[03:45] -ubottu:#ubuntu-release- Launchpad bug 1992859 in linux-allwinner (Ubuntu) "block allwinner for now" [Undecided, New] https://launchpad.net/bugs/1992859
[04:54] <vorlon> mutter published to release; ubuntu desktop and ubuntu budgie spinning now
[05:14] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Kinetic Final] (20221018) has been added
[05:23] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Kinetic Final] (20221018) has been added
[05:45] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Kinetic Final] (20221018) has been added
[06:41] -queuebot:#ubuntu-release- Unapproved: spirv-llvm-translator-15 (kinetic-proposed/universe) [15.0.0-1 => 15.0.0-1ubuntu1] (no packageset)
[06:42] -queuebot:#ubuntu-release- Unapproved: accepted spirv-llvm-translator-15 [source] (kinetic-proposed) [15.0.0-1ubuntu1]
[06:44] -queuebot:#ubuntu-release- Unapproved: spirv-llvm-translator-14 (kinetic-proposed/universe) [14.0.0-3 => 14.0.0-3ubuntu1] (no packageset)
[06:45] -queuebot:#ubuntu-release- Unapproved: accepted spirv-llvm-translator-14 [source] (kinetic-proposed) [14.0.0-3ubuntu1]
[07:35] <sil2100> Hello everyone! I think we now have most images building o/
[07:35] <sil2100> juergh, apw, klebers: hey! How are the new raspi kernels looking? When would be the ETA for those going to the release pocket?
[07:53] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Kinetic Final] (20221018.1) has been added
[07:53] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Kinetic Final] (20221018.1) has been added
[07:53] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+licheerv [Kinetic Final] (20221018.1) has been added
[07:53] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+visionfive [Kinetic Final] (20221018.1) has been added
[07:55] <sil2100> Those raspi images are not final yet, everyone ^
[08:21] <juergh> sil2100, looking promising so far. give me another hour.
[08:21] <sil2100> juergh: \o/
[08:35] -queuebot:#ubuntu-release- Unapproved: diffoscope (kinetic-proposed/universe) [224ubuntu1 => 224ubuntu2] (no packageset)
[08:35] -queuebot:#ubuntu-release- Unapproved: accepted diffoscope [source] (kinetic-proposed) [224ubuntu2]
[08:43] -queuebot:#ubuntu-release- Builds: Ubuntu Core amd64 edge [Kinetic Final] (20221018) has been added
[08:45] <sil2100> ...now that's weird ^
[08:46] <arraybolt3> ...? Something seems scrambled
[08:46] <sil2100> That shouldn't have ended up in kinetic
[08:51] <sil2100> I'll remove it from there and then check up what's up with that
[09:07] <sil2100> apw: will you unblock the raspi kernel when it's good to go?
[09:07] <sil2100> juergh: can you give me a heads up when you give a green light for the raspi kernel?
[09:13] <juergh> sil2100, will do
[09:47] <apw> sil2100, can do
[09:50] <juergh> apw, raspi is good to go.
[09:50] <juergh> sil2100, ^^
[09:51] <sil2100> Great news, apw will you do the honors..?
[09:51] <juergh> FYI: Kinetic raspi is good for release. Francis and I both ran boot tests locally. I also ran RT tests locally. ADT armhf is all good. ADT arm64 shows MISS/REGN due to the ongoing ADT ACPI reboot issue. Previous test results can be reused, so it looks all good. I've added tags to the tracker, the dashboard just needs to refresh.
[09:51] <apw> sil2100, will do.
[09:54] <apw> sil2100, and unblocked.
[09:54] <apw> cc: juergh ^
[10:51] -queuebot:#ubuntu-release- Builds: Ubuntu WSL [Kinetic Final] (3272629537) has been added
[10:59] -queuebot:#ubuntu-release- Unapproved: libva (kinetic-proposed/universe) [2.15.0-1 => 2.16.0-1] (i386-whitelist, kubuntu) (sync)
[11:09] <sil2100> eh, we might have some issues that we're investigating
[11:09] <sil2100> But oh well, still waiting for server images to build + the raspi kernel to migrate
[11:43] <arraybolt3> sil2100: OK, so we have yet more junk on the ZFS-on-Ubuntu front.
[11:43] <arraybolt3> sil2100: This time it's all Ubuntu Desktop. For one, I can't log into GNOME *at all* on a fresh installation. Not with Wayland, not with Xorg.
[11:44] <arraybolt3> For two, if I switch to a TTY and log in, I get a relatively awful error message related to an attempt to check for a new release of Ubuntu.
[11:44] <arraybolt3> This is on VirtualBox, BIOS firmware, ZFS + encryption.
[11:45] <arraybolt3> For the second issue, it appears that there is no /var/lib/dpkg/status file.
[11:46] <arraybolt3> Also "sudo apt update" fails with a related error at the end.
[11:47] <tjaalton> it's on life-support unfortunately
[11:47] <arraybolt3> This is the ick that apt throws at me at the end of a sudo apt update: https://bpa.st/IDIQ
[11:47] <arraybolt3> tjaalton: I think it may be a bit past that at this point...
[11:48] <tjaalton> my kinetic works fine, though it's dist-upgraded from jammy, not a fresh install
[11:49] <arraybolt3> Is it worth making another bug report?
[11:50] <arraybolt3> Hey, interesting discovery. Running "sudo touch /var/lib/dpkg/status" in a TTY made "sudo apt update" work, and also allowed me to log into GNOME.
[11:51] <arraybolt3> And Firefox is borked in exactly the same way as in Ubuntu Budgie.
[11:52] <arraybolt3> Plus it's throwing tons of internal error messages (one of which was related to update manager, not sure what the others were) in my face.
[12:05] <sil2100> tjaalton: how's your ZFS-foo?
[12:08] <tjaalton> spotty :)
[12:09] <arraybolt3> Mine's non-existent, but I have a fast computer, decent download speed, and plenty of time to help test whatever you guys want to throw at me.
[12:09] <tjaalton> I rebuilt my laptop after a nvme breakdown a year ago, so i've been lucky to not hit this bug in jammy and beyond
[12:10] <tjaalton> I'll install it somewhere and have a look if I can reproduce this
[12:17] <sil2100> apw, juergh: huh? I see some regressions reported for linux-meta-raspi on update_excuses, are those hinted?
[12:17] <sil2100> Since I think britney won't let them though this way, will it?
[12:21] <sil2100> grrr, the server builds failed on the debian-cd phase, let me re-run without --live
[12:22] <sil2100> (looked like a networking error)
[12:23] <sil2100> Okay, let me check in the meantime if the issues that juergh mentioned are hinted or not
[12:24] <sil2100> The hint needs bumping, let me do that
[12:24] <juergh> sil2100, I cannot hint britney. rtpengine and systemd failures are not regressions.
[12:25] <sil2100> juergh: yeah, I bumped the hint, since it was still on the old version of linux-meta-raspi
[12:25] <sil2100> Now the packages should migrate, hopefully soon
[12:25] <mdeslaur> could someone please accept tcpbench from the kinetic NEW queue?
[12:28] <mdeslaur> sil2100: ^ please?
[12:28] <sil2100> mdeslaur: o/
[12:38] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Kinetic Final] has been updated (20221018.3)
[12:38] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Kinetic Final] has been updated (20221018.3)
[12:38] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Kinetic Final] has been updated (20221018.3)
[12:38] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity riscv64 [Kinetic Final] has been updated (20221018.3)
[12:38] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Kinetic Final] has been updated (20221018.3)
[12:42] <sil2100> Finally
[12:49] <xnox> apw:  ubuntu-archive: please remove obsolete v5.4 v5.13 v5.15 kernels from kinetic https://bugs.launchpad.net/bugs/1993295
[12:49] -ubottu:#ubuntu-release- Launchpad bug 1993295 in linux-signed-intel-iotg (Ubuntu) "RM - Remove unsupported kernels from kinetic" [Undecided, New]
[12:53] <apw> xnox, looking.
[13:27] <apw> xnox, ok confirmed these are all either redundant sources or incomplete uninstallable package combinations.  All removed.
[13:51] -queuebot:#ubuntu-release- Unapproved: tzdata (focal-proposed/main) [2022c-0ubuntu0.20.04.0 => 2022e-0ubuntu0.20.04.0] (core)
[13:51] -queuebot:#ubuntu-release- Unapproved: tzdata (jammy-proposed/main) [2022c-0ubuntu0.22.04.0 => 2022e-0ubuntu0.22.04.0] (core)
[13:52] -queuebot:#ubuntu-release- Unapproved: tzdata (bionic-proposed/main) [2022c-0ubuntu0.18.04.0 => 2022e-0ubuntu0.18.04.0] (core)
[14:06] <sil2100> hmmm, we're missing the unmatched image?!
[14:09] <mdeslaur> tjaalton: I'm curious...what's on life support, zfs on ubuntu?
[14:11] <tjaalton> mdeslaur: yep
[14:11] <mdeslaur> "yay"
[14:12] <mdeslaur> *sigh*
[14:12] <tjaalton> a pity
[14:12]  * sil2100 is building the unmatched image
[14:13] <sil2100> Anyway, I'd need someone to investigate the ZFS issue
[14:13] <sil2100> I poked the desktop team, but I is there anyone else that knows the ZFS ecosystem enough to debug this?
[14:22] <sil2100> I asked enr0n and adrien to try and reproduce at least
[14:30] <bdmurray> Did arraybolt3 end up opening a bug? That sure would help.
[14:32] -queuebot:#ubuntu-release- Unapproved: gnome-calendar (kinetic-proposed/main) [43.0-2 => 43.1-0ubuntu1] (desktop-extra, ubuntu-desktop)
[14:35] <bdmurray> there is also bug 1993278
[14:35] -ubottu:#ubuntu-release- Bug 1993278 in ubiquity (Ubuntu) "ZFS + Encryption crash after install" [Undecided, New] https://launchpad.net/bugs/1993278
[14:35] <tjaalton> according to bug 1970066 it's not a regression though?
[14:35] -ubottu:#ubuntu-release- Bug 1970066 in snapd (Ubuntu Jammy) "(Encrypted) ZFS breaks 22.04 installation" [Critical, Confirmed] https://launchpad.net/bugs/1970066
[14:37] <sarnold> hello, jfyi the mir team is going through https://people.canonical.com/~ubuntu-archive/component-mismatches.svg and nvidia-graphics-drivers-418-server shows up unexpectedly :)
[14:46] <bdmurray> I'm retrying bug 1993278
[14:46] -ubottu:#ubuntu-release- Bug 1993278 in ubiquity (Ubuntu) "ZFS + Encryption crash after install" [Undecided, New] https://launchpad.net/bugs/1993278
[14:48] <bdmurray> fossfreedom: Did you choose to install 3rd party drivers?
[14:49] <arraybolt3> bdmurray: Pretty sure I did.
[14:49] <bdmurray> there's also a kernel oops in this syslog
[14:49] <arraybolt3> Bug #1993279
[14:49] -ubottu:#ubuntu-release- Bug 1993279 in snapd (Ubuntu) "Firefox fails on the first reboot after installing Ubuntu Budgie with ZFS + encryption + recovery key" [Undecided, New] https://launchpad.net/bugs/1993279
[14:50] <fossfreedom> bdmurray yes. I had to in my case since the macbook has broadcom requirements for the wifi
[14:51] <bdmurray> ack
[14:52] <arraybolt3> (All the rest of the ZFS nonsense described above other than the Firefox stuff, I did not yet file a bug on. I can if that's helpful.)
[14:52] <bdmurray> Its always helpful.
[14:52] <arraybolt3> bdmurray: +1
[14:52] <vorlon> sarnold: looks like apw mis-demoted it, not sure if that was part of xnox's kernel request above but I'm repromoting it now
[14:53] <sarnold> vorlon: aha, thanks :)
[14:54] <vorlon> (thanks for the call-out, I might've missed this otherwise for release as I thought we were done changing components!)
[14:58] <enr0n> sil2100: currently trying to reproduce it
[15:05] <arraybolt3> Bug #1993318 <-- this is the rest of the ZFS mess, excluding the Firefox stuff which already has its own bug report
[15:05] -ubottu:#ubuntu-release- Bug 1993318 in zsys (Ubuntu) "ZFS + Encryption installations of Ubuntu Desktop suffer various severe problems related to the package manager" [Undecided, New] https://launchpad.net/bugs/1993318
[15:08] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Kinetic Final] has been updated (20221018.1)
[15:11] <sil2100> enr0n: thanks! The desktop team mentioned this might not be a regression
[15:14] <bdmurray> I was able to install and log in
[15:14] <xnox> vorlon:  i'm not sure if all the removals were done correct; waiting for archive to fully publish.
[15:14] <xnox> vorlon:  what did you repromote?
[15:15] <vorlon> xnox: nvidia-graphics-drivers-418-server, which isn't linux-* at all
[15:15] <xnox> vorlon:  418-server is no longer supported, and must not be in restricted; it is intentionally in multiverse
[15:15] <xnox> vorlon:  i think seeds need to be adjusted for it maybe.
[15:15] <enr0n> sil2100: bdmurray: Okay, good to know. My installation in a QEMU/KVM setup looks good as well FWIW.
[15:15] <xnox> it is EOL by nvidia
[15:17] <vorlon> xnox: and what's the basis for saying this and why was it demoted in advance of seeds matching?
[15:17] <arraybolt3> Interesting, I'll try QEMU/KVM and see if that behaves differently.
[15:17] <vorlon> I don't believe it's correct that we demote "no longer supported" nvidia packages to multiverse
[15:18] <vorlon> my understanding was they're either in restricted, or removed from the archive (in favor of transitional packages)
[15:18] <xnox> vorlon:  it cannot be really removed, as it has a unique set of nvidia cards that only that series supports; and later drivers have dropped them.
[15:19] <xnox> vorlon:  circa 10-15% pci ids supported by 418-server are not supported by any later series; so it becomes sort of like the 390 package; which is also eol by nvidia and doesn't have security support.
[15:19] <xnox> but also it ftbfs against v5.19 kernel
[15:19] <xnox> let me go ask people what was the plan for it; and if it was completed.
[15:19] <vorlon> xnox: 390 is in restricted up to and including kinetic
[15:20] <vorlon> restricted is not a security support committment
[15:20] <sil2100> enr0n, bdmurray: thanks!
[15:23] <bdmurray> My testing was also in QEMU/KVM
[15:24] -queuebot:#ubuntu-release- Unapproved: ubuntu-image (kinetic-proposed/main) [2.2+22.04ubuntu3 => 2.2+22.10ubuntu1] (desktop-core)
[15:24] <xnox> vorlon:  so unlike 390, 418-server ftbfs against v5.19 kernels; and it hasn't been fixed. kernel team thought it is acceptable to demote it to universe, and left it ftbfs there. (not a true ftbfs, but like apt install the 418-server dkms fails to configure, due to dkms build fail)
[15:25] <vorlon> xnox: are we shipping signed non-dkms modules that don't fail?
[15:25] <xnox> 418-server is not included, and not signed.
[15:25] <vorlon> then what good is it for anyone to have it in kinetic?
[15:25] <xnox> (in lrm)
[15:26] <xnox> i mean i wanted to RM it from the get go =)
[15:26] <vorlon> then who's arguing to keep it? bring them here and make them state their case :P
[15:26] <vorlon> but no, "it ftbfs, dump it in universe" is not the way
[15:27] <xnox> arighi & tseliot are not here
[15:29] <vorlon> well anyway, we shouldn't make any seed changes here
[15:29] <xnox> ack
[15:29] <vorlon> the existing globs are quite deliberate
[15:29] <vorlon> so it's back in restricted now, and I'd be happy to see it removed instead
[15:29] <xnox> well, i fixed up all the globs this cycle; but yes very deliberate
[15:30] <xnox> vorlon:  some people want to be nice. as one has to throw away their gpu if we can't make 418-server build
[15:30] <vorlon> tseliot: hi - who does it serve to have an nvidia 418-server in kinetic that can't build modules for the release kernel? :)
[15:30] <arraybolt3> OK so using QEMU/KVM allowed me to log in also, though first GDM vanished and left me with some scary "failed unmounting /var/spool" and "failed unmounting /var/log" warnings. It just left me there for an uncomfortably long time, and the TTYs didn't work, but then GDM came back and I was able to log in, whereupon Firefox was missing.
[15:30] <vorlon> xnox: I mean, SRU hat, I would let y'all bring it back in -updates if you got the build failures fixed
[15:31] <tseliot> vorlon, basically waiting for me or somebody else to have the time to patch it up
[15:31] <vorlon> ok
[15:31] <arraybolt3> And apt appears to still be broken out of the box.
[15:32] <arraybolt3> And the weird crash in the TTY still happens. So I guess the login problems were a fluke or were due to VBox, but the rest of the bug report still applies. I'll edit it.
[15:33] <vorlon> tseliot, xnox: so from my POV, it does belong in restricted or not in the release pocket at all; if there's metadata here that might cause the installer to select this version and have it fail, then "not at all" is better for release until it gets fixed
[15:33] <vorlon> and I'm more than happy to see a fix in -updates, whether or not it ships in the release pocket
[15:33] <xnox> it does contain metadata to be allowed to be selected as a valid version by the installer
[15:34] <xnox> since it will fail to install; i would prefer to remove it from kinetic-release; and reintroduce as installable once we fix it in kinetic-updates
[15:35] <vorlon> xnox just found https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1988322 lol
[15:35] <tseliot> We were thinking of moving that to multiverse, and fix it there. But whatever makes more sense
[15:35] <xnox> tseliot:  do you agree with above? i.e. person installing desktop on that machine with that old gpu card; and ticking "please install nvidia drivers" => would result in installer failure.
[15:35] -ubottu:#ubuntu-release- Launchpad bug 1988322 in nvidia-graphics-drivers-418-server (Ubuntu) "RM 418-server LRM and demote to multiverse" [Undecided, Incomplete]
[15:35] <tseliot> Yes, that
[15:36] <vorlon> thanks, I'm happy to demote this to -proposed then - someone should make sure there's a bug opened against the package tracking this issue, with appropriate importance set, ideally with update-excuse tag set, that can be used for later SRU
[15:38] <tseliot> Great, thanks, we will take care of that
[15:38] <vorlon> tseliot: as soon as the bug is there, please ping me the link and I'll demote this to -proposed
[15:39] <tseliot> vorlon, Ok, I'll file a new bug report and let you know then
[15:45] <xnox> apw:  ubuntu-archive: vorlon: https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1993324 remove dkms module that has vanilla kernel support now.
[15:45] -ubottu:#ubuntu-release- Launchpad bug 1993324 in rtl8821ce (Ubuntu) "RM rtl8821ce - driver has been upstreamed" [Undecided, Triaged]
[15:45] <vorlon> tseliot, xnox: while you're all here, is nvidia-graphics-drivers-tesla supposed to be in kinetic?
[15:45] <xnox> (it is pain to keep on fixing it for ftbfs, when it is not needed any more by anybody)
[15:45] <vorlon> xnox: lol you raced me by a minute I just reloaded https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-archive&field.status=NEW&field.status=Confirmed&field.status=Triaged&field.status=INPROGRESS&field.status=FIXCOMMITTED&field.status=INCOMPLETE_WITH_RESPONSE&orderby=-id&start=0
[15:46] <xnox> vorlon:  i want to blacklist all *-tesla things from being copied from debian. In ubuntu all the -tesla things are called -server, and we package them ourselves
[15:46] <tseliot> vorlon, no, that comes from Debian
[15:46] <tseliot> Right
[15:46] <vorlon> that's what I figured; I don't recall if we can glob blacklist syncs?
[15:46] <xnox> don't think so
[15:46] <xnox> i seemed to be static list
[15:47] <xnox> but we can remove them once; and they don't come back right?
[15:47] <xnox> (archive sync honors explicit RMs right?!)
[15:47] <vorlon> xnox: it honors explicit RM *of that version*
[15:47] <vorlon> that's why there is a blacklist
[15:48] <xnox> i can do merge proposal to the blacklist.... and keep updating it i guess
[15:49] <vorlon> there's a lot of tesla stuff there already
[15:49] <vorlon> and I've just pushed the blacklist change for this package
[15:49] <vorlon> and no you can't do an mp because the branch is still in +junk :/
[15:50] <vorlon> (there's an action item to fix this)
[15:52] <xnox> i wish "an action item" had a cooler name, like "a forgotten artifact"
[15:53] <vorlon> if it helps, Foundations records all its action items on stele
[16:08] <tseliot> vorlon, how does this look? https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1993328
[16:08] -ubottu:#ubuntu-release- Launchpad bug 1993328 in nvidia-graphics-drivers-418-server (Ubuntu) "Demote nvidia-graphics-drivers-418-server to multiverse" [High, New]
[16:15] <vorlon> tseliot: corrected the title :)
[16:15] <xnox> added block-proposed tags
[16:16] <tseliot> Oh, right, thanks vorlon and xnox
[16:18] <vorlon> actually, changed the title again
[16:18] <vorlon> that's more appropriate for the future SRU
[16:20] <tseliot> All right
[16:43] -queuebot:#ubuntu-release- Unapproved: diffoscope (kinetic-proposed/universe) [224ubuntu2 => 224ubuntu3] (no packageset)
[16:44] -queuebot:#ubuntu-release- Unapproved: accepted diffoscope [source] (kinetic-proposed) [224ubuntu3]
[16:54] <seb128> vorlon, how do we enable a new source to build on i386 for a ppa targetting an older serie? by bootstraping through the update-i386-whitelist like we would do for a package in the archive?
[16:55] <vorlon> seb128: it has to be added statically to update-i386-whitelist because the packageset will never pick up packages not in the archive via germinate
[16:55] <vorlon> lots of examples of this in the script already (I hate it
[16:55] <vorlon> )
[16:56] <xnox> is the whitelist based on target distro/series, rather than a property of the archive? can one not self-grant queue admin rights on a ppa; and then adjust the whitelist in a given ppa?!
[16:56] <xnox> didims
[17:00] <vorlon> the script supports by-series overrides yes
[17:00] <vorlon> adjust the whitelist in a given ppa> I don't believe ppas get to define packagesets so no?
[17:06] -queuebot:#ubuntu-release- Unapproved: pytango (kinetic-proposed/universe) [9.3.3-1build1 => 9.3.3-1ubuntu1] (no packageset)
[17:08] -queuebot:#ubuntu-release- Unapproved: accepted pytango [source] (kinetic-proposed) [9.3.3-1ubuntu1]
[17:17] <seb128> vorlon, thanks
[17:27] <seb128> vorlon, so I tried to do https://git.launchpad.net/ubuntu-archive-tools/commit/?id=f1862557 and then
[17:27] <seb128> $ ./update-i386-whitelist https://people.canonical.com/~ubuntu-archive/germinate-output/i386.jammy/i386+build-depends.sources
[17:27] -ubottu:#ubuntu-release- Commit f186255 in ubuntu-archive-tools "Whitelist mozjs102 not only for kinetic HEAD main"
[17:27] <seb128> since I want to enable the source to build on 22.04
[17:28] <seb128> but that lists a stack of package to add, not including mozjs102 and even more to remove from the whitelist...
[17:31] <vorlon> seb128: under-documented -s <release> option required; you're trying to change the whitelist for kinetic with that commandline
[17:34] <jbicha> for background, this is part of bug 1993214. I intend to email the release list to let y'all know, but the plan is for the update to go through -security
[17:34] -ubottu:#ubuntu-release- Bug 1993214 in mozjs102 (Ubuntu) "[jammy] Update gjs to 1.74 using mozjs102 102.3" [Undecided, New] https://launchpad.net/bugs/1993214
[17:35] <seb128> vorlon, ah ok, I though it would use the serie from the url, thanks
[17:44] <seb128> that worked
[17:45] <seb128> jbicha, it should build now, you need another upload or a copy to the same archive to get it picked though I think
[17:47] <vorlon> correct
[17:47] <vorlon> copy-package --force-same-destination -b :)
[17:48] <jbicha> cool, that worked :)
[17:53] -queuebot:#ubuntu-release- Unapproved: accepted libidn2 [source] (kinetic-proposed) [2.3.3-1build1]
[18:11] -queuebot:#ubuntu-release- Packageset: Added llvm-toolchain-15 to i386-whitelist in jammy
[18:11] -queuebot:#ubuntu-release- Packageset: Added mozjs102 to i386-whitelist in jammy
[18:11] -queuebot:#ubuntu-release- Packageset: Added openjdk-19 to i386-whitelist in jammy
[18:11] -queuebot:#ubuntu-release- Packageset: Added openjdk-20 to i386-whitelist in jammy
[18:33] <seb128> has anyone tried to convert sync-blacklist from bzr to git before? It seems like it should be an easy one but I wonder if that hasn't been done for a reason
[18:35] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+licheerv [Kinetic Final] has been updated (20221018.3)
[18:35] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+nezha [Kinetic Final] (20221018.3) has been added
[18:35] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unmatched [Kinetic Final] (20221018.3) has been added
[18:35] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+visionfive [Kinetic Final] has been updated (20221018.3)
[18:59] <bdmurray> seb128: I think just a lack of time but it should also move to somewhere we can submit MPs for it
[19:00] <vorlon> seb128: what bdmurray said; mostly just Round Tuits, and also coordination with the code on snakefruit that consumes the branch
[19:01] <seb128> ack, maybe an easy hack session for Prague!
[19:07] <rbasak> somewhere we can submit MPs for it> I think this happens automatically with Launchpad git repositories.
[19:07] <rbasak> Since with git you don't have to use +junk
[19:09] <vorlon> rbasak: according to cjwatson it still needs a project, mps still not possible for un-namespaced branches
[19:10] <rbasak> Ah. I was unaware. That might be worth noting in https://help.launchpad.net/Code/Git
[19:11] <rbasak> "propose merges from one branch to another, including in a different repository, provided that they are against the same project or package" sort of alludes to that, but it's not obvious when reading https://help.launchpad.net/Code/Git#Repository_URLs that the third form is inferior in any way.
[19:20] -queuebot:#ubuntu-release- Unapproved: logwatch (focal-proposed/main) [7.5.2-1ubuntu1.3 => 7.5.2-1ubuntu1.4] (ubuntu-server)
[19:28] -queuebot:#ubuntu-release- Unapproved: ubiquity (kinetic-proposed/main) [22.10.9 => 22.10.10] (ubuntu-desktop)
[19:32] <cjwatson> vorlon: almost true; MPs are possible with "personal" repositories too, but only for branches within the same repository
[19:33] <vorlon> aha
[19:33] <cjwatson> (but that's probably a not very helpful distinction in this case)
[19:33] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (kinetic-proposed) [22.10.10]
[19:40] <vorlon> ginggs: apologies for the pytango upload failures, I've cleaned up the NBS binaries from -proposed now if you want to re-trigger those builds.  Though I'm not sure about python3-tango-dbgsym, hopefully that gets auto-removed when I remove python3-tango?
[19:40] <ginggs> vorlon: thanks, i'll retry and look out for the -dbgsym
[20:03] -queuebot:#ubuntu-release- Unapproved: llvm-toolchain-15 (kinetic-proposed/main) [1:15.0.2-1 => 1:15.0.3-1~exp1] (i386-whitelist) (sync)
[20:11] -queuebot:#ubuntu-release- Unapproved: rejected llvm-toolchain-15 [sync] (kinetic-proposed) [1:15.0.3-1~exp1]
[21:28] <vorlon> fyi we've got reproduction of the zfs+encryption install option falling on its face in kinetic and confirmation that it works with jammy so the ubiquity upload above is going to be accepted, forcing respins of the set of images you're about to see notifications for below v
[21:31] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Kinetic Final] has been disabled
[21:31] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Kinetic Final] has been disabled
[21:31] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Kinetic Final] has been disabled
[21:31] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Kinetic Final] has been disabled
[21:31] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Kinetic Final] has been disabled
[21:31] -queuebot:#ubuntu-release- Builds: Ubuntu Unity Desktop amd64 [Kinetic Final] has been disabled
[21:31] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Kinetic Final] has been disabled
[21:31] <vorlon> the ubiquity change greys out the option to do zfs+encryption and the current plan is release notes will direct users who want this feature to install using jammy media, as this appears to work
[22:13] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Kinetic Final] has been updated (20221018.1)
[22:46] <vorlon> bdmurray: tagging you just so that I know someone else sees it, I'm concerned by some of the autopkgtest output in https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html.  ubiquity shows i386 as 'Test in progress' but it was previously failed so that should be indicated; and yesterday I noticed one that said Test in progress but won't block (I don't remember what the
[22:46] <vorlon> exact language is for this) but it should have blocked
[22:46] <vorlon> in that case I watched and the autopkgtests passed so it wasn't an issue, but still
[22:47] <vorlon> and this is not just an html display issue, I grabbed the yaml and see i386 is listed as 'RUNNING', not 'RUNNING-ALWAYSFAIL'
[22:47] <vorlon> so we've apparently got some bugs here
[22:48] <xnox> vorlon: is it expected that ubuntu desktop has "bare" snap preseeded?
[22:48] <vorlon> now on the britney run that just published, all the output is correct :/
[22:48] <vorlon> xnox: one or more of the snaps has that as a base, yes; why?
[23:14] <xnox> couldn't spot any, will double check
[23:17] <xnox> ah gtk-common-themes
[23:20] -queuebot:#ubuntu-release- New source: micropython-mpremote (kinetic-proposed/primary) [0.4.0-0ubuntu1]
[23:20] -queuebot:#ubuntu-release- New source: rpi-lgpio (kinetic-proposed/primary) [0.3-0ubuntu1]
[23:55] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Kinetic Final] has been updated (20221018.1)
[23:57] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Kinetic Final] has been updated (20221018)
[23:58] -queuebot:#ubuntu-release- Builds: Ubuntu Unity Desktop amd64 [Kinetic Final] has been updated (20221018)