[00:01] <cpete> vorlon: how can I tell if a package in proposed has been built against a new lib?
[00:01] <vorlon> cpete: put noble-proposed in your sources.list and look at its deps?
[00:02] <cpete> vorlon: I guess that would make sense. thanks
[00:30] <cpete> bug for upower regression btw (only arm64): #2060335. I wonder if another ncr will fix. I'll give it a shot in a ppa. but I guess we should hint it to allow it to migrate? vorlon:
[00:31] <vpa1977>  perl-modules-5.38 | 5.38.2-3         | noble          | all
[00:31] <vpa1977>  perl-modules-5.38 | 5.38.2-3.2build1 | noble          | all
[00:31] <vpa1977> I am a bit confused, there are two of them in noble
[00:32] <vpa1977> (just failed to setup chroot)
[00:32] <vorlon> vpa1977: architecture: all packages are autoremoved only when all of the arch-specific packages from the same source are also removed.  So this will be due to NBS libperl5.38
[00:33] <vpa1977> vorlon: thank you!!!
[00:35] <vorlon> haven't restarted britney yet because I also haven't seen the results of the latest publisher run yet <sigh>
[00:36] <vorlon> it's updated on ftpmaster.internal though
[00:36] <vorlon> so yes restarting
[00:42] <vorlon> archive.u.c updated
[00:43] <cpete> okay and for kubuntu: there is an amd64 regression for qtwebenginge-opensource-src/5.15.16+dfsg vs yuzu/0-1445+ds-1.3 last it ran ~4 hours ago it failed to install test dependencies so I've re-queued the test w/ all-proposed to see happens. Otherwise I think that's the running angle for kubuntu
[00:44] <cpete> unfortunately I don't have time to investigate further today. have a great weekend
[00:44]  * cpete eod
[00:44] <vorlon> ok unblocking qtwebengine-opensource-src, because it's a no-change bebuild
[00:44] <vorlon> cpete: thanks, have a good weekend
[00:44] <cpete> o/
[00:50] <vorlon> current britney is behaving much more sanely
[00:51] <vorlon> I: [2024-04-06T00:49:06+0000] - Building the list of non-installable packages for the full archive
[00:51] <vorlon> I: [2024-04-06T00:49:51+0000] - > Found 2072 non-installable packages
[01:12] <vorlon> have to wait for britney to schedule a bunch of tests for the new perl upload though, boo
[10:51] -queuebot:#ubuntu-release- New sync: xapers (noble-proposed/primary) [0.9.0-4]
[16:15] <tsimonq2> Alright, let me get this straight... *ALL* ISOs have been failing for *over a week*. TWICE now I have suggested solutions for this issue... the first time I suggested looking at the pristine tar used for builds, the second time I suggested ubuntu-cdimage fixes. This would have been solved a WHILE ago had we simply enabled noble-updates for the livefs builds. We go straight from time_t to xz, and
[16:15] <tsimonq2> we've had close to NO opportunities to test what we will be releasing for Noble, for the last THREE months. Why? Why do we not want to get these ISOs working again? Why do we continue to look at migrating everything as a priority, when we could simply unblock many efforts by getting the ISOs building?
[16:16] <tsimonq2> I *have* to be missing something.
[16:17] <tsimonq2> Please, someone do tell me. I want to know why Lubuntu has had *no* recent dailies to test, and why this is the case *TWO DAYS* before Beta Freeze.
[16:17] <tsimonq2> If this is something I could fix, I would have fixed it already. Even Ubuntu Desktop is failing.
[16:18] <tsimonq2> RUN: /usr/share/launchpad-buildd/bin/in-target override-sources-list --backend=lxd --series=noble --arch=amd64 LIVEFSBUILD-601105 'deb http://ftpmaster.internal/ubuntu noble main universe'
[16:18] <tsimonq2> That should have updates in there as well.
[16:18] <tsimonq2> What actually does the Launchpad API call to create the livefs build? ubuntu-cdimage... right?
[16:19] <tsimonq2> ubuntu-release, vorlon, mwhudson: you all get pings ^^^
[16:20] <tsimonq2> Again, if I'm wrong, *tell me*. I have every right to be incredibly frustrated by this.
[16:26] <tsimonq2> LiveFS lubuntu/noble/amd64 failed to build on 20240328 LiveFS lubuntu/noble/amd64 failed to build on 20240329 LiveFS lubuntu/noble/amd64 failed to build on 20240329 LiveFS lubuntu/noble/amd64 failed to build on 20240330 LiveFS lubuntu/noble/amd64 failed to build on 20240331 LiveFS lubuntu/noble/amd64 failed to build on 20240401 LiveFS lubuntu/noble/amd64 failed to build on 20240401 LiveFS
[16:26] <tsimonq2> lubuntu/noble/amd64 failed to build on 20240402 LiveFS lubuntu/noble/amd64 failed to build on 20240403 LiveFS lubuntu/noble/amd64 failed to build on 20240404 LiveFS lubuntu/noble/amd64 failed to build on 20240405
[16:26] <tsimonq2> I get emails about this *every day*.
[16:29] <tsimonq2> Errors were encountered while processing:  libtirpc3t64:amd64  iproute2  netplan.io  gpgv  apt  apt-utils  ubuntu-minimal
[16:37] <vorlon> tsimonq2: you want an image with a bunch of unreleasable packages from February? that's easy, take the last successful build.  That's what enabling noble-updates would have gotten you.  We've been working around the clock all week to get the noble release pocket back into a releasable state on amd64 in the face of the xz-utils attack, and if you wanted to help make that happen you could have spoken
[16:38] <vorlon> up at any time during the ongoing coordination work here
[16:46] <vorlon> gnupg2 has been uploaded to rebuild against libnpth0t64 which will fix the last known debootstrap failure (and which was hidden by packages in noble-updates until we did noble-updates removals yesterday).  ffmpeg tests given back.  mpg123 force-hinted.  This should take care of the last blockers I'm aware of on Ubuntu and Lubuntu.
[16:47] <vorlon> there seems to be some arm64-specific breakage on x13s images with something depending on libgpod4 instead of libgpod4t64, which someone will need to look into
[16:51] <tsimonq2> vorlon: you could have spoken up at any time> I did, twice. I asked about noble-updates being a possible solution and got ignored, twice. Had someone just taken the second to explain "hey, we can't do that because it wouldn't be DTRT," I would have been okay with that and put some time on the calendar to get it sorted.
[16:51] <tsimonq2> That being said, it's whatever at this point.
[16:51] <tsimonq2> Thank you for helping unblock Lubuntu, at least.
[16:52] <tsimonq2> I'll see if I can find anything interesting WRT the x13s images.
[16:54] <ahasenack> is something broken in LP regarding ppas, and add-apt-repository perhaps? I'm seeing tests that call add-apt-repository fail with a 504 gateway timeout
[16:54] <ahasenack> and yes, I can ask in #launchpad
[16:55] <vorlon> ahasenack: no idea
[16:55] <ahasenack> but given people here are more closely looking at the excuses page and such, it might be faster to get an answer here :)
[16:56] <ahasenack> hmm, maybe it's the proxy
[16:56] <ahasenack> squid.internal
[16:56] <vorlon> ahasenack: I've been online less than an hour this morning, and no activity in this channel since I went to bed, I don't think anyone's currently worrying about update_excuses refresh rate
[16:56] <bdmurray> ahasenack: which arch? test log?
[16:56] <ahasenack> https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-jammy/jammy/amd64/s/software-properties/20240406_143413_3d6bc@/log.gz
[16:57] <ahasenack> but this also failed (noble, amd64): https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/amd64/s/software-properties/20240405_144352_1a3b6@/log.gz
[17:00] <bdmurray> that looks like launchpad timing out to me
[17:01] <bdmurray> "1144s lazr.restfulclient.errors.ServerError: HTTP Error 504: Gateway Time-out"
[17:01] <ahasenack> also in yesterday's run: https://autopkgtest.ubuntu.com/packages/software-properties/noble/ppc64el
[17:01] <ahasenack> the top 2 are fails because of this
[17:01] <vorlon> very strange, only package depending on libgpod4 on arm64 is gpodder which is certainly not part of the Ubuntu Desktop seed
[17:02] <vorlon> and libgpod4 should be on the NBS list but isn't because of noble-updates
[17:02] <vorlon> I'll just remove libgpod4/arm64 from the release pocket and see if that helps any
[17:03] <ahasenack> is noble-updates almost clear?
[17:03] <vorlon> ahasenack: $ cat /var/lib/apt/lists/*noble-updates_*Sources | grep -c Package:
[17:03] <vorlon> 1028
[17:03] <vorlon> $
[17:03] <vorlon> "almost"
[17:03] <ahasenack> looks better
[17:03] <ahasenack> last I remember it was 5k or so
[17:04] <vorlon> 7120 originally
[17:04] <vorlon> another 282 packages are currently superseded and could be removed but that requires freezing the archive again to do it
[17:05] <vorlon> I'm confused what https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntu/+build/601360 is, I didn't recall us having a generic arm64 desktop image that we built
[17:06] <vorlon> letting gnupg2, mpg123, ffmpeg work their way through; afk again
[17:15] <tsimonq2> vorlon: concur with removing libgpod4, the missing piece is https://launchpad.net/ubuntu/noble/arm64/rhythmbox-plugins/3.4.7-2ubuntu6
[17:31] <vorlon> tsimonq2: what do you see that says this is missing? my chdist says the arm64 binary already depends on libgpod4t64
[17:33] <tsimonq2> $ reverse-depends libgpod4
[17:33] <tsimonq2> [...]
[17:33] <tsimonq2> Reverse-Depends
[17:33] <tsimonq2> * rhythmbox-plugins [amd64 arm64 armhf ppc64el s390x]
[17:36] <tsimonq2> I mean, that does follow. https://launchpad.net/ubuntu/+source/rhythmbox/3.4.7-2ubuntu2 was the last upload in the release pocket and that looks to be before time_t... although there is something off here.
[18:26] <vorlon> tsimonq2: the current rhythmbox-plugins in noble is 3.4.7-2ubuntu6
[18:26] <vorlon> ah but it published 9 hours ago
[18:26] <vorlon> there you go then, race condition
[18:27] <doko> so how did that libnpth0 dependency hide?
[18:28] <vorlon> doko: because libnpth0t64 Provides: libnpth0
[18:28] <vorlon> but debootstrap evidently doesn't want that
[18:29] <vorlon> and I guess at this stage noble-updates is enabled in sources, so the resuscitated real libnpth0 binary in -updates - which we cleaned up yesterday as part of trying to fix britney performance - apparently made apt happy
[18:30] <vorlon> anyway britney seems to be running well today, and I'm going to go ahead and add a skiptest hint since this is a no-change rebuild https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html#gnupg2
[18:32] <vorlon> ffmpeg tests coming along, a shame no one triggered these yesterday
[18:34] <tsimonq2> vorlon: thank you :)
[18:38] <doko> well, all autopkg tests failed today anyway:
[18:38] <doko> 1142s The following packages have unmet dependencies:
[18:38] <doko> 1142s  apt : Depends: gpgv
[18:38] <doko> 1142s E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
[18:38] <doko> 1142s blame:
[19:58] <vorlon> doko: not those triggered with --all-proposed. What tests are you looking at?
[20:03] <vorlon> bdmurray, paride: https://autopkgtest.ubuntu.com/packages/r/rust-sequoia-wot/noble/armhf is special, not running with --all-proposed, test being run against the -proposed version of rust-sequioa-wot (why?) which then fails because it downloads the release pocket versions of the binary packages
[20:05] <vorlon> ffmpeg autopkgtests cleaned up nicely, even diffoscope tests passing now
[20:12] <vorlon> skiptesting the remainder which are unrelated failures
[20:15] <vorlon> gst-plugins-good1.0 apparently needs forcing because armhf
[20:17] <vorlon> (done)
[20:24] <vorlon> afk for a few hours.  gnupg2 2.4.4-2ubuntu17 published but not yet on the mirror, so worth checking debootstrap in a little bit.  The above hints should unblock the rest of what I see for ubuntu-desktop, lubuntu-desktop, ubuntucinnamon-desktop, ubuntu-mate-desktop, xubuntu-desktop. kubuntu and ubuntu-unity still have a few more per-flavor things to go (gdb?!).  I haven't looked at edubuntu and
[20:24] <vorlon> ubuntustudio yet as they have significantly larger package sets and have prioritized clearing the smaller images first.
[20:25] <vorlon> going to be worth looking at https://ubuntu-archive-team.ubuntu.com/proposed-migration/noble_uninst.txt soon
[20:27] <vorlon> pytest autosync in -proposed continues to be an obstacle for --all-proposed tests.  Removing it now
[22:03] <liushuyu> for the flavor Ubuntu Kylin: ukui-biometric-auth needs a rebuild: depends on pre-transition libopencv-core406
[22:17] <liushuyu> trying to also get peony migrated
[23:05] <dbungert> analyzed failure of amd64 sbuild chroot creation.  libc6-dev -> linux-libc-dev fails without proposed.  No action taken as this is just hinted as waiting on kernel testing.
[23:59] <vorlon> lubuntu not yet ready, ffmpeg also needs librist which has failing autopkgtests
[23:59] <vorlon> and depends on mbedtls which is also not happy