[00:01] -queuebot:#ubuntu-release- New binary: slidge-matridge [amd64] (noble-proposed/universe) [0+git20240208.c1f6bbf9-1] (no packageset)
[00:40] -queuebot:#ubuntu-release- New: accepted slidge-matridge [amd64] (noble-proposed) [0+git20240208.c1f6bbf9-1]
[00:51] -queuebot:#ubuntu-release- Packageset: Added python-cryptography to i386-whitelist in noble
[00:51] -queuebot:#ubuntu-release- Packageset: Added rust-pyo3-macros to i386-whitelist in noble
[01:05] -queuebot:#ubuntu-release- Packageset: Added rust-proc-macro2 to i386-whitelist in noble
[01:06] -queuebot:#ubuntu-release- Packageset: Added rust-quote to i386-whitelist in noble
[01:06] -queuebot:#ubuntu-release- Packageset: Added rust-syn to i386-whitelist in noble
[01:06] -queuebot:#ubuntu-release- Packageset: Added rust-unicode-ident to i386-whitelist in noble
[01:46] <vorlon> doko: ^ is that you?  (why do we need python-cryptography on i386 if we didn't before?)
[01:54] <doko> yes, that's stunnel4 not migrating, and that one is used by apt, curl, ssvnc
[02:00] <vorlon> ok
[05:14] -queuebot:#ubuntu-release- New binary: node-long [amd64] (noble-proposed/none) [5.2.3-2] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: kubectx [amd64] (noble-proposed/none) [0.9.5-1] (no packageset)
[05:19] -queuebot:#ubuntu-release- New binary: kubectx [ppc64el] (noble-proposed/none) [0.9.5-1] (no packageset)
[05:19] -queuebot:#ubuntu-release- New binary: kubectx [s390x] (noble-proposed/none) [0.9.5-1] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: kubectx [arm64] (noble-proposed/none) [0.9.5-1] (no packageset)
[05:26] -queuebot:#ubuntu-release- New binary: kubectx [armhf] (noble-proposed/none) [0.9.5-1] (no packageset)
[05:43] -queuebot:#ubuntu-release- New binary: kubectx [riscv64] (noble-proposed/none) [0.9.5-1] (no packageset)
[06:11] <vorlon> https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntu-server-live/+build/579586 uh what now?
[06:11] <vorlon> pretty sure we didn't half-publish openssh
[06:11] <vorlon> oh otoh maybe it got published in between apt-get update's in the image build
[07:28] <mwhudson> vorlon: just apt updating all over the place cannot possibly have unintended consequences
[07:46] -queuebot:#ubuntu-release- Unapproved: cockpit (jammy-backports/universe) [310.1-1~bpo22.04.1 => 311-1~bpo22.04.1] (no packageset)
[07:47] -queuebot:#ubuntu-release- Unapproved: cockpit (mantic-backports/universe) [310.1-1~bpo23.10.1 => 311-1~bpo23.10.1] (no packageset)
[10:02] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (jammy-proposed/main) [2.765.39 => 2.765.40] (desktop-core, i386-whitelist)
[10:09] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (jammy-proposed) [2.765.40]
[10:28] -queuebot:#ubuntu-release- New: accepted kubectx [amd64] (noble-proposed) [0.9.5-1]
[10:28] -queuebot:#ubuntu-release- New: accepted kubectx [armhf] (noble-proposed) [0.9.5-1]
[10:28] -queuebot:#ubuntu-release- New: accepted kubectx [riscv64] (noble-proposed) [0.9.5-1]
[10:28] -queuebot:#ubuntu-release- New: accepted node-long [amd64] (noble-proposed) [5.2.3-2]
[10:28] -queuebot:#ubuntu-release- New: accepted kubectx [arm64] (noble-proposed) [0.9.5-1]
[10:28] -queuebot:#ubuntu-release- New: accepted kubectx [s390x] (noble-proposed) [0.9.5-1]
[10:28] -queuebot:#ubuntu-release- New: accepted kubectx [ppc64el] (noble-proposed) [0.9.5-1]
[13:52] -queuebot:#ubuntu-release- Unapproved: apt-mirror (focal-proposed/universe) [0.5.4-1 => 0.5.4-1ubuntu1.20.04.1] (no packageset)
[13:52] -queuebot:#ubuntu-release- Unapproved: apt-mirror (jammy-proposed/universe) [0.5.4-1 => 0.5.4-1ubuntu0.22.04.1] (no packageset)
[13:54] -queuebot:#ubuntu-release- New binary: cpp-httplib [armhf] (noble-proposed/universe) [0.14.3+ds-1] (no packageset)
[13:54] -queuebot:#ubuntu-release- New binary: cpp-httplib [ppc64el] (noble-proposed/universe) [0.14.3+ds-1] (no packageset)
[13:55] -queuebot:#ubuntu-release- New binary: cpp-httplib [amd64] (noble-proposed/universe) [0.14.3+ds-1] (no packageset)
[13:56] -queuebot:#ubuntu-release- New binary: cpp-httplib [s390x] (noble-proposed/universe) [0.14.3+ds-1] (no packageset)
[14:03] -queuebot:#ubuntu-release- New binary: cpp-httplib [arm64] (noble-proposed/universe) [0.14.3+ds-1] (no packageset)
[14:09] -queuebot:#ubuntu-release- New binary: cpp-httplib [riscv64] (noble-proposed/universe) [0.14.3+ds-1] (no packageset)
[14:35] -queuebot:#ubuntu-release- New source: pemmican (noble-proposed/primary) [1.0.1-0ubuntu1]
[14:42] -queuebot:#ubuntu-release- Unapproved: vtun (mantic-proposed/universe) [3.0.4-2build1 => 3.0.4-2ubuntu0.23.10.1] (no packageset)
[14:43] -queuebot:#ubuntu-release- Unapproved: vtun (focal-proposed/universe) [3.0.4-2 => 3.0.4-2ubuntu0.20.04.1] (no packageset)
[14:43] -queuebot:#ubuntu-release- Unapproved: vtun (jammy-proposed/universe) [3.0.4-2build1 => 3.0.4-2ubuntu0.22.04.1] (no packageset)
[15:37] <arraybolt3> umm... is the casper SRU still going to be verified and the ISOs respun?
[15:37] <arraybolt3> for jammy.4
[15:37] <arraybolt3> We're awfully close to release day and if we wait another day we'll be in a mad scramble testing a world respin just before the deadline.
[16:09] -queuebot:#ubuntu-release- Unapproved: digimend-dkms (jammy-proposed/universe) [10-4 => 10-4ubuntu0.1] (no packageset)
[16:25] -queuebot:#ubuntu-release- New: accepted cpp-httplib [amd64] (noble-proposed) [0.14.3+ds-1]
[16:25] -queuebot:#ubuntu-release- New: accepted cpp-httplib [armhf] (noble-proposed) [0.14.3+ds-1]
[16:25] -queuebot:#ubuntu-release- New: accepted cpp-httplib [riscv64] (noble-proposed) [0.14.3+ds-1]
[16:25] -queuebot:#ubuntu-release- New: accepted cpp-httplib [arm64] (noble-proposed) [0.14.3+ds-1]
[16:25] -queuebot:#ubuntu-release- New: accepted cpp-httplib [s390x] (noble-proposed) [0.14.3+ds-1]
[16:25] -queuebot:#ubuntu-release- New: accepted cpp-httplib [ppc64el] (noble-proposed) [0.14.3+ds-1]
[16:28] <aciba> raof: hi, is there anything we can do to make https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2045582 go forward
[16:28] -ubottu:#ubuntu-release- Launchpad bug 2045582 in cloud-init (Ubuntu Mantic) "sru cloud-init (23.4 update) Focal, Jammy, and Mantic" [Undecided, Fix Committed]
[16:28] <aciba> raof: hi, is there anything we can do to make https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2045582 go forward?
[16:40] <Eickmeyer> arraybolt3: I believe you're in reference to bug 1990621
[16:40] -ubottu:#ubuntu-release- Bug 1990621 in casper (Ubuntu Jammy) "[SRU] PXE Boot contains wrong suggested link to ISO for live file system" [Low, Fix Committed] https://launchpad.net/bugs/1990621
[16:40] <Eickmeyer> sil2100: Did you ever get ahold of Dominik?
[16:41] <arraybolt3> yeah I'm pretty sure that's the one
[16:42] <Eickmeyer> arraybolt3: The tricky part is casper must be *on the iso image* prior to test. One does not simply test it with PXE.
[16:42] <arraybolt3> yeah that's the tricky part with all things casper :P
[16:42] <arraybolt3> so you're right
[16:43] <arraybolt3> perhaps someone needs to figure out how to replicate the ISO build infra locally for that sort of thing, and then make a Wiki on how to do that
[16:43] <Eickmeyer> I believe that's why sil2100 wanted Dominik to do the test.
[16:45] <Eickmeyer> Not much time to jump through all those hoops.
[16:45] <sil2100> Eickmeyer: yes! He mentioned that he'll verify the package this week
[16:45] <Eickmeyer> sil2100: Will that be in time for .4? Seems like we'll have to release without.
[16:50] <arraybolt3> I think it has to be either today or tomorrow, unless we fancy doing all test cases for all images in one day and then releasing later that same day.
[16:52] <arraybolt3> unrelated aside, ubuntu-release: I just made another casper MR because I totally goofed the order in which X sessions are searched when trying to add the kubuntu-live-environment session. If that can be looked at sometime soon, that would be *awesome*, I'd love to be able to ask for the Kubuntu ISO to be respun later today so I can test and make sure everything works right for our
[16:52] <arraybolt3> transition to Calamares.
[16:52] <arraybolt3> s/MR/MP/ (getting Gitlab and Launchpad mixed up)
[16:53] <cjwatson> try being this ex-Launchpad developer who's now working almost entirely in GitLab.  The cognitive dissonance is fun
[16:54] <arraybolt3> :O
[16:54] <Eickmeyer> Adding github to the mix and you get MP/MR/PR
[16:55] <arraybolt3> we really need this to be a standard Git term so we all settle on one thing. It's only a matter of time before we get MS (Merge Suggestion), PD (Pull Demand), or CR (Change Request).
[16:56] <Eickmeyer> git push --set-upstream --force is basically a Pull Demand
[17:03] <ahasenack> ubuntu-archive: hi, I would like to request removal of https://launchpad.net/ubuntu/+source/jupyter-client/8.6.0-0ubuntu1 from noble-proposed, as it's causing https://bugs.launchpad.net/ubuntu/+source/jupyter-notebook/+bug/2054342 and we haven't found a fix for that yet. Upstream has pinned jupyter-client to versions less than 8, so there is no fix coming from there as well
[17:03] -ubottu:#ubuntu-release- Launchpad bug 2054342 in jupyter-notebook (Ubuntu) "FTBFS (test failure) with jupyter-client >= 8" [Undecided, New]
[17:04] <ahasenack> I rebuilt and reran dep8 tests of jupyter-client 7.4.9-2 from noble release, in a ppa, with a patch to workaround https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059658
[17:04] -ubottu:#ubuntu-release- Debian bug 1059658 in src:jupyter-client "jupyter-client: autopkgtest failure with Python 3.12" [Serious, Open]
[17:04] <ahasenack> dep8 log (green): https://autopkgtest.ubuntu.com/results/autopkgtest-noble-ahasenack-plusoneweek/noble/amd64/j/jupyter-client/20240220_164938_21410@/log.gz
[17:04] <ahasenack> ppa: https://launchpad.net/~ahasenack/+archive/ubuntu/plusoneweek/+packages
[17:05] <ahasenack> branch with the patch: https://code.launchpad.net/~ahasenack/ubuntu/+source/jupyter-client/+git/jupyter-client/+ref/jupyter-client-749-deprecated-utcnow
[17:05] <ahasenack> and I'm ready to upload
[17:12] -queuebot:#ubuntu-release- New binary: uwsgi [amd64] (noble-proposed/universe) [2.0.24-2ubuntu1] (no packageset)
[17:12] -queuebot:#ubuntu-release- New binary: uwsgi [s390x] (noble-proposed/universe) [2.0.24-2ubuntu1] (no packageset)
[17:12] -queuebot:#ubuntu-release- New binary: uwsgi [armhf] (noble-proposed/universe) [2.0.24-2ubuntu1] (no packageset)
[17:13] -queuebot:#ubuntu-release- New binary: uwsgi [arm64] (noble-proposed/universe) [2.0.24-2ubuntu1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: uwsgi [ppc64el] (noble-proposed/universe) [2.0.24-2ubuntu1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: dyda [amd64] (noble-proposed/none) [1.41.1-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: python-ulmo [amd64] (noble-proposed/none) [0.8.8+dfsg1-3] (no packageset)
[18:11] -queuebot:#ubuntu-release- New: accepted dyda [amd64] (noble-proposed) [1.41.1-2]
[18:11] -queuebot:#ubuntu-release- New: accepted uwsgi [amd64] (noble-proposed) [2.0.24-2ubuntu1]
[18:11] -queuebot:#ubuntu-release- New: accepted uwsgi [armhf] (noble-proposed) [2.0.24-2ubuntu1]
[18:11] -queuebot:#ubuntu-release- New: accepted uwsgi [s390x] (noble-proposed) [2.0.24-2ubuntu1]
[18:11] -queuebot:#ubuntu-release- New: accepted python-ulmo [amd64] (noble-proposed) [0.8.8+dfsg1-3]
[18:11] -queuebot:#ubuntu-release- New: accepted uwsgi [ppc64el] (noble-proposed) [2.0.24-2ubuntu1]
[18:11] -queuebot:#ubuntu-release- New: accepted uwsgi [arm64] (noble-proposed) [2.0.24-2ubuntu1]
[19:02] <LocutusOfBorg> ubuntu-archive: please kick searx out from noble (Debian bug: #1051510). This will make flask migrate, with Python3.12 compatibility code
[19:02] -ubottu:#ubuntu-release- Debian bug 1051510 in src:searx "searx: SearX upstream is no longer maintained" [Serious, Open] https://bugs.debian.org/1051510
[19:33] -queuebot:#ubuntu-release- Unapproved: wrk (mantic-proposed/universe) [4.1.0-3build1 => 4.1.0-3build2] (no packageset)
[20:38] <doko> jbicha: the new gobject-introspection has a dep: python3:any, the old one: python3 (<< 3.12), python3 (>= 3.11~), python3:any
[20:38] <doko> afaik gobject-introspection only works with the default python3, and you dropped that requirement. does it now work with the non-default as well? asking because I'm seeing uninstallabilities again
[20:40] <tsimonq2> doko: Someone asked me why awscli was removed from Noble, just curious why the removal was done literally two minutes after filing the RC bug when the last upload to Unstable was 8 days ago, the new upstream version has Python 3.12 compatibility, and jbicha force synced only 8 days ago? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064307
[20:40] -ubottu:#ubuntu-release- Debian bug 1064307 in src:awscli "awscli ftbfs with Python 3.12 as the default" [Important, Open]
[20:40] <tsimonq2> https://launchpad.net/ubuntu/+source/awscli/+publishinghistory
[20:40] <tsimonq2> There *has* to be something I'm missing...
[20:40] <tsimonq2> I mean, Python 3.12 is still in proposed...
[20:42] <doko> yes, that's exactly why I removed it. I need a bug reference for removal, so I filed it and removed it. we are aiming to start the time_t transitions at the end of the week, and trying to get python3-defaults and glibc migrated before
[20:47] <tsimonq2> Got it, thanks for the info.
[20:58] <jbicha> doko: gobject-introspection got complex changes done this cycle to enable it to (finally!) support multiarch https://salsa.debian.org/gnome-team/gobject-introspection/-/commit/0cd11ab
[20:58] -ubottu:#ubuntu-release- Commit 0cd11ab in gnome-team/gobject-introspection "d/control: Make g-i-bin Multi-Arch: foreign"
[21:00] <jbicha> also coincides with gobject-introspection upstream moving components to glib2.0 🫤
[21:00] <Eickmeyer> doko: https://launchpad.net/ubuntu/+source/gramps/+publishinghistory "No rdeps" ... Seeded in: ubuntu-edu-secondary ubuntu-edu-tertiary . That's twice now. The first time was "Oops, valid mistake. Sorry for not pinging you." Second time, what gives?
[21:01] <doko> that's nice, but why breaking dependencies for native builds/autopkg tests?
[21:03] <doko> Eickmeyer: well, you can upload a fix, can't you?
[21:03] <doko> at least you noticed that the second time
[21:04] <Eickmeyer> doko: There's already a patch in Salsa. The maintainer is a DD and on the Ubuntu Studio team and was invited to and attended Summit. I've contacted him. However, now that it's removed from the archive, it has to go through *archive review process* if *I* were to upload it.
[21:04] <Eickmeyer> doko: So, you've made life harder for me. Thanks.
[21:05] -queuebot:#ubuntu-release- Unapproved: qemu (mantic-proposed/main) [1:8.0.4+dfsg-1ubuntu3.23.10.2 => 1:8.0.4+dfsg-1ubuntu3.23.10.3] (ubuntu-server, virt)
[21:05] <jbicha> doko: sorry about gobject-introspection. I don't know if the changed python dependency was accidental or not. Could you file a Debian bug for it? (I didn't make the change)
[21:06] <doko> yes, currently doing
[21:07] <jbicha> thank you!
[21:07] <doko> Eickmeyer: no, it doesn't. it had been there before. and we don't have a review process for syncs from Debian
[21:08] <Eickmeyer> doko: I'm neither a DD nor a DM. I am a MOTU, so I can *only* upload to universe and multiverse.
[21:10] <doko> then please file a bug report, prepare a package in a PPA and subscribe ubuntu-sponsors
[21:10] <tsimonq2> I'll volunteer to sponsor right this second. :)
[21:11] <doko> here you go \o/
[21:11] <Eickmeyer> I don't need a sponsor if I'm a MOTU for a package in universe!
[21:11] <cjwatson> Eickmeyer: are you _sure_ that what you're saying is true with respect to Launchpad's behaviour?
[21:11] <cjwatson> Eickmeyer: I'm not convinced it is, from having read through the code just now (though it is a bit of a maze)
[21:11] <cjwatson> I _think_ it will pick up the override from the deleted publication
[21:12] <Eickmeyer> cjwatson: Not entirely, I've just been told (by other AAs) that if packages are deleted from the archive they are subject to re-review.
[21:12] <cjwatson> I think you should try it before rolling with that assumption
[21:12] <Eickmeyer> cjwatson: It was v_orlon that told me this.
[21:13] <cjwatson> It is definitely possible I'm wrong here, and if I am it's not my problem any more anyway :-), but it would be easy to try and would save you time if I happen to be right
[21:13] <cjwatson> (assuming you have an upload ready anyway)
[21:14] <Eickmeyer> cjwatson: I suppose I can give it a shot.
[21:14] <cjwatson> I'm about 60% sure that this doesn't apply for NEW in general, at least within a series; I'm less sure about the interaction with packagesets
[21:15] <cjwatson> But since you're a MOTU, those aren't in play, and I think it would pick up the component (main/restricted/universe/multiverse) from the one it finds in ancestry ...
[21:15] <Eickmeyer> I'll just go with that then.
[21:16] <Eickmeyer> But the whole reason I'm angry: If you remove a *SEEDED* package, *PING THE FLAVOR*. <- doko. That's twice now.
[21:18]  * tsimonq2 considers the point valid but hands Eickmeyer a cup of tea :)
[21:18] <cjwatson> (FWIW, I'm fairly sure Steve's statement _is_ true if the package was removed in a previous series and hasn't yet been in the series you're trying to upload to)
[21:19] <doko> sure, it is removed, to get some fundamental stuff done. You were aware of the issue, could have fixed it as well. and if I remember correctly I checked it using reverse-depends, and apparently missed it
[21:19] <Eickmeyer> I wasn't aware of the issue until it was removed and I did a meta update.
[21:20] <doko> cjwatson: at least Debian syncs end up in NEW for removed packages. but processing these as any other new packages
[21:20] <cjwatson> I wouldn't be at all surprised to find syncs behaving differently
[21:20] <cjwatson> But experimentation would be interesting, anyway
[21:21] <doko> jbicha: filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064369
[21:21] -ubottu:#ubuntu-release- Debian bug 1064369 in gobject-introspection "gobject-introspection dropped versioned dependency on python3" [Serious, Open]
[21:27] <doko> jbicha: https://autopkgtest.ubuntu.com/packages/meson/noble/ppc64el see the one triggered by python3-defaults/3.12.1-0ubuntu1 gobject-introspection/1.79.1-1 apperently not yet enough. what else is missing?
[21:45] <jbicha> doko: I'm trying meson again with all-proposed. It could be that apt/autopkgtest handling just isn't clever enough to figure this out :(
[22:21] <tsimonq2> vorlon, mwhudson: so, uh... https://launchpadlibrarian.net/715322064/buildlog_ubuntu_noble_amd64_xubuntu_BUILDING.txt.gz
[22:21] <tsimonq2> E: Unable to locate package linux
[22:23] <mwhudson> whut
[22:23] <mwhudson> did someone do a seed
[22:24] <Eickmeyer> My guess is it needs a line between 888 and 889 in live-guild/auto/config: "add_package minimal.standard linux-$KERNEL_FLAVOURS"
[22:24] <tsimonq2> Nah, because KERNEL_FLAVOURS is explicitly set to generic for Xubuntu...
[22:24] <Eickmeyer> s/live-guild/live-build
[22:24] <Eickmeyer> tsimonq2: Yes, it is, but that's just How It's Done (tm).
[22:25] <tsimonq2> https://git.launchpad.net/~xubuntu-dev/ubuntu-seeds/+git/xubuntu?h=noble
[22:25] <Eickmeyer> tsimonq2: In their stanza, KERNEL_FLAVOURS=generic
[22:25] <tsimonq2> Eickmeyer: That's what I just said XD
[22:25] <Eickmeyer> tsimonq2: I'm saying it's missing a line for that layer.
[22:26] <Eickmeyer> mwhudson can correct me if I'm wrong.
[22:26] <tsimonq2> OH
[22:26] <tsimonq2> Yes, I think you're right.
[22:27] <tsimonq2> Eickmeyer: so then what's this :) add_package ${LIVE_LAYER_PARENT}.live linux-$KERNEL_FLAVORS
[22:27] <Eickmeyer> tsimonq2: Specifically the live layer, not the standard or minimal layers.
[22:28] <mwhudson> oh no
[22:28] <tsimonq2> ubuntucinnamon)
[22:28] <tsimonq2> add_package minimal.standard.live linux-$KERNEL_FLAVOURS
[22:28] <tsimonq2> https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntucinnamon/
[22:28] <mwhudson> KERNEL_FLAVORS vs KERNEL_FLAVOURS
[22:28] <Eickmeyer> ^
[22:28] <Eickmeyer> There it is.
[22:28] <tsimonq2> lol... nice one :)
[22:29] <Eickmeyer> mwhudson: Also, isn't LIVE_LAYER_PARENT definied in a case and shouldn't it be definied outside the case?
[22:33] <mwhudson> Eickmeyer: well it's defined in both cases so i think that's ok
[22:35] <bluesabre> <3 for the investigation (and fix!)
[22:36] <Eickmeyer> mwhudson: Ok
[22:36] <jbicha> doko: I talked nicely to it and got it to pass: https://autopkgtest.ubuntu.com/packages/meson/noble/ppc64el
[22:42] <arraybolt3> hmm... might be worth doing a KERNEL_FLAVORS="${KERNEL_FLAVOURS}" somewhere in the code since undoubtedly this will happen again if you have Americans writing your code.
[22:43] <Eickmeyer> arraybolt3: In bash, that has to be done periodically because, unlike Python, it's not a one-and-done.
[22:43] <arraybolt3> not sure I grasp your meaning?
[22:44] <Eickmeyer> You'd have to do KERNEL_FLAVORS="${KERNEL_FLAVOURS}" periodically throughout the code every time it changes. For instance, in Ubuntu Studio, it changes to lowlatency.
[22:44] <arraybolt3> oh yuck
[22:45] <arraybolt3> Petition to add pointer support to Bash
[22:45] <Eickmeyer> Exactly. In bash, you have to be consistent with your variables.
[22:46] <tsimonq2> I mean, there's alias support? hah
[22:46] <arraybolt3> for variables? :)
[22:46] <tsimonq2> Only one way to find out...
[22:46] <arraybolt3> doesn't seem to work here (we're in the wrong channel also)
[22:49] <tsimonq2> This is true, on both counds. :D
[22:49] <tsimonq2> *counts
[22:52] <tsimonq2> arraybolt3, Eickmeyer: `declare -n KERNEL_FLAVORS=KERNEL_FLAVOURS` does the trick actually ;)
[22:52] <Eickmeyer> Ah, forgot about declare.
[23:44] -queuebot:#ubuntu-release- New binary: rocalution [amd64] (noble-proposed/none) [5.7.1-2] (no packageset)
[23:49] -queuebot:#ubuntu-release- New binary: rocalution [arm64] (noble-proposed/universe) [5.7.1-2] (no packageset)
[23:50] -queuebot:#ubuntu-release- New binary: rocalution [ppc64el] (noble-proposed/universe) [5.7.1-2] (no packageset)