[00:00] <vorlon> liushuyu: libopencv-core406 should be provided by libopencv-core406t64 on amd64 and thus not blocking?
[00:04] <vorlon> lubuntu has some pre-t64 real packages being pulled in via germinate that conflict with the new ones, going to remove these now, may increase armhf uninstallability count (libsmbclient libcdio19 libmpg123-0)
[00:04] <vorlon> +libsphinxbase3
[00:05] <vorlon> liushuyu: from the latest livefs build log, ubuntukylin blockers are as follows:
[00:05] <vorlon>  ukui-control-center : Depends: libkysdk-applications (>= 2.2.1.1) but it is not installable
[00:05] <vorlon>  ukui-desktop-environment-core : Depends: peony but it is not installable
[00:05] <vorlon>  ukui-media : Depends: ukui-media-common (= 3.0.4-1) but 3.1.1.1-2build4 is to be installed
[00:06] <liushuyu> vorlon: I have tried to clear peony, the tests are passed now, waiting for the excuses page to update
[00:06] <vorlon> great
[00:07] <liushuyu> libkysdk-applications is waiting on libstd, which I have retried the tests, now all passed as well
[00:07] <liushuyu> * libstb
[00:08] <liushuyu> "Migration status for ukui-media (3.1.1.1-2build4 to 3.1.1.1-2build5): Will attempt migration (Any information below is purely informational)"
[00:08] <liushuyu> So I believe Ubuntu Kylin is just waiting for the next migration window
[00:09] <vorlon> trying: ukui-media
[00:09] <vorlon> skipped: ukui-media (70, 47, 559)
[00:09] <vorlon>     got: 1440+0: a-469:a-37:a-841:i-6:p-31:r-29:s-27
[00:09] <vorlon>     * amd64: ukui-media
[00:09] <vorlon> from update_output
[00:09] <vorlon> so ukui-media didn't migrate
[00:10] <liushuyu> vorlon: I just run a simulated install on my local device, ukui-media is waiting on libkysdk-applications according to apt output
[00:11] <vorlon> ok
[00:11] <liushuyu> libkysdk-applications is waiting on libstb (just cleared all autopkgtest minutes ago)
[00:11] <liushuyu> maybe there is a delay on pulling the autopkgtest results?
[00:12] <vorlon> so, how are neither libstb nor libkysdk-applications showing up in the list of seeded packages that we previously retriggered tests for
[00:12] <vorlon> are they only newly seeded?
[00:12] <vorlon> liushuyu: update_excuses.html only updates as part of a full britney run
[00:13] <liushuyu> I am unsure. Some of those packages were uploaded at least 2 days ago according to LP
[00:13] <vorlon> doesn't matter if they're new dependencies of the seeded packages
[00:13] <liushuyu> vorlon: Okay, then I guess Ubuntu Kylin is in the clear as far as I can tell
[00:14] <liushuyu> simulated install also showed some of the packages are waiting on gstreamer1.0-plugins-good
[00:14] <vorlon> last proposed-migration run finished 00:10
[00:14] <vorlon> gst-plugins-good1.0 has already migrated
[00:15] <liushuyu> Just migrated I see
[00:16] <liushuyu> Okay, some of the tests missed the update window
[00:16] <vorlon> privoxy continuing to look pretty darn broken
[00:16] <vorlon> liushuyu: britney interval is currently back down to < 1h
[00:16] <liushuyu> vorlon: I investigated privoxy, it seems like newly added Apparmor rules broke the autopkgtest
[00:16] <vorlon> 21:30 22:02 22:58 23:40
[00:17] <liushuyu> AppArmor rules are preventing provoxy from reading the configuration files and writing to the lock files during the test
[00:17] <vorlon> ok rerunning a baseline retest of privoxy
[00:18] <vorlon> that plus a retry of dislocker (which I just scheduled) should unblock mbedtls<-librist<-ffmpeg
[00:19] <liushuyu> Oh, so Britney is running continuously
[00:19] <liushuyu> I thought it's running on a schedule
[00:21] <vorlon> it tries to run every 2 minutes
[00:22] <liushuyu> Okay, it seems like somewhere in the ukui-biometric-auth chain, it pulls in gdal and gdal is stuck due to numpy
[00:22] <vorlon> it's worth retrying numpy tests again with --all-proposed now that pytest is removed
[00:23] <liushuyu> vorlon: doing it now
[00:23] <vorlon> image build failures are now largely due to packages in noble-updates getting pulled in by germinate but conflicting with the t64 versios
[00:31] <liushuyu> Is there a reason why the machine-readable version of update_excuses is a yaml file instead of a json file?
[00:31] <vorlon> rebuilding multipath-tools for libaio1t64 which for some reason doesn't use Provides:
[00:31] <vorlon> liushuyu: because json is machine-readable and not human-readable
[00:32] <liushuyu> (yaml is also not so human-readable, but okay)
[00:38] <vorlon> ubuntu got as far as the kernel, yay progress
[00:41] <liushuyu> vorlon: as far as the kernel > yay, the humanity will thank us for this leap of a progress /s
[00:47] <vorlon> now I probably have to roll back livecd-rootfs to point to hwe-22.04 because the only hwe-24.04 metapackage available points to the removed kernels
[00:51] <vorlon> noble-updates cleaned again of superseded packages
[00:51] <vorlon> down to 739 sources there now
[00:52] <vorlon> that should clean up the remaining pre-kernel issues for ~half the flavors
[00:53] <vorlon> ah linux/linux-meta/linux-signed are ready to go in -proposed except for autopkgtests
[00:54] <vorlon> so let's see if we can't get some slightly less red test results
[00:54] <vorlon> oh liushuyu beat me to it
[00:55] <vorlon> ok, letting that cook and afk again for an hour or so
[00:56] <vorlon> liushuyu: and yes libstb + libkysdk-applications have gone through
[00:56] <vorlon> trying: libstb tinygltf ogre-1.12 libkysdk-applications ukui-media ubuntukylin-meta peony ukui-control-center ukui-power-manager ukui-panel
[00:56] <vorlon> accepted: libstb tinygltf ogre-1.12 libkysdk-applications ukui-media ubuntukylin-meta peony ukui-control-center ukui-power-manager ukui-panel
[00:56] <vorlon>    ori: 2101+0: a-619:a-65:a-1185:i-78:p-64:r-46:s-44
[00:56] <vorlon>    pre: 1479+0: a-470:a-38:a-876:i-6:p-32:r-29:s-28
[00:56] <vorlon>    now: 1468+0: a-459:a-38:a-876:i-6:p-32:r-29:s-28
[00:56] <vorlon> happy to see uninstallable counts coming down, that means much less manual cleanup required
[00:58] <vorlon> kubuntu blocked by kio-extras, currently building on arm64
[00:58] <vorlon> and ubuntustudios needs imath
[01:48] <vorlon> so someone just retried kio-extras 4 minutes ago, but it was building an hour ago which means it's failing in a loop and we need to stop retrying it so we can look at the logs RikMills
[01:56] <dbungert> that would be a nice log, kio-extras is building for me locally
[02:36] <vorlon> dbungert: arm64?
[02:36] <vorlon> (that's the only build missing)
[02:37] <vorlon> linux-meta, all tests passed except lxc and 2 still running; hinting now
[02:38] <vorlon> xubuntu minimal built \o/
[02:38] <dbungert> vorlon: no, I missed that first, building locally now
[02:39] <dbungert> which is to say builds fine on amd64, like LP, and trying a local arm64
[02:39] <vorlon> rebuilding bijiben for t64 (needed for edubuntu)
[02:39] <vorlon> ubuntucinnamon needs a bit of digging, trying to pull pulseaudio again and hitting conflicts
[02:40] <dbungert> oh, kio-extras built on arm64 this time
[02:41] <vorlon> oh, woot
[02:42] <dbungert> your cinnamon attempt, what are you running? `apt install ubuntucinnamon-desktop` seems fine
[02:42] <vorlon> dbungert: I'm looking at the livefs build output, so you can thank germinate https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntucinnamon/+build/601697
[02:43] <vorlon> skiptesting imath (i386 only failure)
[02:44] <vorlon> still blocked by numpy
[02:45] <vorlon> rebuilding nfs-utils for libevent-core-2.1-7t64 ; spotted because of bitshuffle/amd64 autopkgtest complaining about libevent-core but that's probably just because NBS removals needed
[02:46] <vorlon> 1148s E       ModuleNotFoundError: No module named '_sysconfigdata__i386-linux-gnu'
[02:46] <vorlon> looks like a whole lot of Not My Problem
[02:47] <vorlon> (arch: all python module, i386 doesn't matter)
[02:47] <vorlon> 2205s ModuleNotFoundError: No module named 'numpy.distutils'
[02:47] <vorlon> lol go soak
[02:50] <vorlon> and `reverse-depends` times out :(
[02:52] <vorlon> removing metpy, real regression w/ numpy 1.26
[02:53] <vorlon> 2005s  python3-pyobjcryst : Depends: libboost-python1.83.0-py311
[02:53] <vorlon> hmm
[02:54] <vorlon> oh dear, amd64-only package, removed from noble, ftbfs in -proposed, binary in -updates
[02:54] <vorlon> and ftbfs because ModuleNotFoundError: No module named 'numpy.distutils'
[02:55] <vorlon> removed
[02:58] <vorlon> silx/ppc64el showing mesa errors and dying with SIGTERM?  Well, not going to block...
[02:58] <vorlon> hinting numpy
[03:00] <vorlon> failing to see the problem in https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntu-server-live/+build/601673
[03:02] <vorlon> tsimonq2: https://cdimage.ubuntu.com/lubuntu/daily-live/current/
[03:03] <vorlon> lubuntu built. ubuntukylin built. ubuntu-mate built. ubuntu-unity built. xubuntu built (minimal and desktop).
[03:08] <vorlon> oops forgot to dump perl tests from the i386 queue, doing now
[03:09] <vorlon> autopkgtest queues are empty, time to requeue the world (everything not on images)
[03:11] <vorlon> the above succesfully-built images are also built with the old kernel, so we'll want to replace them once linux+linux-meta have migrated
[03:11] <vorlon> only 2382 tests to requeue, that's surprising
[03:17] -queuebot:#ubuntu-release- Unapproved: accepted cups [source] (noble-proposed) [2.4.7-1.2ubuntu5]
[03:19] <vorlon> apw: linux-meta-oem-6.8 is in main but not seeded
[03:21] <vorlon> apw: (and has no team subscriber)
[03:55] <liushuyu> vorlon: are you still looking at Lubuntu?
[03:58] <arraybolt3> vorlon: is ubuntucinnamon dying because of the ftbfs for mozjs?
[03:59] <arraybolt3> I did some work on that yesterday, and am planning on fixing it tomorrow, though I can fix it tonight if that would be better.
[03:59] <liushuyu> ... dying?
[04:00] <arraybolt3> I assume he was referring to the ISO failing to build
[04:00] <arraybolt3> so I meant the ISO build dying
[04:00] <liushuyu> arraybolt3: Ah okay
[04:27] <vorlon> liushuyu: lubuntu built
[04:28] <vorlon> boo I missed unblocking linux
[04:30] <vorlon> arraybolt3: I don't have the log in front of me to say what the failure was, but I don't think there was mention of mozjs
[04:31] <vorlon> arraybolt3: ah that was the one that was trying to pull in pulseaudio
[04:32] <vorlon> skiptest librist, it passed its tests with all-proposed but didn't have the right trigger to be seen
[04:39] <liushuyu> vorlon: 1148s E       ModuleNotFoundError: No module named '_sysconfigdata__i386-linux-gnu' > this Python module is in libpython3.12-minimal:i386
[04:40] <liushuyu> but the package is probably not co-installable with libpython3.12-minimal:amd64, haven't tested this configuration
[04:42] <dbungert> liushuyu: https://irclogs.ubuntu.com/2024/04/07/%23ubuntu-release.html#t02:46
[04:44] <liushuyu> so hint this? otherwise numpy won't migrate
[04:44] <liushuyu> migration-reference test show the previous baseline passes
[04:46] <liushuyu> oh, it's already hinted
[04:57] <liushuyu> Hmm, it seems like we have unclogged all the flavours
[05:25] <vorlon> liushuyu: right, again super-low care factor about arch: all python modules failing their tests on i386
[05:25] <vorlon> they shouldn't even be getting tested (this has been discussed w/ QA Team)
[05:28] <vorlon> dbungert: now that the ausrede output is getting super-low, it's time to widen the net to include all the packages still in noble-updates that haven't been superseded.  I've been running the following to identify the packages in noble-updates that HAVE been superseded so that they can be removed, it would be good to have a report on the inverse: $ for source in $(sed -n -e's/^Package: //p'
[05:28] <vorlon> /var/lib/apt/lists/*noble-updates*Sources); do grep-dctrl -FSource:Package -X $source -a -FArchitecture amd64 /var/lib/apt/lists/*noble_*binary-amd64*Packages >/dev/null && echo $source; done
[05:33] <vorlon> removing gbrainy, gtk-sharp3 on armhf
[05:34] <vorlon> dbungert: fwiw I would go so far as to say that the ausrede reports are now counterproductive in terms of prioritization, since e.g. they now pick up things like gst-plugins-good1.0 being out-of-date on riscv64 and that is no longer a package of concern for xz-utils recovery
[05:35] <vorlon> ah gtk-sharp3 is already removed from release on armhf, it's just noble-updates that's the problem again. hinting
[05:39] <vorlon> hinting vorbis-tools (libvorbis/i386 test failure because linux-libc-dev)
[05:42] <vorlon> rebuilding ghdl because hit by the libllvm-18 mis-linkage
[06:20] <vorlon> oh man, tetrinetx still exists?
[06:23] <vorlon>     got exception: MigrationConstraintException('trying cruft removal item -linux-tools-virtual/amd64/6.8.0-11.11+1, while testing has linux-tools-virtual/6.8.0-22.22 on amd64')
[06:24] <vorlon> sigh
[06:24] <vorlon> hard-copying linux*
[06:24] <vorlon> (linux linux-restricted-modules linux-signed linux-meta)
[07:08] -queuebot:#ubuntu-release- Unapproved: cockpit-machines (jammy-backports/universe) [307-1~bpo22.04.1 => 310-1~bpo22.04.1] (no packageset)
[07:08] -queuebot:#ubuntu-release- Unapproved: cockpit-machines (mantic-backports/universe) [307-1~bpo23.10.1 => 310-1~bpo23.10.1] (no packageset)
[07:37] <vorlon> 2024-04-07 07:36:57 DEBUG   Ciao
[07:54] <vorlon> -#if defined(HAS_UNISTD_H)
[07:54] <vorlon> +#if defined(HAVE_UNISTD_H)
[07:54] <vorlon> :|
[08:05] <vorlon> linux-meta published; image respins begun
[08:18] <vorlon> kanashiro: I notice some ruby-rack* packages are now stuck in -proposed because they depend on ruby-rack (>= 3).  Is it time to revive ruby-rack 3.0.8-1?
[08:30] <vpa1977> nfs-utils can be synced if we need another no-change rebuild for it
[08:31] <vpa1977> (merged)
[09:47] <sil2100> o/
[09:47] <sminez>  /window list
[09:53] <sil2100> Okay, I see cinnamon still has issues building, pipewire
[10:03] <mitya57> vorlon: hi! I have prepared Qt 5.15.13 in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4979/+packages, can I land it today? It looks like the previous version of Qt finally migrated on Friday.
[10:05] <mitya57> And another question: I fixed flightgear FTBFS (LP: #2058975) and uploaded NMU to Debian's DELAYED/2. It also needed some fixes in simgear. Can we wait 2 days and sync them normally, or I should do it earlier (e.g. in the same PPA)?
[10:05] -ubottu:#ubuntu-release- Launchpad bug 2058975 in flightgear (Ubuntu) "proposed-migration for flightgear 1:2020.3.18+dfsg-1build3" [Undecided, New] https://launchpad.net/bugs/2058975
[10:05] <juliank> https://magenta.jak-linux.org/ubuntu-archive/distcheck/noble/release-binaries.txt now groups the report by source package instead of binary package
[10:07] <juliank> especially useful for sth like Packages depending on src:python3-stdlib-extensions:
[10:07] <juliank> (which has migrated now but not yet updated reports)
[10:09] <doko> A server error has occured, please contact a member of the Ubuntu QA team. You can contact them via the ubuntu-quality mailing list, or via the #ubuntu-quality IRC channel on irc.libera.chat (highlight 'qa-help' for more reactivity). Traceback: local variable 'msg' referenced before assignment
[10:11] <sil2100> mitya57: I assume that's the target Qt version we want for the release/beta, right?
[10:13] <mitya57> sil2100: I would want it, right. It's yet another bugfix release in LTS 5.15 series, which only receives important fixes at this point.
[10:21] <sil2100> mitya57: since vorlon is likely asleep now, I'd say go for it. The Kubuntu images are building correctly now, and I think we all need the time to prepare everything before the Beta next week
[10:21] <sil2100> So even though it's a lot of packages, I guess there won't be a better time
[10:21] <mitya57> Okay, thanks. Copying to archive then.
[10:47] <fossfreedom_> ubuntu-release a quick FYI - for UB the installer crashes and burns;  the candidate snap works just fine.  So probably needs a ubuntu-desktop team member to promote the candidate snap - at least before beta freeze occurs!
[10:48] <sil2100> fossfreedom_: ACK o/
[11:06] -queuebot:#ubuntu-release- New binary: rust-wayland-backend [amd64] (noble-proposed/universe) [0.3.3-1] (no packageset)
[11:07] -queuebot:#ubuntu-release- New binary: rust-wayland-backend [s390x] (noble-proposed/universe) [0.3.3-1] (no packageset)
[11:07] -queuebot:#ubuntu-release- New binary: rust-wayland-backend [armhf] (noble-proposed/universe) [0.3.3-1] (no packageset)
[11:07] -queuebot:#ubuntu-release- New binary: rust-wayland-backend [arm64] (noble-proposed/universe) [0.3.3-1] (no packageset)
[11:07] -queuebot:#ubuntu-release- New binary: rust-wayland-backend [ppc64el] (noble-proposed/universe) [0.3.3-1] (no packageset)
[11:19] -queuebot:#ubuntu-release- New binary: rust-wayland-backend [riscv64] (noble-proposed/universe) [0.3.3-1] (no packageset)
[11:23] <sil2100> hm, I don't understand why the cinnamon problem is happening. germinate insists to pull in pulseaudio-module-bluetooth to satisfy blueman even though libspa-0.2-bluetooth is perfectly installable
[11:24] <sil2100> I see previously libspa-0.2-bluetooth was being pulled in to satisfy gnome-settings-daemon
[11:42] <juliank> sil2100: is pa module seeded explicitly somewhere
[11:42] <juliank> But meh when in doubt seed the libspa one explicitly and be happY?
[11:43] <sil2100> No, doesn't look like it, I didn't see it in neither the cinammon or platform seeds
[11:46] <sil2100> Well, seeding is and option, but also I'd like to understand why it's suddenly not pulled in. I also am not a big fan of putting a package into the seeds that has a lib version in it
[11:46] <sil2100> Then again, meh
[12:06] <sil2100> Interesting, looks like somehow previously something was pulling in gnome-settings-daemon into cinnamon, but now doesn't - and this causes the whole mismatch
[12:07] <sil2100> I'm getting a feeling that this might be the better option?
[12:14] <sil2100> Ok, trying that
[12:29] <sil2100> hm, I think for studio we were waiting for imath, which should be all good now? Kicking an experimental re-build
[12:54] <sil2100> oh, is it because we have imath in -updates?
[12:54] <sil2100> I'll remove it from -updates
[12:55] <sil2100> ...ah, forgot, I can't ._.
[13:00] <sil2100> vorlon: what do we do in such cases? ^
[13:02] <juliank> I think we'll freeze tomorrow again and do a cleanup?
[13:02] <juliank> Or just freeze archive now and clean it up :D
[13:03] <juliank> Not like there's much going on is there
[13:15] <sil2100> Rebuilding cinnamon to see how things are looking
[13:24] <howarth> Is there a schedule yet for re-enabling 'do-release-upgrade -d' for 24.04 upgrades?
[13:25] <howarth> Currently the existence of a devel release appears to be masked
[13:34] <sil2100> vorlon: ok, so now cinnamon also fails on imath!
[13:34] <sil2100> howarth: I'd say somewhen next week. We're still finalizing all the package rebuilds due to the xz-backdoor
[13:37] <doko> ginggs, sil2100: please hint boost1.83. the only failing autopkg test is pyobjcryst, which was removed
[13:38] <sil2100> doko: ACK
[13:43] <sil2100> Done
[13:43]  * sil2100 AFK
[14:44] -queuebot:#ubuntu-release- New: accepted rust-wayland-backend [amd64] (noble-proposed) [0.3.3-1]
[14:44] -queuebot:#ubuntu-release- New: accepted rust-wayland-backend [armhf] (noble-proposed) [0.3.3-1]
[14:44] -queuebot:#ubuntu-release- New: accepted rust-wayland-backend [riscv64] (noble-proposed) [0.3.3-1]
[14:44] -queuebot:#ubuntu-release- New: accepted rust-wayland-backend [arm64] (noble-proposed) [0.3.3-1]
[14:44] -queuebot:#ubuntu-release- New: accepted rust-wayland-backend [s390x] (noble-proposed) [0.3.3-1]
[14:44] -queuebot:#ubuntu-release- New: accepted rust-wayland-backend [ppc64el] (noble-proposed) [0.3.3-1]
[14:49] <dbungert> vorlon: will do
[14:51] <dbungert> and yes, I can stop the reports if they aren't focusing on the right things
[17:14] -queuebot:#ubuntu-release- New binary: rust-wayland-client [amd64] (noble-proposed/universe) [0.31.2-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: rust-wayland-client [ppc64el] (noble-proposed/universe) [0.31.2-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: rust-wayland-client [s390x] (noble-proposed/universe) [0.31.2-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: rust-wayland-client [armhf] (noble-proposed/universe) [0.31.2-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: rust-wayland-server [ppc64el] (noble-proposed/universe) [0.31.1-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: rust-wayland-server [amd64] (noble-proposed/universe) [0.31.1-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: rust-wayland-server [arm64] (noble-proposed/universe) [0.31.1-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: rust-wayland-server [s390x] (noble-proposed/universe) [0.31.1-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: rust-wayland-server [armhf] (noble-proposed/universe) [0.31.1-1] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: rust-wayland-client [arm64] (noble-proposed/universe) [0.31.2-1] (no packageset)
[17:20] <howarth> filed https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2060394 to remind them to stop hiding the development release now that the mass rebuild is completed and live images are being built again
[17:20] -ubottu:#ubuntu-release- Launchpad bug 2060394 in ubuntu-release-upgrader (Ubuntu) "do-release-upgrade -d currently non-functional" [Undecided, New]
[17:29] -queuebot:#ubuntu-release- New binary: rust-wayland-client [riscv64] (noble-proposed/universe) [0.31.2-1] (no packageset)
[17:31] -queuebot:#ubuntu-release- New binary: rust-wayland-server [riscv64] (noble-proposed/universe) [0.31.1-1] (no packageset)
[18:26] <arraybolt3> um, what happened to zram-config?
[18:28] -queuebot:#ubuntu-release- New: accepted rust-wayland-server [amd64] (noble-proposed) [0.31.1-1]
[18:28] -queuebot:#ubuntu-release- New: accepted rust-wayland-server [ppc64el] (noble-proposed) [0.31.1-1]
[18:28] -queuebot:#ubuntu-release- New: accepted rust-wayland-server [s390x] (noble-proposed) [0.31.1-1]
[18:28] -queuebot:#ubuntu-release- New: accepted rust-wayland-server [arm64] (noble-proposed) [0.31.1-1]
[18:28] -queuebot:#ubuntu-release- New: accepted rust-wayland-server [riscv64] (noble-proposed) [0.31.1-1]
[18:28] <arraybolt3> must have used to been a dependency and now is no longer, doing some fiddling
[18:29] -queuebot:#ubuntu-release- New: accepted rust-wayland-client [amd64] (noble-proposed) [0.31.2-1]
[18:29] -queuebot:#ubuntu-release- New: accepted rust-wayland-client [armhf] (noble-proposed) [0.31.2-1]
[18:29] -queuebot:#ubuntu-release- New: accepted rust-wayland-client [riscv64] (noble-proposed) [0.31.2-1]
[18:29] -queuebot:#ubuntu-release- New: accepted rust-wayland-server [armhf] (noble-proposed) [0.31.1-1]
[18:29] -queuebot:#ubuntu-release- New: accepted rust-wayland-client [arm64] (noble-proposed) [0.31.2-1]
[18:29] -queuebot:#ubuntu-release- New: accepted rust-wayland-client [s390x] (noble-proposed) [0.31.2-1]
[18:29] -queuebot:#ubuntu-release- New: accepted rust-wayland-client [ppc64el] (noble-proposed) [0.31.2-1]
[18:51] <ginggs> trying: gnat libtexttools liblog4ada libxmlezout libaunit libgmpada anet libgnatcoll libgnatcoll-bindings libgnatcoll-db gprbuild libxmlada libtemplates-parser libflorist ahven adasockets pcscada dbusada libgtkada libncursesada adacgi plplot libalog
[18:51] <ginggs> britney seems to miss alire from ^
[18:51] <ginggs> what hint would help?
[18:54]  * ginggs tries an easy hint
[19:15] -queuebot:#ubuntu-release- New binary: rust-wayland-cursor [amd64] (noble-proposed/universe) [0.31.1-1] (no packageset)
[19:16] -queuebot:#ubuntu-release- New binary: rust-wayland-cursor [arm64] (noble-proposed/universe) [0.31.1-1] (no packageset)
[19:16] -queuebot:#ubuntu-release- New binary: rust-wayland-cursor [s390x] (noble-proposed/universe) [0.31.1-1] (no packageset)
[19:16] -queuebot:#ubuntu-release- New binary: rust-wayland-cursor [armhf] (noble-proposed/universe) [0.31.1-1] (no packageset)
[19:16] -queuebot:#ubuntu-release- New binary: rust-wayland-cursor [ppc64el] (noble-proposed/universe) [0.31.1-1] (no packageset)
[19:17] <ahasenack> vorlon: a few days ago you mentioned nfs-server failing on s390x (https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2060217)
[19:17] -ubottu:#ubuntu-release- Launchpad bug 2060217 in nfs-utils (Ubuntu) "NFSv4 fails to mount in noble/s390x" [High, Triaged]
[19:17] <ahasenack> vorlon: I can reproduce it, but cannot further troubleshoot it I think, it got into kernel things
[19:17] <ahasenack> 1998 mount("localhost:/home", "/mnt/nfs_home", "nfs", 0, "vers=4.2,addr=127.0.0.1,clientad"...) = -1 EIO (Input/output error)
[19:18] <ahasenack> I'll try to get the kernel team's attention tomorrow
[19:19] <ahasenack> interestingly, since we don't have noble images, I started with mantic, and I set it up there first to confirm it's working in mantic
[19:19] <ahasenack> then I dist-upgraded, and it started failing
[19:29] -queuebot:#ubuntu-release- New binary: rust-wayland-cursor [riscv64] (noble-proposed/universe) [0.31.1-1] (no packageset)
[19:57] <apw> vorlon, ok sorted the subscribers
[20:02] <apw> vorlon, on the seeding, i am expecting that thing to be where oem-24.04 points ... oh perhaps we are still seeding 22.04
[20:17] <vpa1977> anything that I can help with?
[20:29] <mwhudson> good morning
[20:30] <vpa1977> mwhudson: morning =)
[20:39] -queuebot:#ubuntu-release- New binary: rust-wayland-protocols [amd64] (noble-proposed/universe) [0.31.0-1] (no packageset)
[20:40] -queuebot:#ubuntu-release- New binary: rust-wayland-protocols [s390x] (noble-proposed/universe) [0.31.0-1] (no packageset)
[20:40] -queuebot:#ubuntu-release- New binary: rust-wayland-protocols [armhf] (noble-proposed/universe) [0.31.0-1] (no packageset)
[20:41] -queuebot:#ubuntu-release- New binary: rust-wayland-protocols [ppc64el] (noble-proposed/universe) [0.31.0-1] (no packageset)
[20:42] -queuebot:#ubuntu-release- New binary: rust-wayland-protocols [arm64] (noble-proposed/universe) [0.31.0-1] (no packageset)
[20:42] <mwhudson> so some desktop isos got made apparently?
[20:43] <mwhudson> and server
[20:44] <mwhudson> and at least some flavors
[20:48] <bdmurray> I'm requeueing tests with `--min-age 4` and `--state=RUNNING`.
[20:48] <dbungert> perl seems sad.  Attempting to build a noble-chroot fails on perl-modules-5.38, and rmadison says that both 5.38.2-3 and 5.38.2-3.2build2 are present in noble (not noble-updates or noble-proposed).  Publishing history says 5.38.2-3 should be Deleted at this point.  ubuntu-archive: please delete perl 5.38.2-3 from noble
[20:51] <bdmurray> dbungert: the publishing history shows things are okay
[20:51] <bdmurray> https://launchpad.net/ubuntu/+source/perl/+publishinghistory
[20:51] <dbungert> bdmurray: rmadison output on perl-modules-5.38 looks odd
[20:52] <vpa1977> dbungert: vorlon explained it is due to dependencies not fully removed
[20:52] <dbungert> darn
[20:55] -queuebot:#ubuntu-release- New binary: rust-wayland-protocols [riscv64] (noble-proposed/universe) [0.31.0-1] (no packageset)
[21:06] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-535-server [amd64] (noble-proposed/restricted) [535.161.08-0ubuntu2] (i386-whitelist)
[21:07] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-535 [amd64] (noble-proposed/restricted) [535.171.04-0ubuntu2] (i386-whitelist)
[21:07] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-535-server [arm64] (noble-proposed/restricted) [535.161.08-0ubuntu2] (i386-whitelist)
[21:12] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-535 [arm64] (noble-proposed/restricted) [535.171.04-0ubuntu2] (i386-whitelist)
[22:35] <tsimonq2> vorlon: Lubuntu built> thank you! :)
[22:36]  * tsimonq2 fixes some Ubuntu MATE bugs in livecd-rootfs
[22:51] <dbungert> tsimonq2: +1
[23:02] <tsimonq2> dbungert: I tagged your upload btw ;)
[23:07] <dbungert> just needed the tag push, so I've fixed it
[23:07] <tsimonq2> cool :) it's just a tag, no worries, glad it's sorted now