[00:15] <vorlon> xnox: removed a bunch of binaries; this'll take a couple of passes but I'll stay on top of it
[01:59] <vorlon> sergiodj: so, britney thinks your qemu upload isn't migratable because it makes an awful lot of packages uninstallable: https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_output.txt
[02:12] <sergiodj> vorlon: wait, what? that's new to me
[02:12] <sergiodj> I'm about to go to bed (and today was a holiday here), but I'll take a look at it first thing tomorrow morning
[02:12] <vorlon> sergiodj: ok
[04:25] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (mantic-proposed/main) [23.10.51 => 23.10.52] (desktop-core, i386-whitelist)
[04:38] <vorlon> xnox: ok, livecd-rootfs migrated (casper made it a while ago) and the next daily image is scheduled to build in an hour
[04:44] <vorlon> xnox: and all the NBS binaries are gone from -proposed
[04:44] -queuebot:#ubuntu-release- Unapproved: ssl-cert (mantic-proposed/main) [1.1.2 => 1.1.2ubuntu1] (desktop-core, i386-whitelist, ubuntu-server)
[04:47] <vorlon> xnox: and today's daily image picked up the new linux-raspi
[04:47] <vorlon> EOD
[07:40] -queuebot:#ubuntu-release- Unapproved: sosreport (mantic-proposed/main) [4.5.6-0ubuntu1 => 4.5.6-0ubuntu2] (ubuntu-desktop, ubuntu-server)
[08:12] -queuebot:#ubuntu-release- Unapproved: yt-dlp (mantic-proposed/universe) [2023.07.06-1 => 2023.09.24-2] (no packageset) (sync)
[08:46] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (mantic-proposed) [23.10.52]
[08:50] -queuebot:#ubuntu-release- Unapproved: accepted yt-dlp [sync] (mantic-proposed) [2023.09.24-2]
[08:51] -queuebot:#ubuntu-release- Unapproved: accepted ssl-cert [source] (mantic-proposed) [1.1.2ubuntu1]
[08:52] -queuebot:#ubuntu-release- Unapproved: accepted sosreport [source] (mantic-proposed) [4.5.6-0ubuntu2]
[08:57] -queuebot:#ubuntu-release- Unapproved: linux-firmware (jammy-proposed/main) [20220329.git681281e4-0ubuntu3.19 => 20220329.git681281e4-0ubuntu3.20] (core, kernel)
[10:05] -queuebot:#ubuntu-release- Unapproved: gnome-control-center (mantic-proposed/main) [1:45.0-1ubuntu1 => 1:45.0-1ubuntu2] (ubuntu-desktop)
[10:17] -queuebot:#ubuntu-release- Unapproved: tepl (mantic-proposed/universe) [6.4.0-7ubuntu1 => 6.4.0-7ubuntu2] (no packageset)
[10:48] -queuebot:#ubuntu-release- Unapproved: accepted gnome-control-center [source] (mantic-proposed) [1:45.0-1ubuntu2]
[10:49] -queuebot:#ubuntu-release- Unapproved: ubuntu-wallpapers (mantic-proposed/main) [23.10.3 => 23.10.4] (desktop-core)
[10:49] -queuebot:#ubuntu-release- Unapproved: xubuntu-default-settings (mantic-proposed/universe) [23.10.0 => 23.10.1] (xubuntu)
[10:50] -queuebot:#ubuntu-release- Unapproved: accepted tepl [source] (mantic-proposed) [6.4.0-7ubuntu2]
[10:53] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-wallpapers [source] (mantic-proposed) [23.10.4]
[10:55] -queuebot:#ubuntu-release- Unapproved: accepted xubuntu-default-settings [source] (mantic-proposed) [23.10.1]
[12:13] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (jammy-proposed) [20220329.git681281e4-0ubuntu3.20]
[13:11] -queuebot:#ubuntu-release- Unapproved: veryfasttree (mantic-proposed/universe) [4.0.1+dfsg-2 => 4.0.3+dfsg-1] (no packageset) (sync)
[13:12] -queuebot:#ubuntu-release- Unapproved: accepted veryfasttree [sync] (mantic-proposed) [4.0.3+dfsg-1]
[13:25] -queuebot:#ubuntu-release- Unapproved: casacore (mantic-proposed/universe) [3.5.0-4 => 3.5.0-4ubuntu1] (no packageset)
[13:27] -queuebot:#ubuntu-release- Unapproved: accepted casacore [source] (mantic-proposed) [3.5.0-4ubuntu1]
[13:37] -queuebot:#ubuntu-release- Unapproved: ubuntu-meta (mantic-proposed/main) [1.523 => 1.524] (core)
[13:41] <mitchdz> Anyone know if there a change with the arm64 gcc compiler w.r.t SIMD functions? I'm looking at darktable arm64 build blocking proposed migration. The new synced package & the current package in the main archive (if I rebuild) has a new error and a warning related to SIMD functions.
[13:48] <LocutusOfBorg> mitchdz, since the last build, gcc switched from 12 to 13?
[13:50] <LocutusOfBorg> I'm checking with latest debian http://debomatic-arm64.debian.net/distribution#unstable/darktable/4.4.2-1/buildlog
[13:50] -queuebot:#ubuntu-release- Unapproved: llvm-toolchain-17 (mantic-proposed/universe) [1:17.0.1-1~exp1ubuntu1 => 1:17.0.2-1~exp1ubuntu1] (i386-whitelist)
[13:51] -queuebot:#ubuntu-release- Unapproved: accepted llvm-toolchain-17 [source] (mantic-proposed) [1:17.0.2-1~exp1ubuntu1]
[13:52] <LocutusOfBorg> mitchdz, https://github.com/void-linux/void-packages/issues/21105
[13:52] -ubottu:#ubuntu-release- Issue 21105 in void-linux/void-packages "darktable>=3.0.x: build fails for aarch64* with openmp" [Closed]
[13:54] <LocutusOfBorg> (maybe not the right one)
[13:54] <mitchdz> LocutusOfBorg: That is a very similar warning!
[14:11] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-meta [source] (mantic-proposed) [1.524]
[14:33] <LocutusOfBorg> mitchdz, reproduced on debian arm64
[14:33] <LocutusOfBorg> http://debomatic-arm64.debian.net/distribution#unstable/darktable/4.4.2-1/buildlog
[14:33] <LocutusOfBorg> I issued a rb build and will open an RC bug
[14:33] <LocutusOfBorg> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/darktable.html
[14:35] <mitchdz> LocutusOfBorg: Thanks!
[14:36] <mitchdz> LocutusOfBorg: If you want I can file the bug
[14:42] <LocutusOfBorg> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111677
[14:42] -ubottu:#ubuntu-release- gcc.gnu.org bug 111677 in gcc "arm64 build fails unrecognizable insn [REGRESSION]" [Normal, Unconfirmed]
[14:42] <LocutusOfBorg> I checked gcc-13 4.2.0-2 looks fine, so the regression might be between that one and 4.2.0-4
[15:03] <LocutusOfBorg> mitchdz, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053405
[15:03] -ubottu:#ubuntu-release- Debian bug 1053405 in src:darktable "darktable: FTBFS on arm64 (gcc bug?)" [Serious, Open]
[15:07] <mitchdz> LocutusOfBorg: Thanks for filing those bugs :)
[15:07] <mitchdz> I'll see if I can make the build passing for now
[15:13] <LocutusOfBorg> mitchdz, gcc-12 might be your best friend, at least to check if this is really a gcc regression
[15:13] <LocutusOfBorg> can you please update me?
[15:15] <mitchdz> LocutusOfBorg: I will try that out and update!
[15:20] <LocutusOfBorg> FYI https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/26750619
[15:29] <ricotz> bdmurray, hello :), please take a look at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2037274
[15:29] -ubottu:#ubuntu-release- Launchpad bug 2037274 in libreoffice (Ubuntu Lunar) "[SRU] libreoffice 7.5.7 for lunar" [Medium, In Progress]
[15:36] <vorlon> xnox, dbungert: did we do an end-to-end budgie test with these livecd-rootfs changes? https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/mantic/ubuntu-budgie/+build/506494
[15:54] <dbungert> vorlon: looking
[15:59] <vorlon> xnox: sooooo more NBS packages?  and linux-restricted-modules still unfixed
[16:01] <vorlon> xnox: looks like the new NBSes are all derivative kernels, not uploads of the ones I remember were already NBS
[16:03] <vorlon> also somebody may have beaten me to the NBS removals
[16:06] <LocutusOfBorg> mitchdz, I think it worked
[16:07] <LocutusOfBorg> uploaded
[16:07] <mitchdz> LocutusOfBorg: Nice! I'm still waiting for my build to finish
[16:08] -queuebot:#ubuntu-release- Unapproved: darktable (mantic-proposed/universe) [4.4.2-1 => 4.4.2-1ubuntu1] (ubuntustudio)
[16:10] <Eickmeyer> Thanks LocutusOfBorg ! I was unaware of that. ^
[16:10] <Eickmeyer> LocutusOfBorg: Did you do a NMU?
[16:11] <LocutusOfBorg> Eickmeyer, context?
[16:11] <LocutusOfBorg> I didn't NMU, just uploaded in Ubuntu
[16:11] <Eickmeyer> LocutusOfBorg: Darktable.
[16:11] <LocutusOfBorg> I just opened a bug for gcc folks upstream
[16:11] <LocutusOfBorg> they are usually quick at reducing testcase
[16:11] <Eickmeyer> Ah. Either way, thank you!
[16:11] <LocutusOfBorg> well, I'm reducing it by myself, lets see
[16:15] <LocutusOfBorg> meh, doesn't build on amd64 and I have no arm64 handy chroot
[16:15] <Eickmeyer> yikes
[16:19] <mitchdz> Still FTBFS on arm64 when I used gcc-12 for me https://launchpad.net/~mitchdz/+archive/ubuntu/darktables-mantic/+build/26750644
[16:19] <mitchdz> Same error with SIMD
[16:20] <vorlon> LocutusOfBorg: why are you forcing gcc-12 on all archs for an arm64-specific failure?
[16:20] <LocutusOfBorg> "all" means amd64...
[16:20] <vorlon> where is this?
[16:20] <LocutusOfBorg> vorlon, reject please
[16:20] <vorlon> ah yes, amd64 and arm64
[16:20] <LocutusOfBorg> looks like it failed on another stage
[16:20] <vorlon> ok
[16:21] <LocutusOfBorg> :/ it used to fail at 31% of build meh
[16:21] <LocutusOfBorg> but I have a debian chroot now
[16:21] -queuebot:#ubuntu-release- Unapproved: rejected darktable [source] (mantic-proposed) [4.4.2-1ubuntu1]
[16:32] <dbungert> vorlon: xnox: https://git.launchpad.net/~dbungert/livecd-rootfs/commit/?id=88256be5bf79b58193116b54e8aecac6a2c22f98
[16:32] -ubottu:#ubuntu-release- Commit 88256be in ~dbungert/livecd-rootfs "budgie-kernel budgie-kernel"
[16:35] <mitchdz> so far I've gotten armhf and ppc64el slic3r-prusa to build in -prposed. I know this package has been flaky in the past, just retesting it now to see if anything has magically changed. https://launchpad.net/~mitchdz/+archive/ubuntu/slic3r-prusa-mantic/+builds?build_state=built
[16:35] <mitchdz> Takes a while to build finished 6 minutes ago taking 1 hour 40 minutes
[16:36] <vorlon> dbungert: looks augh to me, so it's probably correct.  Also I spot that ubuntu-oem is missing this too
[16:37] <dbungert> vorlon: I can setup a ppa test or shall we JFDI?  I'm pretty sure this it.
[16:38] <vorlon> dbungert: JFDI, set up a ppa in parallel / after if you want
[16:38] <dbungert> on it
[16:38] <vorlon> dbungert: and the previous successful budgie build had linux in the minimal layer
[16:38] <vorlon> so that tracks
[16:40] -queuebot:#ubuntu-release- Unapproved: ubuntustudio-meta (mantic-proposed/universe) [0.302 => 0.303] (ubuntustudio)
[16:41] <Eickmeyer> vorlon: This was just a final update run for due dillegence. ^
[16:45] <vorlon> seb128: maybe you want to take LP: #2037408 since you did the source accept
[16:45] -ubottu:#ubuntu-release- Launchpad bug 2037408 in fdk-aac-free (Ubuntu) "Please move fdk-aac-free binary packages to universe" [Undecided, New] https://launchpad.net/bugs/2037408
[16:46] <dbungert> vorlon: https://code.launchpad.net/~dbungert/livecd-rootfs/+git/livecd-rootfs/+merge/452674
[16:46] <seb128> vorlon, ack
[16:53] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (mantic-proposed/main) [23.10.52 => 23.10.53] (desktop-core, i386-whitelist)
[16:59] <bdmurray> seb128: Do you know if we should expect an upload of gnome-shell for bug 2036889 before release?
[16:59] -ubottu:#ubuntu-release- Bug 2036889 in gnome-shell (Ubuntu) "gnome-shell crashed with SIGABRT: libmutter:ERROR:../src/backends/x11/meta-barrier-x11.c:231:meta_x11_barriers_free: assertion failed: (g_hash_table_size (x11_barriers->barriers) == 0)" [Medium, In Progress] https://launchpad.net/bugs/2036889
[16:59] <bdmurray> That might be the cause of the "Try Ubuntu" session crash on the legacy image
[17:08] <mitchdz> LocutusOfBorg: darktable builds from source w/ gcc-13 if I disable openmp, not optimal but at least we have it as a data point - https://launchpadlibrarian.net/690201104/buildlog_ubuntu-mantic-arm64.darktable_4.4.2-1ubuntu1~mantic2_BUILDING.txt.gz
[17:14] <seb128> jbicha, ^ any idea about Brian's question?
[17:15] <Eickmeyer> mitchdz: I'm much more of a fan of that than gcc-12.
[17:17] -queuebot:#ubuntu-release- Unapproved: accepted ubuntustudio-meta [source] (mantic-proposed) [0.303]
[17:18] <mitchdz> We can hold a delta to disable openmp on arm64 for darktable until it's fixed so we can migrate. Or would it make more sense to just leave it in proposed until either debian or upstream fixes the build?
[17:22] <Eickmeyer> mitchdz: I'd say if we only disable openmp for arm64 that'd be best, because that way the delta is minimal for amd64.
[17:23] <Eickmeyer> Getting it to migrate, of course, is better than just leaving it in proposed this close to release.
[17:25] -queuebot:#ubuntu-release- Unapproved: grub2-unsigned (mantic-proposed/main) [2.12~rc1-10ubuntu2 => 2.12~rc1-10ubuntu4] (core) (sync)
[17:26] -queuebot:#ubuntu-release- Unapproved: grub2-signed (mantic-proposed/main) [1.195 => 1.197] (core) (sync)
[17:27] <mitchdz> Sounds good. I'll test a change to only disable openmp for arm64 and propose that.
[17:27] <Eickmeyer> mitchdz: 👍
[17:28] -queuebot:#ubuntu-release- Unapproved: grub2 (mantic-proposed/main) [2.12~rc1-10ubuntu2 => 2.12~rc1-10ubuntu4] (core)
[17:28] <juliank> Somebody please accept grub2-unsigned, grub2-signed, grub2 for mantic (vorlon?) - these are the new security update; I included grub2 for consistency to make customers and me happy
[17:29] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (mantic-proposed) [23.10.53]
[17:29] <Eickmeyer> I've seen an upset juliank. It's not good.
[17:36] <juliank> Also the grub2 has the advantage of having a diff :)
[17:48] -queuebot:#ubuntu-release- Unapproved: exim4 (mantic-proposed/main) [4.96-17ubuntu1 => 4.96-17ubuntu2] (ubuntu-server)
[17:48] <jbicha> bdmurray: yes, we'll upload gnome-shell with that patch
[17:49] <bdmurray> jbicha: Do you have a timeline? We'd really like to spin images on Friday
[17:49] <jbicha> bdmurray: I'm looking into it and mutter today
[17:50] <bdmurray> jbicha: mutter for what?
[17:52] <jbicha> bdmurray: we were going to add a build autopkgtest to mutter to hopefully address the concern from bug 1993226
[17:52] -ubottu:#ubuntu-release- Bug 1993226 in mutter (Ubuntu) "mutter autopkgtests fail to detect regressions in mesa" [Undecided, New] https://launchpad.net/bugs/1993226
[17:53] <bdmurray> okay
[17:55] -queuebot:#ubuntu-release- Unapproved: glibc (mantic-proposed/main) [2.38-1ubuntu5 => 2.38-1ubuntu6] (core, i386-whitelist)
[17:58] <sergiodj> vorlon: still trying to get an arm64 where I can test the qemu issue
[18:03] -queuebot:#ubuntu-release- Unapproved: zict (mantic-proposed/universe) [3.0.0-2 => 3.0.0-2ubuntu1] (no packageset)
[18:03] <jbicha> vorlon: could you review rust-convert-case NEW binaries in mantic? I believe you accepted the source package last week
[18:04] -queuebot:#ubuntu-release- Unapproved: accepted zict [source] (mantic-proposed) [3.0.0-2ubuntu1]
[18:07] <vorlon> sergiodj: it's not arch-specific; each britney run picks a different arch at random to check installability on first
[18:07] <vorlon> jbicha: yes I'll look
[18:07] <sergiodj> vorlon: I couldn't see any issues when trying on amd64
[18:08] <sergiodj> but it was late and maybe I missed something.  either way, I'm getting an arm64 now just in case
[18:17] <vorlon> I also could not reproduce it on amd64 but one of the update_output.txt pages did show the uninstallables on amd64
[18:17] <vorlon> let me see what I can reproduce
[18:18] <mitchdz> Have MP up for darktable, but Q: since LocutusOfBorg uploaded 4.4.2-1ubuntu1 which got rejected, should I make my new version 4.4.2-1ubuntu2 or can I reuse 4.4.2-1ubuntu1?  https://code.launchpad.net/~mitchdz/ubuntu/+source/darktable/+git/darktable/+merge/452678
[18:18] <vorlon> mitchdz: you can reuse
[18:18] <mitchdz> vorlon: Thanks
[18:21] -queuebot:#ubuntu-release- Unapproved: gnome-shell (mantic-proposed/main) [45.0-1ubuntu1 => 45.0-1ubuntu2] (desktop-extra, mozilla, ubuntu-desktop)
[18:22] -queuebot:#ubuntu-release- Unapproved: accepted grub2-unsigned [sync] (mantic-proposed) [2.12~rc1-10ubuntu4]
[18:23] <mitchdz> LocutusOfBorg: Eickmeyer: mind taking a look at that MP  I mentioned a few lines up and uploading if you are happy with it?
[18:24] <Eickmeyer> mitchdz: Looking...
[18:24] <mitchdz> Eickmeyer: Thanks, let me know if you want me to test any changes
[18:25] <Eickmeyer> mitchdz: I have no way to test the arm changes, but I do see that it built cleanly in your PPA. I'm still checking to see if it does anything to the amd64 build, which I'm assuming at this point it doesn't.
[18:28] <vorlon> apw: remind me, is there supposed to be a bot that autorejects uefi signing requests in the queue? https://launchpad.net/ubuntu/mantic/+queue?queue_state=1
[18:28] <Eickmeyer> mitchdz: I approve. Do you need it sponsored or can you upload?
[18:28] -queuebot:#ubuntu-release- Unapproved: accepted grub2-signed [sync] (mantic-proposed) [1.197]
[18:29] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (mantic-proposed) [2.12~rc1-10ubuntu4]
[18:29] <vorlon> juliank: cd-boot-images-*?
[18:29] <juliank> vorlon: tomorrow, when back from holiday!
[18:30] <vorlon> k
[18:30] <sergiodj> vorlon: I installed all packages listed in the report and everything succeeded. huh...
[18:31] <sergiodj> I see that ppc64el is now listed as the architecture that was tested.  let me try with it
[18:34] -queuebot:#ubuntu-release- Unapproved: accepted exim4 [source] (mantic-proposed) [4.96-17ubuntu2]
[18:39] -queuebot:#ubuntu-release- Unapproved: accepted glibc [source] (mantic-proposed) [2.38-1ubuntu6]
[18:40] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell [source] (mantic-proposed) [45.0-1ubuntu2]
[18:45] <vorlon> sergiodj: qemu-system-data is missing from mantic-proposed
[18:46] <sergiodj> ah
[18:46] <vorlon> sergiodj: here's the apt preferences I used to reproduce it https://paste.ubuntu.com/p/7q9Bq8pcqD/
[18:46] <sergiodj> that's probably a side effect of the last upload.  sigh
[18:46] <sergiodj> thanks
[18:46] -queuebot:#ubuntu-release- Unapproved: libx11 (mantic-proposed/main) [2:1.8.6-1 => 2:1.8.6-1ubuntu1] (core, i386-whitelist, xorg)
[18:46] -queuebot:#ubuntu-release- Unapproved: libxpm (mantic-proposed/main) [1:3.5.12-1.1 => 1:3.5.12-1.1ubuntu1] (core, i386-whitelist, xorg)
[18:49] -queuebot:#ubuntu-release- New: accepted rust-convert-case [amd64] (mantic-proposed) [0.6.0-0ubuntu2]
[18:50] -queuebot:#ubuntu-release- New: accepted rust-convert-case [armhf] (mantic-proposed) [0.6.0-0ubuntu2]
[18:50] -queuebot:#ubuntu-release- New: accepted rust-convert-case [riscv64] (mantic-proposed) [0.6.0-0ubuntu2]
[18:50] -queuebot:#ubuntu-release- New: accepted rust-convert-case [arm64] (mantic-proposed) [0.6.0-0ubuntu2]
[18:50] -queuebot:#ubuntu-release- New: accepted rust-convert-case [s390x] (mantic-proposed) [0.6.0-0ubuntu2]
[18:50] -queuebot:#ubuntu-release- New: accepted rust-convert-case [ppc64el] (mantic-proposed) [0.6.0-0ubuntu2]
[18:53] -queuebot:#ubuntu-release- New: accepted rust-ansi-str [sync] (mantic-proposed) [0.8.0-1]
[18:53] -queuebot:#ubuntu-release- New: accepted rust-gweather-sys [sync] (mantic-proposed) [4.3.0-2]
[18:53] -queuebot:#ubuntu-release- New: accepted rust-ansitok [sync] (mantic-proposed) [0.2.0-1]
[18:56] -queuebot:#ubuntu-release- New binary: rust-ansitok [amd64] (mantic-proposed/none) [0.2.0-1] (no packageset)
[18:56] -queuebot:#ubuntu-release- New binary: rust-gweather-sys [amd64] (mantic-proposed/none) [4.3.0-2] (no packageset)
[18:56] -queuebot:#ubuntu-release- New binary: rust-ansitok [armhf] (mantic-proposed/none) [0.2.0-1] (no packageset)
[18:57] -queuebot:#ubuntu-release- New binary: rust-ansitok [ppc64el] (mantic-proposed/none) [0.2.0-1] (no packageset)
[18:57] -queuebot:#ubuntu-release- New binary: rust-gweather-sys [ppc64el] (mantic-proposed/none) [4.3.0-2] (no packageset)
[18:57] -queuebot:#ubuntu-release- New binary: rust-gweather-sys [arm64] (mantic-proposed/none) [4.3.0-2] (no packageset)
[18:58] -queuebot:#ubuntu-release- New binary: rust-gweather-sys [s390x] (mantic-proposed/none) [4.3.0-2] (no packageset)
[18:59] -queuebot:#ubuntu-release- New binary: rust-gweather-sys [armhf] (mantic-proposed/none) [4.3.0-2] (no packageset)
[19:00] -queuebot:#ubuntu-release- New binary: rust-ansitok [arm64] (mantic-proposed/universe) [0.2.0-1] (no packageset)
[19:00] -queuebot:#ubuntu-release- New binary: rust-ansitok [s390x] (mantic-proposed/universe) [0.2.0-1] (no packageset)
[19:08] -queuebot:#ubuntu-release- New binary: rust-ansitok [riscv64] (mantic-proposed/universe) [0.2.0-1] (no packageset)
[19:08] -queuebot:#ubuntu-release- New binary: rust-gweather-sys [riscv64] (mantic-proposed/universe) [4.3.0-2] (no packageset)
[19:09] -queuebot:#ubuntu-release- Unapproved: python-duniterpy (mantic-proposed/universe) [1.1.0-3 => 1.1.0-3ubuntu1] (no packageset)
[19:09] <LocutusOfBorg> mitchdz, please also mention debian bug?
[19:09] -queuebot:#ubuntu-release- Unapproved: accepted python-duniterpy [source] (mantic-proposed) [1.1.0-3ubuntu1]
[19:11] <sergiodj> so, Debian qemu dropped the dh sequencer and is now invoking each build step manually.  this broke qemu-system-data in Ubuntu but not in Debian, where it's built as part of the "all" architecture
[19:12] <sergiodj> d/rules is now more confusing than before; I'm trying to understand how to fix it
[19:13] <tsimonq2> Could be worse, I hear CDBS is a treat. ;)
[19:14] <sergiodj> I've had my share of CDBS for my entire life already :)
[19:14] <tsimonq2> Regardless, it's slightly surprising that dh no longer... fits their package?
[19:15] <sergiodj> it's a long and somewhat complicated story...
[19:15] <sergiodj> but I'm disappointed, too
[19:15] <Eickmeyer> Sounds like a regression to me, and I'd be surprised if it's even policy.
[19:18] <mitchdz> LocutusOfBorg: I mentioned the debian bug in the LP bug I have tied to the MP https://bugs.launchpad.net/ubuntu/+source/darktable/+bug/2038351 Is there a different debian bug you'd like me to link?
[19:18] -ubottu:#ubuntu-release- Launchpad bug 2038351 in darktable (Ubuntu) "darktable FTBFS" [Undecided, New]
[19:18] <mitchdz> Or link the debian bug directly on the MP
[19:19] <Eickmeyer> mitchdz: I think he meant in the changelog.
[19:19] <mitchdz> ah
[19:19] <mitchdz> I assumed if someone sees this they will go to the LP bug and see the debian bug there
[19:20] <Eickmeyer> Not necessarily. Oftentimes Debian folks can't be bothered to look at Launchpad.
[19:20]  * Eickmeyer has experienced that.
[19:20] <mitchdz> That's understandable. Would you like me to make that change to the MP right now?
[19:21] <Eickmeyer> That would be preferable, before it's merged.
[19:21] <mitchdz> Will do
[19:21] <tsimonq2> *shrug* I mean, he could also be talking about closing the Debian bug in the Ubuntu upload, which has an added benefit of including it in the .changes file (basically a no-op but helps for reference in case someone does a requestsync in the future.)
[19:22] <Eickmeyer> tsimonq2: Yes, that's what I meant by referencing the Debian bug in the changelog, and 99.9% sure that's what LocutusOfBorg meant because he had that in the previous upload.
[19:22] <Eickmeyer> tsimonq2: Also, mitchdz is using git-ubuntu for this.
[19:22] <tsimonq2> Eickmeyer: Fancy.
[19:23] <Eickmeyer> Yeah, I don't even know how to use git-ubuntu. I'm old-school trained. *blames tsimonq2 et al*
[19:25] <mitchdz> Is there a specific way I should reference the debian bug in the changelog so our tools see it and be happy when a future sync happens?
[19:26] <Eickmeyer> mitchdz: Debian sees it with (Closes: #xxxxx).
[19:26] <mitchdz> Eickmeyer: Wonderful, thanks
[19:26] <Eickmeyer> np
[19:27] <Eickmeyer> mitchdz: However, because it's a gcc bug, perhaps just referencing the bug number is more appropriate than closing it.
[19:28] <Eickmeyer> LocutusOfBorg: ^ Correct me if I'm wrong.
[19:28] <mitchdz> It's trending to be gcc
[19:28] <Eickmeyer> Right
[19:29] <mitchdz> https://code.launchpad.net/~mitchdz/ubuntu/+source/darktable/+git/darktable/+merge/452678 looks good now?
[19:29] <Eickmeyer> mitchdz: To me that looks perfect. Does this need sponsoring?
[19:29] <mitchdz> Yes I need a sponsor :)
[19:29] <Eickmeyer> Can do.
[19:31] <tsimonq2> Actually...
[19:31] <Eickmeyer> tsimonq2: ?
[19:31] <tsimonq2> mitchdz: Proper syntax for closing Debian bugs is Closes: #XXXXXXX
[19:31] <Eickmeyer> mitchdz: Read up. We don't want to close it, it's a gcc bug.
[19:31] <Eickmeyer> er... tsimonq2 ^
[19:32] <tsimonq2> You can't close Debian bugs from Launchpad ;)
[19:32] <Eickmeyer> tsimonq2: That's not the point. When it's merged in (which LocutusOfBorg plans to do), we don't want it to close.
[19:32] <tsimonq2> Actually, there *is* a different syntactically-correct way to *reference* a bug but not *close* it.
[19:32] <Eickmeyer> The bug being referenced (Debian Bug 1053405) should *not* be closed.
[19:32] -ubottu:#ubuntu-release- Debian bug 1053405 in src:darktable "darktable: FTBFS on arm64 (gcc bug?)" [Serious, Open] https://bugs.debian.org/1053405
[19:33] <tsimonq2> Eickmeyer: I know. But the syntax isn't right.
[19:33]  * tsimonq2 references policy for the best happy medium
[19:33] <Eickmeyer> Then what's the best way to reference it?
[19:37] <tsimonq2> I really really thought there was a way, but I'm struggling to find it.
[19:37] <tsimonq2> I've done this before.
[19:37] <Eickmeyer> This was just supposed to be a comment in the changelog, nothing more, as I see it.
[19:37] <tsimonq2> Give me like 5 minutes, if I can't find it, JFDI :)
[19:38] <mitchdz> I copied the syntax in this commit https://salsa.debian.org/debian-phototools-team/darktable/-/commit/d8a10bcbdf88cb35f4aa2e117bf6a728e750391e
[19:38] -ubottu:#ubuntu-release- Commit d8a10bc in debian-phototools-team/darktable "changelog for 4.2.1-1"
[19:38] <Eickmeyer> tsimonq2: ^ That seems sane enough.
[19:39] <mitchdz> I just lied because I added a : after bug, but I think that should be fine
[19:39] <Eickmeyer> mitchdz: The : might be what he's questioning.
[19:40] <mitchdz> It's easy enough for me to remove that :)
[19:40] <mitchdz> I'll wait to see if there's a more specific way
[19:40] <Eickmeyer> Right. I'm giving him until 15 to the hour.
[19:40] <tsimonq2> I really thought you could do like a References: #XXXXXX or etc and it would just DTRT WRT the changes file. It's looking like that's not the case.
[19:41] <Eickmeyer> tsimonq2: Yeah, anything I've ever seen it's just a comment in the bug and is completely NOOP.
[19:41] <Eickmeyer> s/bug/changelog
[19:41] <tsimonq2> *shrug* the other option might be adding glibc as an affected package in the Debian bug and letting it be closed for that specific package.
[19:42] <tsimonq2> At this point, do what you have to do :)
[19:42] <Eickmeyer> tsimonq2: ack
[19:42] <Eickmeyer> mitchdz: uploading shortly.
[19:42] <mitchdz> Eickmeyer: sounds good
[19:42] <tsimonq2> Eickmeyer: Thanks for taking the lead on sponsoring this, and for holding off even though I ended up being incorrect.
[19:42] <tsimonq2> mitchdz: And thank *you* for a clean diff. :)
[19:42]  * tsimonq2 goes back to the shadows
[19:43] <Eickmeyer> tsimonq2: No worries. It's a package seeded in Ubuntu Studio, so it's something I *should* be leading on.
[19:43] <tsimonq2> I agree :)
[19:44] <mitchdz> Thanks Eickmeyer: and tsimonq2: for helping out so quickly!
[19:45] <tsimonq2> mitchdz: Get some upload rights soon, eh? :)
[19:46] <apw> vorlon, there is indeed supposed to be a bot rejecting them
[19:46] <vorlon> apw: yeah and it did its thing within a few minutes of me asking :)
[19:47] -queuebot:#ubuntu-release- Unapproved: darktable (mantic-proposed/universe) [4.4.2-1 => 4.4.2-1ubuntu1] (ubuntustudio)
[19:47] <Eickmeyer> mitchdz: ^ uploaded, go ahead and mark your MP as merged.
[19:47] <apw> vorlon, ahh yes, its about 10m-ly
[19:47] <mitchdz> Eickmeyer: done!
[19:48] <Eickmeyer> mitchdz: Awesome. Thanks for your help with that!
[19:49] <vorlon> does anyone want to debug why britney is again taking so long to iterate, when the number of packages to migrate and the number of autopkgtests we're waiting for are so small
[19:50] <vorlon> we're back up to ~1h intervals
[19:51] <Eickmeyer> It's running on a pentium. 🤷
[19:52] <tsimonq2> vorlon: How are you making that determination? All the logs I'm seeing show maybe 5 minutes (which is amazing for Britney!!!!): https://ubuntu-archive-team.ubuntu.com/proposed-migration/log/mantic/2023-10-03/
[19:53] <tsimonq2> (Is it maybe just a cronjob that's set too-infrequently?)
[19:53] <vorlon> tsimonq2: 5 minutes isn't accurate either? 18:49 -> 19:18 == 29m
[19:53] <vorlon> (the notest logs don't count)
[19:54] <vorlon> but you're right, that's not an hour, yet https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html is old; so this could be rsync propagation delay
[19:55] <tsimonq2> This has me slightly curious, as a side note: "Tue, 03 Oct 2023 19:29:42 +0000\nSTATS:\nFinished at: Tue, 03 Oct 2023 19:34:03 +0000"
[19:56] <tsimonq2> (If that's actually doing something productive, it's not very verbose. :P )
[19:56] <vorlon> aha no worse, it's caching
[19:57] <vorlon> ok I'll see about fixing that
[19:57] <tsimonq2> hah nice, thanks :)
[19:59]  * tsimonq2 almost wonders if a .path systemd unit would do the trick... working dir copies to staging dir which is then synced with prod... or similar...
[19:59] -queuebot:#ubuntu-release- New source: mailman-hyperkitty (jammy-proposed/primary) [1.2.1-1~ubuntu22.04.1]
[20:11] -queuebot:#ubuntu-release- Unapproved: debian-keyring (mantic-proposed/universe) [2023.05.26 => 2023.09.24] (no packageset) (sync)
[20:11] -queuebot:#ubuntu-release- Unapproved: rust-libspa (mantic-proposed/universe) [0.6.0-3 => 0.7.2-2] (no packageset) (sync)
[20:11] <tsimonq2> calamares-settings-ubuntu is incoming, it will need a binary NEW review. I'm removing the Ubuntu Studio configuration (cc Eickmeyer) since they no longer use Calamares.
[20:12] -queuebot:#ubuntu-release- Unapproved: accepted debian-keyring [sync] (mantic-proposed) [2023.09.24]
[20:12] -queuebot:#ubuntu-release- Unapproved: accepted rust-libspa [sync] (mantic-proposed) [0.7.2-2]
[20:12] <Eickmeyer> tsimonq2: No problem there since ubiquity is in full-swing for Ubuntu Studio in mantic.
[20:13] -queuebot:#ubuntu-release- Unapproved: calamares-settings-ubuntu (mantic-proposed/universe) [1:23.10.3 => 1:23.10.4] (lubuntu, ubuntustudio)
[20:13] <tsimonq2> ^ Thanks for confirming.
[20:14] <Eickmeyer> I mean, considering I've been working with vorlon on some ubiquity items, at least he knows. :)
[20:17] -queuebot:#ubuntu-release- Unapproved: accepted libx11 [source] (mantic-proposed) [2:1.8.6-1ubuntu1]
[20:21] <vorlon> ok, https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html should no longer have any caching in front of it HOWEVER the existing cached pages have to expire out on some of the frontends before this takes effect
[20:21] <sergiodj> for some reason, one of the targets inside d/rules is only being called once.  hmm
[20:25] -queuebot:#ubuntu-release- Unapproved: accepted libxpm [source] (mantic-proposed) [1:3.5.12-1.1ubuntu1]
[20:30] <vorlon> -fopenmp uh ok well that's new to me
[20:30] <vorlon> mitchdz: you should be forwarding your patch upstream to the Debian bug
[20:31] -queuebot:#ubuntu-release- Unapproved: accepted darktable [source] (mantic-proposed) [4.4.2-1ubuntu1]
[20:31] <Eickmeyer> vorlon: Speaking on behalf of mitchdz and LocutusOfBorg, it's already there.
[20:31] <Eickmeyer> Or, at least, that's the plan.
[20:32] <mitchdz> vorlon: Eickmeyer: it's not yet. I'll propose it now.
[20:32] <vorlon> mitchdz: thanks
[20:32] <mitchdz> Thanks
[20:33] <sergiodj> OK, I think I have a fix for it.  testing now
[20:35] -queuebot:#ubuntu-release- Unapproved: rejected calamares-settings-ubuntu [source] (mantic-proposed) [1:23.10.4]
[20:42] <tsimonq2> Sounds good, I'll dput it first thing next cycle. :)
[21:28] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (mantic-proposed/main) [23.10.53 => 23.10.54] (desktop-core, i386-whitelist)
[21:29] <vorlon> seb128: ^^ push to git please
[21:30] <seb128> vorlon, pushed
[21:30] <vorlon> ta
[21:31] <seb128> np, sorry I got sidetracked while I was trying to commit/push/upload
[21:35] -queuebot:#ubuntu-release- Unapproved: rust-pipewire (mantic-proposed/universe) [0.6.0-2build1 => 0.7.2-1] (no packageset) (sync)
[21:36] -queuebot:#ubuntu-release- Unapproved: accepted rust-pipewire [sync] (mantic-proposed) [0.7.2-1]
[21:38] <vorlon> ok fixed the caching issues with proposed-migration, just in time for the runs to again take a long time because of glibc
[21:56] -queuebot:#ubuntu-release- Unapproved: bibshelf (mantic-proposed/universe) [1.6.0-0ubuntu5 => 1.6.0-0ubuntu6] (no packageset)
[21:57] -queuebot:#ubuntu-release- Unapproved: accepted bibshelf [source] (mantic-proposed) [1.6.0-0ubuntu6]
[22:19] <sergiodj> vorlon: would you like to do a quick review? https://code.launchpad.net/~sergiodj/ubuntu/+source/qemu/+git/qemu/+merge/452691
[22:22] <vorlon> sergiodj: no :) please upload and I'll review there
[22:22] <sergiodj> ack
[22:25] -queuebot:#ubuntu-release- Unapproved: qemu (mantic-proposed/main) [1:8.0.4+dfsg-1ubuntu2 => 1:8.0.4+dfsg-1ubuntu3] (ubuntu-server, virt)
[22:25] <sergiodj> vorlon: ^
[22:28] -queuebot:#ubuntu-release- Unapproved: accepted qemu [source] (mantic-proposed) [1:8.0.4+dfsg-1ubuntu3]
[22:29] <sergiodj> thanks
[22:46] -queuebot:#ubuntu-release- Unapproved: mutter (mantic-proposed/main) [45.0-2ubuntu1 => 45.0-3ubuntu1] (desktop-core, desktop-extra)
[22:52] -queuebot:#ubuntu-release- Unapproved: rust-ashpd (mantic-proposed/universe) [0.6.2-2ubuntu2 => 0.6.2-2ubuntu3] (no packageset)
[22:52] -queuebot:#ubuntu-release- Unapproved: accepted rust-ashpd [source] (mantic-proposed) [0.6.2-2ubuntu3]
[23:05] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (mantic-proposed/main) [0.142ubuntu14 => 0.142ubuntu15] (core, i386-whitelist)
[23:22] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (mantic-proposed) [23.10.54]
[23:23] -queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (mantic-proposed) [0.142ubuntu15]
[23:27] <vorlon> +Test-Command: echo "ok"
[23:27] <vorlon> haha
[23:27] <vorlon> I don't disapprove
[23:28] -queuebot:#ubuntu-release- Unapproved: accepted mutter [source] (mantic-proposed) [45.0-3ubuntu1]
[23:31] -queuebot:#ubuntu-release- New: accepted obfuscate [source] (mantic-proposed) [0.0.9-0ubuntu1]
[23:40] -queuebot:#ubuntu-release- New: accepted rust-ansitok [arm64] (mantic-proposed) [0.2.0-1]
[23:40] -queuebot:#ubuntu-release- New: accepted rust-ansitok [riscv64] (mantic-proposed) [0.2.0-1]
[23:40] -queuebot:#ubuntu-release- New: accepted rust-gweather-sys [arm64] (mantic-proposed) [4.3.0-2]
[23:40] -queuebot:#ubuntu-release- New: accepted rust-gweather-sys [ppc64el] (mantic-proposed) [4.3.0-2]
[23:40] -queuebot:#ubuntu-release- New: accepted rust-gweather-sys [s390x] (mantic-proposed) [4.3.0-2]
[23:40] -queuebot:#ubuntu-release- New: accepted rust-ansitok [ppc64el] (mantic-proposed) [0.2.0-1]
[23:40] -queuebot:#ubuntu-release- New: accepted rust-gweather-sys [armhf] (mantic-proposed) [4.3.0-2]
[23:40] -queuebot:#ubuntu-release- New: accepted rust-ansitok [s390x] (mantic-proposed) [0.2.0-1]
[23:40] -queuebot:#ubuntu-release- New: accepted rust-gweather-sys [riscv64] (mantic-proposed) [4.3.0-2]
[23:40] -queuebot:#ubuntu-release- New: accepted rust-ansitok [amd64] (mantic-proposed) [0.2.0-1]
[23:40] -queuebot:#ubuntu-release- New: accepted rust-gweather-sys [amd64] (mantic-proposed) [4.3.0-2]
[23:41] -queuebot:#ubuntu-release- New: accepted rust-ansitok [armhf] (mantic-proposed) [0.2.0-1]
[23:41] -queuebot:#ubuntu-release- New binary: obfuscate [amd64] (mantic-proposed/none) [0.0.9-0ubuntu1] (no packageset)
[23:42] -queuebot:#ubuntu-release- New binary: obfuscate [ppc64el] (mantic-proposed/none) [0.0.9-0ubuntu1] (no packageset)
[23:42] -queuebot:#ubuntu-release- New binary: obfuscate [s390x] (mantic-proposed/none) [0.0.9-0ubuntu1] (no packageset)
[23:54] -queuebot:#ubuntu-release- New binary: obfuscate [arm64] (mantic-proposed/none) [0.0.9-0ubuntu1] (no packageset)


[02:53] <psusi> I thought that the opinion status was supposed to be different than invalid, but it seems to be hidden from all searches just like invalid.  am I not seeing a difference that is there, or shouldn't it show up when doing a text search for a bug, just not when listing open bugs in a particular package?
[02:55] <wgrant> psusi: There is no functional difference between Invalid, Opinion and Won't Fix, except that Won't Fix and Opinion can only be set by the bug supervisor.
[02:58] <psusi> wgrant, umm... shouldn't there be some difference?  I mean... why have them if there is no difference?  I would think that won't fix and opinion should show up when a user goes to report a new bug and searches to see if it has already been reported, but invalid wouldn't
[02:58] <wgrant> psusi: That is one of the big unanswered questions of the universe.
[02:58] <nhomar00> Hello
[02:58] <psusi> wgrant, let there be light ;)
[02:59] <nhomar00> I'm  using Lp topost a blueprint, and when i suscribe my team to the blueprint it is shown in "gray" and the tooltip is telling "No longer Uses Launchpad", somebody knows what it means?
[02:59] <wgrant> nhomar00: Which blueprint, and which team?
[03:00] <nhomar00> https://blueprints.launchpad.net/openerp-venezuela-localization/+spec/requisitos-fiscales-6.0
[03:00] <nhomar00> look suscribers
[03:00] <nhomar00> team: openerp-venezuela
[03:03] <nhomar00> Hello :-s - so difficult ¿?
[03:03] <wgrant> nhomar00: Have you tried refreshing the page?
[03:03] <wgrant> It looks OK for me now.
[03:03] <wgrant> But there is a problem here.
[03:05] <wgrant> Ahh
[03:07] <nhomar00> well
[03:07] <nhomar00> aomething is wrong
[03:07] <nhomar00> something
[03:07] <nhomar00> i refreshed
[03:07] <wgrant> The subscriber listing shows the wrong icon for teams.
[03:07] <wgrant> Sometimes.
[03:08] <nhomar00> mmm, BTW the tool tip is telling "no longer uses launchpad"
[03:08] <nhomar00> I'm worried about this
[03:08] <nhomar00> we use a LOT LP ;-)
[03:08] <wgrant> It's assuming that everyone in that list is a person, not a team.
[03:08] <wgrant> So it calls is_valid_person to determine which icon to show... and is_valid_person is False for teams.
[03:09] <wgrant> So it's nothing to worry about.
[03:09] <wgrant> Just a display bug.
[03:09] <nhomar00> ok ok ok ok ok
[03:09] <nhomar00> i got it
[03:09] <nhomar00> fine!
[03:09] <nhomar00> good answer
[03:09] <nhomar00> but must i publish a bug for this?
[03:10] <nhomar00> or it should be in roadmap already?
[03:10] <wgrant> Let me check if there's one already.
[03:14] <wgrant> Bug #516301
[03:25]  * lifeless makes it high
[03:29] <nhomar00> I can see
[03:30] <nhomar00> THANKS
[03:31] <cody-somerville> Weird. It doesn't say "no longer uses launchpad" and the icon isn't grayed out for me.
[03:32] <wgrant> cody-somerville: It depends on who you're logged in as.
[03:32] <wgrant> We have a caching bug.
[03:32] <wgrant> Something is populated is_valid_person incorrectly.
[03:33] <wgrant> (it should always be False for a team0
[15:59] <mwb_suse> hi.  is anyone around familiar with the api, specifically the PATCH calls?
[17:24] <Ampelbein> hi there! I'm having trouble accessing staging.lp.net via the python api, getting a "Unknown access token (c1gqlQh03cMKsfkm3V4T)." error. production works without problem
[19:18] <james_w> Ampelbein, are you trying to use a token that you got a few days ago?
[19:18] <james_w> Ampelbein, if so then delete it and get a new one
[19:18] <james_w> staging gets reset frequently, and so will forget about the tokens
[19:29] <Ampelbein> james_w: thanks, that was it. on  that note, the keyring entry is named "network password", it isn't immediately obvious that this is for lplib.
[19:29] <james_w> Ampelbein, you could file a bug about that
[19:31] <Ampelbein> will do
[19:32] <Ampelbein> thanks again ;-)
[21:53] <bdrung> maxb: regarding https://code.launchpad.net/~jd-team/jdownloader/trunk - the read-protected subtree is not needed. is it possible to ignore that subtree and continue the import?
[21:56] <maxb> bdrung: No. bzr-svn's design doesn't really permit such a thing
[21:58] <bdrung> maxb: and it can't be work around manually?
[22:34] <maxb> bdrung: Manually? There isn't really any scope for "manually" perturbing the results of a bzr-svn conversion
[22:36] <maxb> I guess you should talk to jelmer for a final word on this, but I think you're out of luck on this unless you contrive to set up a svnsync-ed mirror of the upstream, and then have bzr-svn import from that
[22:37] <maxb> If you do such a thing, it would be good to ensure the svnsynced svn repository has a different uuid to the original, since it will contain elided content
[22:39] <bdrung> maxb: no way for doing something for one time and then let the LP importer continue the imports?
[22:48] <maxb> I'd be shocked if you didn't run into errors due to data inconsistencies very quickly
[23:37] <blueyed> The vim code imports appear to not work anymore? https://code.launchpad.net/vim
[23:46] <spiv> blueyed: known bug
[23:46] <spiv> blueyed: oh, you don't mean package imports
[23:47] <spiv> Might still be a known bug of course!
[23:49] <spiv> Hmm, I don't see one filed.
[23:51] <blueyed> I wanted to use it for recipes, but when it's broken then there's not much reason..
[23:51] <spiv> Filed.
[23:51] <spiv> https://bugs.launchpad.net/bzr-hg/+bug/738498
[23:53] <blueyed> Thanks, spiv.


[09:11] <froud> hi, can anyone point me to or list the differences between a server or workstation install of Kubuntu?
[09:40] <froud> anyone awake?
[10:58] <uniq> riddell: non of them are ready for review. they are old. i have ggz-kde-games ready.
[10:59] <uniq> but thanks for reviews anyway.
[11:03] <uniq> i'll get started cleaning some of that mess up.
[11:34] <uniq> riddell: new kio-locate up.
[01:47] <uniq> riddell: fixed ggz-kde-games uploading.


[01:56] <Unit193> bluesabre: OK, I won't bother you then.  Did you see the ping re: xfce4-session and lightdm?
[07:37] -SwissBot:#xubuntu-devel- ATTN: Xubuntu Core 23.04 - amd64 - amd64 built.
[15:54]  * arraybolt3 notices the Xubuntu Core ISO show up
[15:56] <arraybolt3> Zsync in progress.
[20:08] <arraybolt3> Flashing the Core ISO, will test it on my EFI Chromebook shortly.
[21:57] <arraybolt3> Unsure if this was a problem before, but on my Dell Chromebook... 3120, I believe? I'm noticing that my screen is rapidly flashing (not super-noticably, but definitely flashing a bit with Xubuntu Core 23.04.
[21:58] <arraybolt3> Hmm, now it stopped. Maybe it was just the screen recovering while powering back on (I think I half-bricked the firmware on this particular machine, it boots when it feels like it and doesn't when it doesn't unless you fiddle with it a good amount).
[21:58] <arraybolt3> Anyway, false alarm. ISO boots, used it to entirely zero the storage on the system which succeeded, now doing an installation test.
[22:00] <arraybolt3> I'm doing one final test to make sure that the internal storage really is entirely zeroed, then we'll try to install. (I don't usually fully zero storage like this but this time around I wanted to try it.)
[23:19] <Unit193> Good that it works, it's too early for something to break it. :P
[23:20] <Unit193> Note too that this is the first ISO with pipewire.


[01:08] <JanC> does the abi-check script that Ubuntu uses depend on modversions?
[01:17] <JanC> background: https://lwn.net/Articles/707520/