[00:55] <vorlon> xnox: I have no specific reason to want that branch owned by ~ubuntu-release when livecd-rootfs is owned by ~ubuntu-core-dev.  sil2100 set it up, so you might want to ask him when he's back.  But core-dev is no better than ubuntu-release as a default reviewer, neither generates email notifications
[00:55] <vorlon> xnox: ubuntu-cdimage would be better than ubuntu-release, I think
[01:28] -queuebot:#ubuntu-release- Unapproved: accepted cups-filters [source] (mantic-proposed) [2.0.0-0ubuntu1]
[01:31] -queuebot:#ubuntu-release- Unapproved: accepted s390-tools [s390x] (mantic-proposed) [2.29.0-0ubuntu2]
[01:33] -queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (mantic-proposed) [0.142ubuntu14]
[02:12] <mclemenceau> xnox Ack.
[02:14] <mclemenceau> a bit of a blind spot in a busy time, but I'll look into this
[06:28] -queuebot:#ubuntu-release- Unapproved: accepted cups-browsed [source] (mantic-proposed) [2.0.0-0ubuntu1]
[06:31] -queuebot:#ubuntu-release- Unapproved: accepted gst-plugins-good1.0 [source] (mantic-proposed) [1.22.6-1ubuntu1]
[06:33] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (mantic-proposed) [23.10.45]
[06:33] <tjaalton> vorlon: okay, see how that goes
[06:35] -queuebot:#ubuntu-release- Unapproved: accepted cogl [source] (mantic-proposed) [1.22.8-4ubuntu1]
[06:36] <tumbleweed> ~/36
[06:37] -queuebot:#ubuntu-release- Unapproved: accepted cinder [source] (mantic-proposed) [2:23.0.0~rc1-0ubuntu1]
[06:40] <tjaalton> vorlon: I can't remember the regression though, at least it wasn't fixed by a later kinetic upload
[06:40] <tjaalton> +mesa
[06:41] <vorlon> rs2009: hi, it's ubuntu-unity's turn to get its image size limit in order.  We set an initial limit of 3.1GB last September, but that wasn't actually enough for lunar, which was > 3.2GB when it went out, and isn't enough for mantic which is now > 3.4GB.  Are you expecting to do any size reduction here for mantic, or should we bump the limit to 3.5GB?
[06:43] <vorlon> tjaalton: the regression was that mesa had a post-FF upload in kinetic that itself built ok, but once mesa was rebuilt with a newer LLVM, it in turn caused mutter to fail to build against it on armhf; was worked around by disabling a test on armhf in mutter https://launchpad.net/ubuntu/+source/mutter/43.0-1ubuntu3
[06:44] <tjaalton> vorlon: ack, thanks. the current mesa doesn't bump llvm though, at least not yet
[06:45] <tjaalton> since it'd need a newer bindgen, which I did sync but feel free to reject if that's going too far
[06:45] <vorlon> tjaalton: if I remember at the time, it wasn't a bump of the llvm build-dep, but an actual regression in the llvm that was used
[06:45] <vorlon> tjaalton: I think a bindgen sync is fine, but as noted this is a transition so its revdeps will also need updated so I want a transition plan before I accept that
[06:47] <tjaalton> looks like 22.2.0-1ubuntu1 was the ffe upload and it did move to llvm 15
[06:47] <vorlon> tjaalton: and especially since xnox found mutter build regressions due to test failures in his ppa test against a new mesa, I do want an autopkgtest in mutter that gates this new mesa from landing in the release pocket with a regressed mutter
[06:48] <vorlon> he mentions it was built with a different llvm, so MAYBE mutter won't fail to build with this one.  But it should be an automated gate, not a maybe when we upload
[06:48] <tjaalton> you mean this version? okay he didn't mention that to me :)
[06:49] <vorlon> tjaalton: it's in scrollback on this channel, in response to me raising this :)
[06:49] <tjaalton> hah, okay
[06:50] <tjaalton> oh, I missed the bindgen msgs
[06:50]  * tjaalton scrolls back all the way
[06:52] <vorlon> anyway, it's midnight here, so I'll leave it to ginggs to follow up on this today
[06:55] <vorlon> rs2009: I had a look at the ubuntu-unity manifests for lunar vs mantic, and it looks like a lot of the delta is localization packages for ~8 languages.  this isn't a difference in the ubuntu-unity seed, these packages had Task: ubuntu-unity-live in lunar but were missing from the image, due to conflicts that were silently ignored by lunar livecd-rootfs
[06:55] <vorlon> rs2009: and that got sorted out for mantic when livecd-rootfs became stricter
[07:15] -queuebot:#ubuntu-release- Unapproved: alacarte (mantic-proposed/universe) [3.44.3-1 => 3.50.0-1] (desktop-extra) (sync)
[07:15] -queuebot:#ubuntu-release- Unapproved: gnome-panel (mantic-proposed/universe) [1:3.49.1-1ubuntu1 => 1:3.50.0-1ubuntu1] (desktop-extra, ubuntu-budgie)
[07:19] -queuebot:#ubuntu-release- Unapproved: grub2-signed (mantic-proposed/main) [1.194 => 1.195] (core) (sync)
[07:19] -queuebot:#ubuntu-release- Unapproved: grub2-unsigned (mantic-proposed/main) [2.12~rc1-4ubuntu1 => 2.12~rc1-10ubuntu2] (core) (sync)
[07:19] <juliank> matching -unsigned and -signed packages for yesterday's accepted grub2
[07:26] <tjaalton> xnox: could you rebuilt mutter against mesa rc4 which is now on x-staging
[07:26] <tjaalton> just to see if the issue is already fixed
[07:33] -queuebot:#ubuntu-release- Unapproved: libwebp (mantic-proposed/main) [1.2.4-0.3 => 1.3.2-0.3] (core, i386-whitelist) (sync)
[07:35] <tjaalton> oh well, looks like it's similar to https://gitlab.gnome.org/GNOME/mutter/-/issues/2509
[07:35] -ubottu:#ubuntu-release- Issue 2509 in GNOME/mutter "Intermittent test failure: stacking/restore-size.metatest: 27: Expected size 300x200 didn't match actual size 500x400" [Opened]
[07:35] <tjaalton> since it's failing like: 36: Expected size 800x600 didn't match actual size 500x400
[07:36] <tjaalton> mutter carries a patch to disable similar checks in another test
[07:37] <LocutusOfBorg> for libwebp, we did a huge work on Debain to cleanup the packaging, move to cmake, fix the ubuntu bugs and debian bugs
[07:37] <LocutusOfBorg> it would be nice to see it landing
[07:51] <tjaalton> xnox, vorlon: latest mutter upload to debian failed on the same test on arm64 but not armhf, so I believe this falls into the same flakyness as the other test that was modified earlier
[08:11] -queuebot:#ubuntu-release- Unapproved: libxs-parse-sublike-perl (mantic-proposed/main) [0.20-1 => 0.20-1ubuntu1] (no packageset)
[08:12] -queuebot:#ubuntu-release- Unapproved: accepted libxs-parse-sublike-perl [source] (mantic-proposed) [0.20-1ubuntu1]
[08:15] <LocutusOfBorg> vorlon, fyi libzstd drops the lto fix from Ubuntu, because the lto bug was probably in some lto helper inside gcc, and the new gcc fixed it I tested in ppa, and with gcc 13 it builds fine
[08:15] <LocutusOfBorg> but I agree that this is not critical, we can sync for nanimal
[08:15] <LocutusOfBorg> (btw I checked in my ppa the buildability for all archs)
[08:25] -queuebot:#ubuntu-release- Unapproved: gcc-13-cross (mantic-proposed/main) [10ubuntu1 => 10ubuntu2] (i386-whitelist)
[08:27] -queuebot:#ubuntu-release- Unapproved: accepted gcc-13-cross [source] (mantic-proposed) [10ubuntu2]
[08:30] -queuebot:#ubuntu-release- Unapproved: gcc-13-cross-ports (mantic-proposed/universe) [13ubuntu1 => 13ubuntu2] (i386-whitelist)
[08:32] -queuebot:#ubuntu-release- Unapproved: accepted gcc-13-cross-ports [source] (mantic-proposed) [13ubuntu2]
[08:33] -queuebot:#ubuntu-release- Unapproved: gcc-12-cross (mantic-proposed/universe) [18ubuntu1 => 18ubuntu2] (i386-whitelist)
[08:35] -queuebot:#ubuntu-release- Unapproved: accepted gcc-12-cross [source] (mantic-proposed) [18ubuntu2]
[08:37] -queuebot:#ubuntu-release- Unapproved: ethtool (mantic-proposed/main) [1:6.4-1 => 1:6.5-1] (core) (sync)
[08:37] -queuebot:#ubuntu-release- Unapproved: gcc-12-cross-ports (mantic-proposed/universe) [16ubuntu1 => 16ubuntu2] (i386-whitelist)
[08:39] -queuebot:#ubuntu-release- Unapproved: accepted gcc-12-cross-ports [source] (mantic-proposed) [16ubuntu2]
[08:40] -queuebot:#ubuntu-release- Unapproved: accepted ethtool [sync] (mantic-proposed) [1:6.5-1]
[08:52] -queuebot:#ubuntu-release- Unapproved: rejected alacarte [sync] (mantic-proposed) [3.50.0-1]
[09:23] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-artwork (mantic-proposed/universe) [23.04.1 => 23.10.0] (ubuntu-mate)
[09:24] -queuebot:#ubuntu-release- Unapproved: gnome-initial-setup (mantic-proposed/main) [45.0-1ubuntu2 => 45.0-1ubuntu3] (ubuntu-desktop)
[09:25] <Wimpy> Please accept ubuntu-mate-artwork/23.10.0
[09:25] <tjaalton> jbicha: re bindgen, looks like some packages haven't been updated in sid yet, like rust-laurel, rust-leptonica-sys which are maintained outside the rust team
[09:27] <tjaalton> then again, bindgen did transition to testing already, so dunno
[09:30] <ginggs> Wimpy: .
[09:31] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-artwork [source] (mantic-proposed) [23.10.0]
[09:32] <ginggs> Wimpy: there's also a mate-desktop sync'd by someone else, are you ok for that to be accepted?
[09:35] -queuebot:#ubuntu-release- New binary: ubuntu-mate-artwork [amd64] (mantic-proposed/universe) [23.10.0] (ubuntu-mate)
[09:45] -queuebot:#ubuntu-release- Unapproved: accepted gnome-initial-setup [source] (mantic-proposed) [45.0-1ubuntu3]
[09:46] -queuebot:#ubuntu-release- Unapproved: mosquitto (mantic-proposed/universe) [2.0.17-3 => 2.0.18-1] (no packageset) (sync)
[09:47] -queuebot:#ubuntu-release- Unapproved: accepted mosquitto [sync] (mantic-proposed) [2.0.18-1]
[10:04] <Wimpy> ginggs: Let me just take a quick look at mate-desktop....
[10:06] <Wimpy> mate-desktop was sync back in July. That came from the Debian pkg-mate team (which I am on) so that is all fine.
[10:06] <ginggs> Wimpy: ack, thanks
[10:08] -queuebot:#ubuntu-release- Unapproved: accepted mate-desktop [sync] (mantic-proposed) [1.26.2-1]
[10:10] -queuebot:#ubuntu-release- Unapproved: cockpit-machines (jammy-backports/universe) [298-1~bpo22.04.1 => 299-1~bpo22.04.1] (no packageset)
[10:10] -queuebot:#ubuntu-release- Unapproved: cockpit-machines (lunar-backports/universe) [298-1~bpo23.04.1 => 299-1~bpo23.04.1] (no packageset)
[10:10] -queuebot:#ubuntu-release- Unapproved: cockpit-podman (jammy-backports/universe) [76-1~bpo22.04.1 => 77-1~bpo22.04.1] (no packageset)
[10:10] -queuebot:#ubuntu-release- Unapproved: cockpit-podman (lunar-backports/universe) [76-1~bpo23.04.1 => 77-1~bpo23.04.1] (no packageset)
[10:17] <Wimpy> ginggs: Thanks. I see some other MATE packages which might have made it to the sync queue. Would you be able to accept a few more?
[10:20] -queuebot:#ubuntu-release- Unapproved: flycheck (mantic-proposed/universe) [33~git20230824.e56e30d-1 => 33~git20230824.e56e30d-1ubuntu1] (no packageset)
[10:20] -queuebot:#ubuntu-release- Unapproved: accepted flycheck [source] (mantic-proposed) [33~git20230824.e56e30d-1ubuntu1]
[10:22] <ginggs> Wimpy: sure, which ones?
[10:25] <Wimpy> Just double checking.....
[10:29] <LocutusOfBorg> while debugging flycheck autopkgtest failure ^^ I found that gawk is installed inside autopkgtests for ubuntu, but not for debian
[10:29] <LocutusOfBorg> (not a direct dependency for the package)
[10:30] <LocutusOfBorg> oh... src:linux? :/
[10:31] <LocutusOfBorg> they must have been $reasons to pull in gawk
[10:32] <LocutusOfBorg> apw, ^^ maybe we can use awk instead of gawk?
[10:33] -queuebot:#ubuntu-release- New: accepted gnome-shell-extension-gsconnect [sync] (mantic-proposed) [55-4]
[10:33] -queuebot:#ubuntu-release- New: accepted gnome-shell-pomodoro [sync] (mantic-proposed) [0.24.0-1~exp1]
[10:33] <apw> LocutusOfBorg, woh, that was a probabally done 30 cycles ago, not sure if i can remember why we would have chosen gawk over awk.
[10:33] <apw> LocutusOfBorg, why do we care?  awk and gawk should be compatible right?  other than gnu extensions?
[10:34] <LocutusOfBorg> so better not drag in directly?
[10:34] <LocutusOfBorg> installing it inside autopkgtests testbed makes flycheck fail, and it's an additional dependency w.r.t. debian testbed
[10:34] <Wimpy> ginggs: Please accept/sync these:
[10:34] <Wimpy> caja-rename/23.10.1-1
[10:34] <Wimpy> libmatemixer/1.26.0-2+deb12u1
[10:34] <Wimpy> mate-notification-daemon/1.26.1-1
[10:34] <Wimpy> mate-system-monitor/1.26.0-4
[10:34] <Wimpy> mate-session-manager/1.26.1-2
[10:34] <Wimpy> mate-user-guide/1.26.2-1
[10:34] <Wimpy> mate-utils/1.26.1-1
[10:34] <Wimpy> mate-notification-daemon/1.26.0-1+deb12u1
[10:34] <Wimpy> mate-system-monitor/1.26.0-5
[10:35] <apw> LocutusOfBorg, what is flycheck ?
[10:35] <LocutusOfBorg> +$(foreach _line,$(shell gawk '{ OFS = "!"; $$1 = $$1; print }' $(DROOT)/dkms-versions), \
[10:36] <LocutusOfBorg> flycheck is a package not migrating due to autopkgtest failures
[10:36] <LocutusOfBorg> blocking emacs
[10:36] <apw> LocutusOfBorg, right but why would it fail with gawk
[10:36] <LocutusOfBorg> after some debugging, I found that failing test is skipped in debian due to gawk not being installed
[10:36] <apw> LocutusOfBorg, so we should fix the test ?
[10:36] <LocutusOfBorg> reverse-depends brings me to kernel
[10:36] -queuebot:#ubuntu-release- New binary: gnome-shell-extension-gsconnect [amd64] (mantic-proposed/none) [55-4] (no packageset)
[10:36] <LocutusOfBorg> apw, I already uploaded a fix to ignore the test, it's a new one
[10:36] -queuebot:#ubuntu-release- New binary: gnome-shell-pomodoro [ppc64el] (mantic-proposed/none) [0.24.0-1~exp1] (no packageset)
[10:36] -queuebot:#ubuntu-release- New binary: gnome-shell-pomodoro [amd64] (mantic-proposed/none) [0.24.0-1~exp1] (no packageset)
[10:36] -queuebot:#ubuntu-release- New binary: gnome-shell-pomodoro [s390x] (mantic-proposed/none) [0.24.0-1~exp1] (no packageset)
[10:37] <LocutusOfBorg> but in any case, why can't we sed gawk/awk in kernel?
[10:37] <LocutusOfBorg> (not for this cycle, maybe later?)
[10:37] <LocutusOfBorg> https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/mantic/commit/debian/rules.d/0-common-vars.mk?id=63047736aa9a00747e062159c581a77f1ddd420e
[10:37] -ubottu:#ubuntu-release- Commit 6304773 in ~ubuntu-kernel/ubuntu/+source/linux/+git/mantic "UBUNTU: [Packaging] support standalone dkms module builds"
[10:37] <LocutusOfBorg> stuff was done recently
[10:37] <LocutusOfBorg> maybe copy-paste
[10:37] <apw> LocutusOfBorg, right, but that isn't the reason we use gawk in the packaging
[10:38] <apw> LocutusOfBorg, we use it in the packaging because we have to have gawk installed for the kernel itself
[10:38] <LocutusOfBorg> kernel itself needs gawk? why debian kernel doesn't?
[10:39] <apw> LocutusOfBorg, a good question, but the objdump-func uses it directly, they may have fixed the scripting etc.
[10:39] -queuebot:#ubuntu-release- New binary: gnome-shell-pomodoro [armhf] (mantic-proposed/none) [0.24.0-1~exp1] (no packageset)
[10:39] <LocutusOfBorg> build time dependency or runtime one in your opinion?
[10:39] <apw> LocutusOfBorg, but ... the bug here is we have a test enabled which doesn't work in flycheck
[10:40] <apw> LocutusOfBorg, from the name i would say build-time
[10:41] <apw> LocutusOfBorg, but i want to understand why fixing flycheck isn't appropriate here.
[10:41] <LocutusOfBorg> apw, fixing flycheck is appropriate indeed, and I'm doing it
[10:42] <LocutusOfBorg> the question for kernel was "why do you runtime depend on it"?
[10:42] <LocutusOfBorg> I'm already reporting flycheck bug upstream
[10:42] <LocutusOfBorg> and ignore looks good since it looks more an upstream issue
[10:42] -queuebot:#ubuntu-release- New: accepted libgedit-gtksourceview [source] (mantic-proposed) [299.0.4-0ubuntu1]
[10:43] <apw> LocutusOfBorg, and the reason there is internal kernel tooling use gawk specifically.  i am not au-fait enough with the delta in gawk's functionality to know if the kernel is just doing that in a fit of GPL pride or it uses the extensions.
[10:44] <apw> LocutusOfBorg, though why would autopkgtest have it installed for the kernel, why would the kernel testing/build not install it as a direct dep.
[10:44] -queuebot:#ubuntu-release- Unapproved: openjdk-22 (mantic-proposed/universe) [22~15ea-2 => 22~16ea-1] (no packageset)
[10:45] -queuebot:#ubuntu-release- Unapproved: accepted openjdk-22 [source] (mantic-proposed) [22~16ea-1]
[10:45] <LocutusOfBorg> gawk	1:5.2.1-2
[10:45] <LocutusOfBorg> how can we know who is adding something on testbed-packages?
[10:45] <apw> LocutusOfBorg, a good question; on i don't think i know the answer to.
[10:45] -queuebot:#ubuntu-release- New binary: libgedit-gtksourceview [amd64] (mantic-proposed/none) [299.0.4-0ubuntu1] (no packageset)
[10:46] -queuebot:#ubuntu-release- New binary: libgedit-gtksourceview [ppc64el] (mantic-proposed/none) [299.0.4-0ubuntu1] (no packageset)
[10:46] -queuebot:#ubuntu-release- New binary: libgedit-gtksourceview [s390x] (mantic-proposed/none) [299.0.4-0ubuntu1] (no packageset)
[10:46] <LocutusOfBorg> for sure I don't have in a clean pbuilder-dist mantic chroot
[10:48] -queuebot:#ubuntu-release- New binary: libgedit-gtksourceview [arm64] (mantic-proposed/none) [299.0.4-0ubuntu1] (no packageset)
[10:50] -queuebot:#ubuntu-release- New binary: libgedit-gtksourceview [armhf] (mantic-proposed/universe) [299.0.4-0ubuntu1] (no packageset)
[10:51] -queuebot:#ubuntu-release- Unapproved: openjdk-22 (mantic-release/universe) [22~16ea-1 => 22~15ea-2] (i386-whitelist) (sync)
[10:55] -queuebot:#ubuntu-release- New binary: gnome-shell-pomodoro [arm64] (mantic-proposed/universe) [0.24.0-1~exp1] (no packageset)
[10:57] -queuebot:#ubuntu-release- Unapproved: caja-rename (mantic-proposed/universe) [23.9.1-1 => 23.10.1-1] (ubuntu-mate) (sync)
[10:58] <LocutusOfBorg> kanashiro, hello, any idea for ruby3.1 build failure on arm* I fixed the symbol issue, but still getting something about test failures
[10:59] -queuebot:#ubuntu-release- Unapproved: mate-notification-daemon (mantic-proposed/universe) [1.26.0-1 => 1.26.1-1] (ubuntu-mate, ubuntukylin) (sync)
[10:59] -queuebot:#ubuntu-release- New binary: gnome-shell-pomodoro [riscv64] (mantic-proposed/universe) [0.24.0-1~exp1] (no packageset)
[11:05] -queuebot:#ubuntu-release- Unapproved: smcroute (mantic-proposed/universe) [2.5.6-1 => 2.5.6-2] (no packageset) (sync)
[11:05] -queuebot:#ubuntu-release- Unapproved: accepted smcroute [sync] (mantic-proposed) [2.5.6-2]
[11:06] -queuebot:#ubuntu-release- Unapproved: pykeepass (mantic-proposed/universe) [4.0.3-1 => 4.0.6-1] (no packageset) (sync)
[11:07] -queuebot:#ubuntu-release- Unapproved: accepted pykeepass [sync] (mantic-proposed) [4.0.6-1]
[11:11] -queuebot:#ubuntu-release- Packageset: Removed isa-support from i386-whitelist in mantic
[11:11] -queuebot:#ubuntu-release- Packageset: Removed pcre3 from i386-whitelist in mantic
[11:11] -queuebot:#ubuntu-release- Packageset: Removed ttf-bitstream-vera from i386-whitelist in mantic
[11:11] -queuebot:#ubuntu-release- Packageset: Added openjdk-22 to i386-whitelist in mantic
[11:13] -queuebot:#ubuntu-release- New binary: libgedit-gtksourceview [riscv64] (mantic-proposed/universe) [299.0.4-0ubuntu1] (no packageset)
[11:15] -queuebot:#ubuntu-release- Unapproved: secrets (mantic-proposed/universe) [7.3-1 => 8.0-1] (no packageset) (sync)
[11:15] -queuebot:#ubuntu-release- Unapproved: accepted secrets [sync] (mantic-proposed) [8.0-1]
[11:44] -queuebot:#ubuntu-release- Unapproved: accepted caja-rename [sync] (mantic-proposed) [23.10.1-1]
[11:44] -queuebot:#ubuntu-release- Unapproved: accepted mate-notification-daemon [sync] (mantic-proposed) [1.26.1-1]
[11:47] <ginggs> Wimpy: ^ caja-rename and mate-notification daemon accepted
[11:47] <Wimpy> ty!
[11:47] <Wimpy> Shall I run syncpackage for the others?
[11:48] <jbicha> Wimpy: I believe the others are already in mantic
[11:48] <Wimpy> jbicha: Thanks for confirming
[11:49] <Wimpy> Nice to get everything aligned again.
[11:49] <Wimpy> Fixes you identified I think jbicha
[11:49] <ginggs> Wimpy, jbicha: i also had a quick look, all seem up-to-date
[11:50] <Wimpy> Thanks both
[11:56] -queuebot:#ubuntu-release- Unapproved: gcc-snapshot (mantic-proposed/universe) [1:20230917-1ubuntu1 => 1:20230926-1ubuntu1] (i386-whitelist)
[11:57] <tjaalton> ginggs, vorlon, xnox: given that mutter builds on arm64/armhf are a hit-or-miss also on the debian side because of flaky tests, they shouldn't block the new mesa
[11:57] <tjaalton> https://buildd.debian.org/status/logs.php?pkg=mutter&arch=arm64
[11:57] -queuebot:#ubuntu-release- Unapproved: accepted gcc-snapshot [source] (mantic-proposed) [1:20230926-1ubuntu1]
[11:58] <tjaalton> not all failures are due to tests failing, but many are
[11:58] <tjaalton> bindgen is another matter, we could stay on llvm 15 too
[11:59] <tjaalton> s/too/still
[13:23] <jbicha> ubuntu-release: please review gnome-shell-extension-tiling-assistant for mantic. It fixes one bug and once it's in mantic I'm going to get people to check if it also fixes bug 2034998 for mantic for them
[13:23] -ubottu:#ubuntu-release- Bug 2034998 in gnome-shell-extension-tiling-assistant (Ubuntu) "Super keybindings don't work when Tiling Assistant is enabled" [High, Confirmed] https://launchpad.net/bugs/2034998
[13:25] <LocutusOfBorg> apw, FYI I opened an upstream issue and a Debian RC bug for flycheck, just adding an additional build-dependency on gawk shows same issue
[13:25] <LocutusOfBorg> but still why it's pulled in is a question I can't solve
[13:27] -queuebot:#ubuntu-release- Unapproved: accepted libppd [source] (mantic-proposed) [2:2.0.0-0ubuntu1]
[13:28] -queuebot:#ubuntu-release- Unapproved: libreoffice (mantic-proposed/main) [4:7.6.1~rc2-0ubuntu2 => 4:7.6.2-0ubuntu1] (ubuntu-desktop)
[13:28] <ginggs> tjaalton: to be clear, the rust-bindgen sync is not needed for mesa 23.2.0~rc4-1ubuntu1
[13:28] <ginggs> ?
[13:29] <jbicha> tjaalton: I'm uploading a NMU to Unstable for rust-laurel now; rust-leptonica-sys doesn't appear to need any changes
[13:31] <tjaalton> ginggs: correct, it's for migrating mesa to llvm 16, but it's not critical at this point
[13:32] <tjaalton> jbicha: okay cool
[13:32] <ricotz> ginggs, hello :), please accept libreoffice/mantic, its testbuild succeeded and autopkgtests passed
[13:40] <ginggs> tjaalton: mutter still fails on arm64 and armhf here https://launchpad.net/~xnox/+archive/ubuntu/mesa/+packages?field.name_filter=mutter&field.status_filter=published&field.series_filter=
[13:40] <ginggs> (last retried about 1 hour ago)
[13:41] <tjaalton> still flaky tests, as it's a different one this time
[13:42] <tjaalton> there is a report upstream at https://gitlab.gnome.org/GNOME/mutter/-/issues/2509
[13:42] -ubottu:#ubuntu-release- Issue 2509 in GNOME/mutter "Intermittent test failure: stacking/restore-size.metatest: 27: Expected size 300x200 didn't match actual size 500x400" [Opened]
[13:42] <tjaalton> but not much love there
[13:44] <tjaalton> pinged smcv about it
[13:45] <ginggs> it would be nice if those tests would be skipped in the mutter build, so if it ever needs to be rebuilt it can be done without someone hitting retry all the time
[13:45] <tjaalton> jbicha: ^ ?
[13:46] <tjaalton> but yes I agree, there's already a patch to skip some checks
[13:47] -queuebot:#ubuntu-release- Unapproved: libreoffice (lunar-proposed/main) [4:7.5.6-0ubuntu0.23.04.1 => 4:7.5.7-0ubuntu0.23.04.1] (ubuntu-desktop)
[13:53] -queuebot:#ubuntu-release- Unapproved: accepted libreoffice [source] (mantic-proposed) [4:7.6.2-0ubuntu1]
[14:04] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell-extension-tiling-assistant [source] (mantic-proposed) [44-1ubuntu1]
[14:17] -queuebot:#ubuntu-release- Unapproved: accepted cairo [sync] (mantic-proposed) [1.18.0-1]
[14:27] -queuebot:#ubuntu-release- Unapproved: pycairo (mantic-proposed/main) [1.24.0-1.1 => 1.24.0-3] (desktop-core, i386-whitelist) (sync)
[14:34] -queuebot:#ubuntu-release- Unapproved: accepted pycairo [sync] (mantic-proposed) [1.24.0-3]
[14:47] -queuebot:#ubuntu-release- Unapproved: pkgbinarymangler (mantic-proposed/main) [153 => 154] (i386-whitelist, ubuntu-desktop)
[15:04] <vorlon> tjaalton: rust revdeps that are in unstable-only and don't have any apps depending on them can just be removed for release
[15:08] -queuebot:#ubuntu-release- Unapproved: accepted pkgbinarymangler [source] (mantic-proposed) [154]
[15:09] -queuebot:#ubuntu-release- Unapproved: rejected openjdk-22 [sync] (mantic-release) [22~15ea-2]
[15:18] -queuebot:#ubuntu-release- Unapproved: dill (mantic-proposed/universe) [0.3.6-1 => 0.3.7-1] (i386-whitelist) (sync)
[15:19] -queuebot:#ubuntu-release- Unapproved: accepted dill [sync] (mantic-proposed) [0.3.7-1]
[15:23] <vorlon> dbungert, fossfreedom_: the livecd-rootfs update missed today's ubuntu-budgie daily, so I'm doing a respin to pick up the fix for LP: #2036966
[15:23] -ubottu:#ubuntu-release- Launchpad bug 2036966 in livecd-rootfs (Ubuntu) "Budgie Installer fails with internet enabled / additional media support selected" [Undecided, Fix Released] https://launchpad.net/bugs/2036966
[15:24] <vorlon> oh.  no, it didn't miss, the budgie daily is happening right now - so no respin :)
[15:26] <dbungert> nice
[15:26] <vorlon> tjaalton, ginggs, xnox: I'm not thrilled about flaky tests on mutter, either; please talk to the desktop team (jbicha, seb128?) and make sure there's an agreed plan for if mutter needs updating in mantic after the mesa update
[15:27] <vorlon> tjaalton: also wrt rust, if newer bindgen is the right answer, there's always the option of parallel packaging as a bindgen-0.66 so you don't have to deal with the transition.  Please advise which way you want to go with this, I will support whichever option, just so long as there's a plan to get things into a coherent state by release
[15:28] <vorlon> tjaalton: (and thus, let me know if I should accept / reject the current mesa and bindgen uploads)
[15:36] <mitchdz> Hi! I'm looking at amazon-ec2-net-utils that's currently in the universe archive for Lunar/Mantic. I'd like to also have this package available in Jammy/Focal. Could I get some guidance on the process for this?
[15:41] -queuebot:#ubuntu-release- Unapproved: cups (mantic-proposed/main) [2.4.6-0ubuntu2 => 2.4.6-0ubuntu3] (core, i386-whitelist)
[15:43] -queuebot:#ubuntu-release- Unapproved: ceph (mantic-proposed/main) [18.2.0-0ubuntu1 => 18.2.0-0ubuntu2] (ubuntu-server)
[15:43] -queuebot:#ubuntu-release- Unapproved: cups-browsed (mantic-proposed/main) [2.0.0-0ubuntu1 => 2.0.0-0ubuntu2] (no packageset)
[16:14] <vorlon> mitchdz: https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases "e.g. entirely new packages are usually fine".  But they fall a bit outside the normal SRU process, because they wind up in a different queue for NEW packages that only the intersection of ubuntu-archive + ubuntu-sru have access and authority to process; so after you get an upload you should reach out directly to the team (using
[16:14] <vorlon> this channel is fine)
[16:23] <vorlon> ItzSwirlz: hi, can we talk about ubuntucinnamon image sizes and what our target size limit should be for mantic
[16:26] -queuebot:#ubuntu-release- Unapproved: sbsigntool (mantic-proposed/main) [0.9.4-3.1ubuntu2 => 0.9.4-3.1ubuntu3] (core)
[16:28] -queuebot:#ubuntu-release- Unapproved: accepted sbsigntool [source] (mantic-proposed) [0.9.4-3.1ubuntu3]
[16:30] <mitchdz> vorlon: Thanks! Since I plan to copy 2.3.0-2 from Lunar, can I use that same version for both Jammy/Focal or will there be an issue in the archive uploading the same version? e.g. Should I use 2.3.0-2ubuntu1.22.04.1
[16:30] -queuebot:#ubuntu-release- Unapproved: accepted ceph [source] (mantic-proposed) [18.2.0-0ubuntu2]
[16:33] -queuebot:#ubuntu-release- Unapproved: accepted cups-browsed [source] (mantic-proposed) [2.0.0-0ubuntu2]
[16:33] -queuebot:#ubuntu-release- Unapproved: accepted cups [source] (mantic-proposed) [2.4.6-0ubuntu3]
[16:37] <mitchdz> never mind about the version comment, I figured out what it should be
[17:14] <tjaalton> vorlon: newer bindgen is only needed if doko wants mesa to be built with llvm ;)
[17:14] <tjaalton> llvm 16 that is
[17:14] <tjaalton> current mesa is fine, bindgen we can still discuss
[17:14] <vorlon> tjaalton: I'll reject bindgen for now
[17:15] <tjaalton> okay, that's fine
[17:16] -queuebot:#ubuntu-release- Unapproved: rejected rust-bindgen [sync] (mantic-proposed) [0.66.1-3]
[17:18] -queuebot:#ubuntu-release- Unapproved: distro-info (xenial-backports/main) [0.18~ubuntu16.04.1 => 0.18ubuntu0.18.04.1~bpo18.04.1] (core)
[17:19] -queuebot:#ubuntu-release- New binary: klepto [amd64] (mantic-proposed/universe) [0.2.4-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- Unapproved: ubuntu-docs (mantic-proposed/main) [23.10.1 => 23.10.2] (ubuntu-desktop)
[17:29] -queuebot:#ubuntu-release- Unapproved: mozjs115 (mantic-proposed/universe) [115.2.0-0ubuntu1 => 115.3.0-0ubuntu1] (no packageset)
[17:29] <vorlon> tjaalton: and I'm accepting mesa because I know we need to get this moving, but am still concerned about mutter flakiness and the possibility of any increase in that flakiness
[17:29] -queuebot:#ubuntu-release- Unapproved: accepted mozjs115 [source] (mantic-proposed) [115.3.0-0ubuntu1]
[17:31] -queuebot:#ubuntu-release- Unapproved: gjs (mantic-proposed/main) [1.76.2-4 => 1.78.0-0ubuntu1] (desktop-core, desktop-extra, i386-whitelist, mozilla)
[17:33] <jbicha> vorlon: I replied to bug 2034276 & uploaded gjs here ^
[17:33] -ubottu:#ubuntu-release- Bug 2034276 in gjs (Ubuntu) "[FFE] Update gjs to 1.77.90 and switch mozjs102 to mozjs115" [Undecided, New] https://launchpad.net/bugs/2034276
[17:35] -queuebot:#ubuntu-release- Unapproved: accepted mesa [source] (mantic-proposed) [23.2.0~rc4-1ubuntu1]
[17:37] -queuebot:#ubuntu-release- Unapproved: geoclue-2.0 (mantic-proposed/main) [2.7.0-3ubuntu2 => 2.7.0-3ubuntu3] (desktop-core)
[17:39] <tjaalton> vorlon: thanks. looking at the past build logs on debian side it looks like this isn't something new
[17:41] <fossfreedom_> hmm ... something strange on the UB ISO - we now have the mate-desktop on it.  Has there been some mate syncs lately?
[17:44] <bdmurray> fossfreedom_: I seem to recall seeing that in the scrollback
[17:48] <fossfreedom_> why on earth has mate-system-monitor now got a dependency on mate-session-monitor?!  I never has had it in the past.
[17:49] <jbicha> looks like I found it the same time you did: https://tracker.debian.org/news/1465970/accepted-mate-system-monitor-1260-4-source-into-unstable/
[17:49] <fossfreedom_> s/mate-session-monitor/mate-session-manager/
[17:50] <jbicha> fossfreedom_: it was a response to https://sources.debian.org/src/mate-system-monitor/1.26.0-5/src/sysinfo.cpp/?hl=222#L222
[17:51] <jbicha> but I'll prepare an upload to drop that dependency for mantic
[17:51] <fossfreedom_> much appreciated!
[17:57] -queuebot:#ubuntu-release- Unapproved: mate-system-monitor (mantic-proposed/universe) [1.26.0-5 => 1.26.0-5ubuntu1] (ubuntu-mate, ubuntukylin)
[18:18] <ricotz> bdmurray, hello :), would you have time to take a look at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2037274
[18:18] -ubottu:#ubuntu-release- Launchpad bug 2037274 in libreoffice (Ubuntu Lunar) "[SRU] libreoffice 7.5.7 for lunar" [Medium, In Progress]
[19:05] -queuebot:#ubuntu-release- Unapproved: python-openstackclient (mantic-proposed/main) [6.2.0-0ubuntu1 => 6.3.0-0ubuntu1] (openstack)
[20:07] -queuebot:#ubuntu-release- Unapproved: thunderbird (mantic-proposed/main) [1:115.2.3+build2-0ubuntu1 => 1:115.3.0+build2-0ubuntu1] (mozilla, ubuntu-desktop)
[20:10] <jbicha> ubuntu-release: could mate-system-monitor be reviewed for mantic since it fixes a disruptive bug for desktop flavors?
[20:10] <vorlon> yes
[20:12] <vorlon> jbicha: should there be a Breaks: << replacing the Depends: >= ?
[20:13] -queuebot:#ubuntu-release- Unapproved: accepted mate-system-monitor [source] (mantic-proposed) [1.26.0-5ubuntu1]
[20:14] <jbicha> I'll ask at Debian bug 1052997
[20:14] -ubottu:#ubuntu-release- Debian bug 1052997 in src:mate-system-monitor "mate-system-monitor: unwanted dependency on mate-session-manager" [Normal, Open] https://bugs.debian.org/1052997
[20:14] -queuebot:#ubuntu-release- Unapproved: accepted gjs [source] (mantic-proposed) [1.78.0-0ubuntu1]
[20:16] <vorlon> juliank, mkukri: is it time to bump cd-boot-images-foo for this grub, or are you expecting Yet Another Upload before release?
[20:17] <juliank> vorlon: ah shoot I forgot
[20:18] <juliank> But yes I think there will be another one
[20:18] <juliank> It's still good to bump it now for more testing I think
[20:19] -queuebot:#ubuntu-release- Unapproved: accepted grub2-unsigned [sync] (mantic-proposed) [2.12~rc1-10ubuntu2]
[20:19] <vorlon> mm yes very good point
[20:20] -queuebot:#ubuntu-release- Unapproved: accepted grub2-signed [sync] (mantic-proposed) [1.195]
[20:50] -queuebot:#ubuntu-release- Unapproved: ubuntustudio-default-settings (mantic-proposed/universe) [23.10.13 => 23.10.14] (ubuntustudio)
[20:50] <Eickmeyer> ^ solves critical upgrade bug 2037471
[20:50] -ubottu:#ubuntu-release- Bug 2037471 in ubuntustudio-default-settings (Ubuntu) "ubuntustudio-lowlatency-settings fails to upgrade 23.04 -> 23.10" [Critical, In Progress] https://launchpad.net/bugs/2037471
[21:36] -queuebot:#ubuntu-release- Unapproved: censys (mantic-proposed/universe) [2.2.5-1 => 2.2.6-1] (no packageset) (sync)
[21:36] -queuebot:#ubuntu-release- Unapproved: python-esmre (mantic-proposed/universe) [1.0-1build2 => 1.0.1-1] (no packageset) (sync)
[21:36] -queuebot:#ubuntu-release- Unapproved: accepted censys [sync] (mantic-proposed) [2.2.6-1]
[21:36] -queuebot:#ubuntu-release- Unapproved: accepted python-esmre [sync] (mantic-proposed) [1.0.1-1]
[21:45] -queuebot:#ubuntu-release- Unapproved: workrave (mantic-proposed/universe) [1.10.51.1-2ubuntu1 => 1.10.52-1ubuntu1] (no packageset)
[21:46] -queuebot:#ubuntu-release- Unapproved: accepted workrave [source] (mantic-proposed) [1.10.52-1ubuntu1]
[21:54] -queuebot:#ubuntu-release- New binary: workrave [amd64] (mantic-proposed/universe) [1.10.52-1ubuntu1] (no packageset)
[21:54] <vpa1977> Hi, would it be possible to take a look at https://bugs.launchpad.net/ubuntu/+source/libyuv/+bug/2015413 - sync for libyuv at some point? Thank you!!!
[21:54] -ubottu:#ubuntu-release- Launchpad bug 2015413 in libyuv (Ubuntu) "[FFe] please sync libyuv from Debian  0.0~git20230616.a366ad7-2" [Undecided, New]
[22:05] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (mantic-proposed/main) [23.10.45 => 23.10.47] (desktop-core, i386-whitelist)
[22:10] <bdmurray> coreycb: I don't see the version of horizon listed in https://bugs.launchpad.net/cloud-archive/+bug/2030526/comments/11
[22:10] -ubottu:#ubuntu-release- Launchpad bug 2030526 in octavia (Ubuntu Jammy) "[SRU] yoga stable releases" [High, Fix Committed]
[22:14] -queuebot:#ubuntu-release- Unapproved: accepted geoclue-2.0 [source] (mantic-proposed) [2.7.0-3ubuntu3]
[22:18] <xnox> vorlon: i didn't know if we have precedent with capitalisation or not
[22:19] <xnox> given the model name in dmidecode and on websites is Lenovo X13s Gen 1
[22:21] <xnox> i think i have my answer with OMAP 4
[22:21] <xnox> given that it an actual acronym
[22:22] <vorlon> xnox: all other subarchs use lowercase, despite most of them clearly being brand names etc
[22:23] -queuebot:#ubuntu-release- Unapproved: accepted python-openstackclient [source] (mantic-proposed) [6.3.0-0ubuntu1]
[22:26] -queuebot:#ubuntu-release- Unapproved: accepted thunderbird [source] (mantic-proposed) [1:115.3.0+build2-0ubuntu1]
[22:30] <vorlon> Eickmeyer: LP: #2037471 this is not the first grub ordering issue that's come up during the development cycle, and none of the other issues involved adding versioned depends on grub-common. I'm pinging juliank for a refresher on what he needed to do here, to make sure we're aligned
[22:30] -ubottu:#ubuntu-release- Launchpad bug 2037471 in ubuntustudio-default-settings (Ubuntu) "ubuntustudio-lowlatency-settings fails to upgrade 23.04 -> 23.10" [Critical, Fix Committed] https://launchpad.net/bugs/2037471
[22:42] <Eickmeyer> vorlon: GRUB_FLAVOUR_ORDER is implemented in this, and simply needs to be implemented in grub. I've been communicating with juliank on what needed to be done on this and we've been coordinating.
[22:43] <Eickmeyer> vorlon:  The problem here is, when upgrading, the old /etc/grub.d/10_linux was being run despite grub being upgraded, whereas grub-common provides /etc/grub.d/10_linux.
[22:44] <Eickmeyer> Basically, I made d/control in ubuntustudio-lowlatency-settings prevent the race condition caused by apt running the upgrade of u-ll-s before grub-common.
[22:45] <Eickmeyer> Right now, upgrades for Ubuntu Studio 23.04 -> 23.10 beta are failing due to this issue.
[22:46] <vorlon> Eickmeyer: why is it a versioned dependency instead of an unversioned dependency
[22:48] <Eickmeyer> vorlon: Because the versions of 10_linux prior to that version are incompatible with grub prior to that, and we don't want to run update-grub unless everything matches.
[22:48] <Eickmeyer> Let me rephrase.
[22:50] <Eickmeyer> The 10_linux in grub-common prior to 2.12~ is incompatible with grub 2.12~. ubuntustudio-lowlatency-settings *might* (and in my testing, did) install between grub and grub-common being upgraded.
[22:50] <Eickmeyer> This change prevents that.
[22:50] <Eickmeyer> Hence, >=
[22:51] <vorlon> "grub and grub-common" < these are not the correct package names
[22:51] <Eickmeyer> grub2 and grub2-common then.
[22:51] <Eickmeyer> It's correct in the package.
[22:51] <vorlon> no, you don't have a package named grub2 installed
[22:51] <vorlon> update-grub is provided by grub2-common
[22:52] <vorlon>  /etc/grub.d/10_linux is provided by grub-common
[22:52] <vorlon> and grub2-common has a strict versioned dependency on grub-common
[22:52] <vorlon> so from what I see the issue you're having is because you have a maintainer script invoking code from a package that it doesn't declare a dependency on at all
[22:53] -queuebot:#ubuntu-release- Unapproved: accepted rtl8812au [source] (lunar-proposed) [4.3.8.12175.20140902+dfsg-0ubuntu20~23.04]
[22:53] <Eickmeyer> No. I'm trying to explain this better.
[22:53] <vorlon> because if there was an unversioned Depends: grub2-common, apt would not configure ubuntustudio-lowlatency-settings while grub2-common was not configured
[22:53] <Eickmeyer> It's not because of update-grub.
[22:54] <Eickmeyer> It has more to do with grub itself. update-grub failed at 10_linux during the maintscript.
[22:54] <Eickmeyer> But, when it was ran later, there was no failure.
[22:55] <Eickmeyer> This tells me that grub-common needed to be upgraded/configured first.
[22:56] <vorlon> yes, which it is if you have an unversioned dependency on grub2-common.
[22:56] <Eickmeyer> If It's upgrading and were unversioned, would it not still see that grub-common were installed and do it anyway?
[22:56] <Eickmeyer> s/grub-common/grub2-common
[22:57] <Eickmeyer> Because, I assure you, grub2-common was installed in the machine to be upgraded.
[22:57] <vorlon> CONFIGURED
[22:57] <Eickmeyer> er, configured.
[22:57] <vorlon> no, it wasn't
[22:58] <Eickmeyer> And now I'm confused.
[22:58] <vorlon> also I just noticed you're adding this as a pre-depends
[22:58] <vorlon> no
[22:58] <vorlon> do you have an upgrade log from the failure?
[22:58] <Eickmeyer> I'm not trying to be hostile here, I'm just *very* confused.
[22:59] <Eickmeyer> I did, let me see if I can fetch it.
[23:05] <Eickmeyer> https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default-settings/+bug/2037471/comments/2
[23:05] -ubottu:#ubuntu-release- Launchpad bug 2037471 in ubuntustudio-default-settings (Ubuntu) "ubuntustudio-lowlatency-settings fails to upgrade 23.04 -> 23.10" [Critical, Fix Committed]
[23:05] <Eickmeyer> vorlon: ^
[23:05] <vorlon> thanks, looking
[23:06] <Eickmeyer> Had the same symptoms before removing 09_lowlatency from lowlatency-settings after grub 2.11 dropped.
[23:10] -queuebot:#ubuntu-release- Unapproved: accepted gnome-applets [sync] (mantic-proposed) [3.50.0-1]
[23:17] <Eickmeyer> vorlon: I do see what you're saying, can demote from pre-deps to depends.
[23:18] <Eickmeyer> But still confused as to why it'd need to be unversioned.
[23:18] <vorlon> working on posting a full analysis to the bug
[23:18] <Eickmeyer> Ok.
[23:19] <Eickmeyer> As long as I don't have to go back to the drawing board on the whole package.
[23:21] <bdmurray> xnox: Who are you expecting an answer from? https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2013236/comments/37
[23:21] -ubottu:#ubuntu-release- Launchpad bug 2013236 in ubuntu-drivers-common (Ubuntu Mantic) "b43 driver conflicts with bcmwl driver for some Broadcom devices" [Undecided, Incomplete]
[23:22] <xnox> bdmurray: the gui stuff was to alberto
[23:22] <xnox> bdmurray: the "blacklist not working, whilst clearly packaged by default, and requiring manual blacklist" was to you
[23:23] <xnox> also the latest comments are confusing
[23:23] <xnox> given that said drivers haven't had any changes in years
[23:27] <vorlon> Eickmeyer: posted
[23:27] <Eickmeyer> Looking..
[23:29] <bdmurray> Isn't this upgrade issue the same as bug 2031420?
[23:29] -ubottu:#ubuntu-release- Bug 2031420 in memtest86+ (Ubuntu) "package memtest86+ 6.20-2 failed to install/upgrade: installed memtest86+ package post-installation script subprocess returned error exit status 127" [High, Fix Released] https://launchpad.net/bugs/2031420
[23:29] <vorlon> Eickmeyer: added a further comment with what I believe would be a correct implementation
[23:29] <vorlon> bdmurray: THERE we go, I knew there had been another such issue but couldn't remember where it was
[23:29] <Eickmeyer> vorlon: I was just about to type here: update-grub || true. :D
[23:30] <vorlon> yes, it's the same issue; except more complicated because ubuntustudio-lowlatency-settings is calling update-grub in a few more places than is usual
[23:30] <vorlon> memtest86+ already only calls update-grub from the postrm if $1 in (remove,purge)
[23:31] <vorlon> oh actually, you don't need to call it for the failed-upgrade case either
[23:33] <vorlon> Eickmeyer: so I'm bypassing the check for update-grub2 as part of this, both because a failure to execute due to a missing command can be ignored with || true the same as any other failure; and because it's bad form to do `which update-grub2` and then call a different command than update-grub2
[23:34] -queuebot:#ubuntu-release- Unapproved: rejected ubuntustudio-default-settings [source] (mantic-proposed) [23.10.14]
[23:35] <Eickmeyer> vorlon: Oh, yeah, I never use "which" anymore, only "command -v" if I must, and check executable path if necessary.
[23:42] <vorlon> Eickmeyer: also, whereas ubuntustudio-default-settings uses .maintscript for managing removal of obsolete conffiles, ubuntustudio-lowlatency-settings is doing by-hand removals of /etc/grub.d/09_lowlatency which don't have the expected conffile handling in many cases
[23:42] <vorlon> Eickmeyer: and you're calling chmod +x /etc/grub.d/10_linux rather a lot...
[23:43] <Eickmeyer> vorlon: Sadly, that's because a previous package maintainer thought it was a good idea to do chmod -x /etc/grub.d/10_linux, so I wanted to make *darn sure* it's executable again.
[23:44] -queuebot:#ubuntu-release- Unapproved: easyssh (mantic-proposed/universe) [1.7.9-3 => 1.7.9-4] (no packageset) (sync)
[23:45] -queuebot:#ubuntu-release- Unapproved: accepted easyssh [sync] (mantic-proposed) [1.7.9-4]
[23:45] <vorlon> rs2009: I'm going ahead and bumping the image limit for ubuntu-unity to 3.5GB. If you want a different limit, we can set it accordingly.  (But if you want a lower limit, you'll have to make some changes to your seeds to achieve it...)
[23:47] <Eickmeyer> vorlon: five years later, and there's a lot of non-policy mess and bad habits, even from myself, I'm cleaning up.
[23:47] <Eickmeyer> Right now, I'm just trying to get mantic across the finish line.
[23:50] -queuebot:#ubuntu-release- Unapproved: accepted gnome-panel [source] (mantic-proposed) [1:3.50.0-1ubuntu1]
[23:57] <vorlon> tumbleweed: uh why does seeded-in-ubuntu tell me gnome-shell-extension-desktop-icons-ng is in ubuntu "daily-legacy, daily-live, daily-preinstalled" when the actual seed its in (as shown by the Task: field) is ubuntu desktop-minimal
[23:58] <vorlon> jbicha: if gnome-shell-extension-desktop-icons-ng already had GNOME 45 support cherry-picked, what's the advantage of taking this new sync?