[00:00] I'll take a look at some of the failures for glibc then [00:01] nb the util-linux security update is to the 'wall' command, chances of this regressing any revdeps are ~ 0 [00:03] vpa1977: thanks for opening those bug reports on the regressed util-linux revdeps. hinting util-linux through now [00:03] that leaves only (trivial, insignificant, you'll barely notice it's missing) glibc from the Priority: required set [00:04] Ok, so I see glibc's abseil and ableton-link failures seem to be badpkg cmake-data related, which as I understand correctly is just a matter of migrating cmake? [00:05] good lord, flavors are pulling in gdebi -> lintian -> build-essential -> gcc in their desktops? [00:05] Looking at the adsys regression [00:05] sil2100: or of retesting with all-proposed, which is queued but will take time [00:06] sil2100: but see also my doc above with triage notes :) [00:07] "if a test fails because of uninstallability of test deps, but there is at least one architecture on which the test passes, this is ignorable" [00:07] sil2100: please also feel free to /sanity check/ my triage notes, but these are the principles I'm currently following, I think [00:08] +1 on those! [00:08] Ok, adsys regression seems to be hm, unrelated to glibc. It fails the same way on other packages, was failing the same way in the past as well [00:08] So more like ignore/hint material [00:08] Moving on [00:09] thanks for the notes, that's helpful [00:09] Looking at alsa-lib regression... actually not, i386, moving on [00:09] Looking at anet [00:11] Okay, anet also unrelated, package was failing similar with the release glibc [00:12] I'll hint it since it will just continue to fail, I'll get a bug as well [00:16] Looking at apparmor [00:16] afk for dinner [00:17] apparmor glibc regressions look like badpkg, so ignoring as per current policy! Other arche is okay [00:17] Looking apt [00:18] apt = badpkg, mostly cmake, non-blocking [00:18] I took a look at libgpod and I sent a message here but I am not sure if people noticed it. It is in main and depends on libimobiledevice-dev, the libimobiledevice-dev is in main in all arches but amd64 (not sure why) in the release pocket. And in universe in all arches in -updates [00:18] https://chat.debianbsb.org/file/3/W5wVK5Qn6sYJX5VL [00:19] Looking arrayfire on glibc [00:19] any hint on that? [00:22] arrayfire another badpkg on cmake, nonblockable [00:22] Checking authd [00:23] uuuu, this looks worse [00:26] Then again, the same test passed for 2.39-0ubuntu7, which is the actual new version of glibc. So I'd say it non-blockable as well, we can ignore that [00:27] Checking auto-multiple-choice [00:27] ...badpkg, passed with ubuntu7 [00:27] Ignoring [00:28] DChecking ayatana-indicator-session [00:28] badpkg, fine on other arches, moving on [00:28] Checking benchmark [00:29] Another badpkg [00:29] Checking binutils [00:30] Actually passed with an additional trigger, moving on [00:30] bliss [00:32] I queued up a migration reference test, I assume it's just broken, so I'd ignore it (non-blocking) [00:32] Checking boost1.74 [00:33] Testbed errors, but passed fine on ubuntu7, so non-blocking [00:34] Checking booth [00:35] badpkg, other arches fine, non-blocking [00:35] Checking brlaser [00:35] All proposed passed, moving on [00:35] bruteforce-wallet... [00:36] Timed out, but I see it timed out similarly in the past - also, passed for ubuntu7, ignoring [00:37] Checking burp, tests still running but I see that it already passed for ubuntu7 [00:37] soooo, ignoring [00:37] burrow passed [00:37] bustools passed for ubuntu7 [00:38] bwa same, passed for ubuntu7 [00:38] Checking c2esp [00:39] Constantly failing, wouldn't block on this, unrelated to glibc [00:39] c2x passed for ubuntu7 [00:40] cadaver... always neutral, even for ubuntu7, skip [00:40] calculix-ccx passed [00:41] calibre passes [00:41] camlpdf - passes [00:41] Yep, badpkg on 2 arches, passed on one, all good [00:42] (I'm also looking at the Test in progress ones) [00:42] looking capnproto [00:42] Looking at camlzip [00:42] ...passed on ubuntu7, we can ignore [00:43] Checking casa-formats-io [00:43] canproto - passed with ubuntu7 [00:43] casa-formats-io passed with ubuntu7, no reason why it should fail for a no-change rebuild [00:44] Looking at cataclysm-dda [00:44] looking at cbatticon [00:44] cataclysm-dda badpkg, good on other arches, skipping [00:45] Checking cbm [00:45] cbatticon - passed with ubuntu7 [00:45] neutral with ubuntu7, all good [00:45] looking cccolutils [00:45] Darn, that's a lot of autopkgtests [00:46] cccolutils - neutral with ubuntu7 [00:46] hm [00:46] pick a letter and go all the way with it ? [00:47] I wonder if it would be possible to somehow query the ADT db and check the test results for ubuntu7 and then scratch out all the failures/in-progress for ubuntu8 [00:47] I'll take [00:47] 'e' for now [00:47] I'll need to EOD soon but at least that'll be a few more packages [00:48] I'm looking at all 'e' starting autopkgtests for glibc - I'll grind through them and then put a summary (not to spam) [00:49] continuing with c then [00:53] Ok, all 'e' tests looking good, non-blockable [00:54] bdmurray: hey hey! Do you maybe have enough autopkgtest-db-foo to maybe figure something out here? We're looking at all glibc ubuntu8 test regressions - and basically since it's a no-change rebuild, I feel like we should ignore all tests that fail but passed on the ubuntu7 version [00:55] bdmurray: do you think there would be an easy way to query the DB for that? aka. grabbing all ubuntu8 failures, comparing with ubuntu7 results and if ubuntu7 passes, than informing that it's all good? [00:55] vorlon: ^ [00:56] Ok, I'll be EODing now, please be sure to leave a message for me and others on where this stands - if I wake up and need to continue, please let me know where [00:56] I get the feeling that glibc is hintable, but I guess it would be best to cut through some more tests [00:59] o/ [01:13] I think we dumped most of the tests from the queue for 0ubuntu7 without ever getting results tho [01:27] failing and test-in-progress links for glibc https://paste.ubuntu.com/p/PQyW2sPyjB/ (7152 items). We probably need a script [01:27] *lines [01:35] back === chris14_ is now known as chris14 [01:36] I'll try and query the test results for the previous glibc ubuntu7 run as that seems achievable [01:52] Alright, you could use this as a basis for comparison. [01:52] $ sqlite3 autopkgtest.db "SELECT distinct(result.run_id), result.exitcode, package, result.triggers FROM test, result WHERE te [01:52] st.id = result.test_id AND release ='noble' AND result.triggers IN ('glibc/2.39-0ubuntu7') ORDER BY package;" | pastebinit [01:52] https://dpaste.com/35GAWZFWP [01:52] are those are passed tests? [01:53] No you'd want to modify the query to include result.exitcode = 0 [01:55] https://dpaste.com/82SBLX2KF [01:56] Oh, the arch would be helpful too [01:58] https://dpaste.com/9VHU32AZA [02:02] accountservice is missing from the second paste [02:02] https://autopkgtest.ubuntu.com/packages/a/accountsservice/noble/amd64 [02:08] it hasn't succeeded in a long time though? [02:09] yes, but it was in the first paste ... [02:17] the second column in the first paste is exit code? [02:19] yes [02:19] It would be nice to pick up also neutral packages [02:24] do you know the neutral exit code? [02:25] no :( [02:28] Looks like 8 [02:28] https://dpaste.com/9SPF9KGHN see achilles [02:34] https://dpaste.com/BXZY5HQ2A-preview [02:35] filtered list of failures that did not have successful or neutral ubuntu7 run [02:35] and something wrong with paste again - chiark-tcl is not in paste [02:42] same highlighting amd64 and armhf [02:42] https://dpaste.com/2KM8TUHWX-preview [02:48] ummm where did the graph of autopkgtest throughput go https://ubuntu-release.kpi.ubuntu.com/d/yIC34LpGk/ubuntu-metrics?orgId=1 [02:49] oh here we go https://ubuntu-release.kpi.ubuntu.com/d/76Oe_0-Gz/autopkgtest?viewPanel=10&orgId=1&refresh=1m [02:50] raising bug for cura-engine (buffer overflow) [02:50] (its already there) [02:51] dnsmasq - always fail amd64 [02:52] docker.io-app - always fail [02:54] eztrace - existing bug https://bugs.launchpad.net/ubuntu/+source/eztrace/+bug/2059183 [02:54] -ubottu:#ubuntu-release- Launchpad bug 2059183 in eztrace (Ubuntu) "autopkgtest failure on eztrace/2.1-7ubuntu3" [Undecided, New] [02:55] fence-agents - false positive, passed on ubuntu7 [02:57] fitsverify - https://bugs.launchpad.net/ubuntu/+source/fitsverify/+bug/2059185 [02:57] -ubottu:#ubuntu-release- Launchpad bug 2059185 in fitsverify (Ubuntu) "fitsverify is uninstallable on Noble" [Undecided, New] [02:58] flatpak, fuse-zip - neutral [02:58] gdcm - https://bugs.launchpad.net/ubuntu/+source/gdcm/+bug/2060243 [02:58] -ubottu:#ubuntu-release- Launchpad bug 2060243 in util-linux (Ubuntu) "proposed migration util-linux 2.39.3-9ubuntu4 vs gdcm/3.0.22-2.1build2" [Undecided, New] [03:03] globalplatform - ftbfs, retrying [03:05] globalplatform - raised ftbfs https://bugs.launchpad.net/ubuntu/+source/globalplatform/+bug/2060262 [03:05] -ubottu:#ubuntu-release- Launchpad bug 2060262 in globalplatform (Ubuntu) "globalplatform fails to build from source" [Undecided, New] [03:07] did anyone analyze the regression of contourpy on arm64? [03:14] it appears it fails tests assuming more than one core. I will try it locally [03:14] yes [03:14] vorlon: do some of the autopkgtest works sometimes only have 1 thread? I filed https://bugs.launchpad.net/ubuntu/+source/contourpy/+bug/2060250 [03:14] -ubottu:#ubuntu-release- Launchpad bug 2060250 in contourpy (Ubuntu) "autopkgtests are flaky due to threadedness" [Undecided, New] [03:15] cpete: all the autopkgtest runners should have multiple (virtual) cores [03:16] dipy/arm64 doesn't look good [03:16] but also looks kinda flaky [03:19] gslang - raised https://bugs.launchpad.net/ubuntu/+source/glslang/+bug/2060263 - autopkgtest needs to be updated [03:19] -ubottu:#ubuntu-release- Launchpad bug 2060263 in glslang (Ubuntu) "autopkgtest fails due to removal of OGLCompiler" [Undecided, New] [03:19] vorlon: for whatever reason those tests always fail on s390x and ppc64el, and sometimes on arm64 [03:34] eod. After hacking away at numpy today I got down to mdp and found or filed bugs for regressions in: astroml, asymptote, contourpy, cython-legacy, and mdp. (ignoring i386 regressions). There may be more regressions before mdp but tests have still been queued on amd64. [03:52] What does this autopkgtest error generally mean? [03:52] badpkg: rules extract failed with exit code 1 [03:55] cpete: cheers! [03:55] pushkarnk: AIUI that usually means the package that's supposed to be tested doesn't actually have binaries on the arch in question [03:56] vorlon: ack, thanks [03:56] but that should be confirmed by looking at the archive, I guess [03:56] ack [04:12] did anybody look at gitbatch/armhf? "but cgo is not enabled" - clearly not caused by glibc, but [04:37] glibc revdep autopkgtest failures reviewed down to libz, all cleared [04:38] taking down through m now to review [04:47] cleared through m [04:47] afk for a bit [04:58] ugh why did libtirpc-common 1.3.4+ds-1build1 get left behind in noble release [04:58] well, fixed that blocker for server image bootstrap on riscv64 now [04:59] Because libtirpc3 is still published and NBS [04:59] darnit you're right [05:00] and fails to show up on the NBS report because noble-updates, sigh [05:00] Ahh heh [05:00] well anyway, libtirpc3 is uninstallable now, take that [05:00] reviewing n-o autopkgtest failuers [05:00] We must be very close to being able to clear out noble-updates. [05:01] we're close to being able to freeze the archive for beta, ish [05:01] clearing it out completely will increase uninstallability count and make britney sadder again, tho [05:02] Ah, true. [05:03] vpa1977: I've forgotten what the solution was supposed to be for '507s Exception in thread "main" java.lang.UnsatisfiedLinkError: /usr/lib/jvm/java-21-openjdk-s390x/lib/libfontmanager.so: libharfbuzz.so.0: cannot open shared object file: No such file or directory' [05:03] (nncp/s390x) [05:05] hmmm nodejs looks quite unhappy yet somehow there's been no discussion of nodejs here since the 27th [05:06] lots of SIGABRT [05:09] vorlon: install openjdk-21-jdk. We have made a patch to issue a warning, but it is merged only in openjdk-22 and -23. Which package is it ? [05:09] vpa1977: nncp/s390x [05:10] haha and nodejs itself fails its autopkgtests because it needs distutils [05:12] vorlon: ah, no, also in -21: 507s Please install the openjdk-*-jre package or recommended packages for openjdk-*-jre-headless. [05:13] plantuml needs upload - change binary dependency to -jre [05:19] n-o cleared [05:21] checking p-q [05:32] cleared p-q, and calling it there; still plenty of test failures of various stripes but nothing pointing to a glibc regression and nothing to block on at this point. hinting glibc [05:33] stopping current britney and restarting [05:39] seeing chroot upgrade failures on amd64 that seem likely to be due to systemd depending on libssl3 instead of libssl3t64, so uploading [05:48] hinting at-spi2-core (unblocks gnome-shell) [06:03] vorlon, libvirt 10.0.0-2ubuntu7 is now back in release (main). Can we remove the 10.0.0-1ubuntu1 version from updates? [06:19] I just read the IRC logs, so forget about it vorlon, I understand the removal will have to wait [06:28] flushing the remainder of glibc out of the queues, requeuing retries for remaining blocking tests [06:28] upils: good morning. is libvirt in -updates blocking something? [06:32] googd morning :). No, but I suspected having a "older" version in updates vs main could be problematic [06:32] *good [06:43] juliank: after jettisoning the rest of the queued tests for glibc, we're down to ~1000 tests total in the queue now, which is all the tests for all the seeded packages currently in -proposed. What should be the next thing in the queue? [06:43] that includes both --all-proposed retries of failed tests (in regular queue) and --all-proposed give-backs of 'running' tests (in huge queue) [06:48] hmm systemd takes 4 hours to build on riscv64; not waiting that long for a fix for amd64, hinting harder [06:51] juliank: my inclination is to next load up --all-proposed retries of all other failed tests not tied to seeded packages, then retries of running tests that were dumped from the queue, both of these in the huge queue; wdyt? [06:51] the latter should not be done on amd64+armhf due to lack of deduping for --state=RUNNING [07:00] well the uninstallable count on amd64 is down below the uninstallable count on armhf, so that's progress. Unfortunately that includes noble-updates tho [07:06] dbungert: I notice that https://people.canonical.com/~dbungert/ausrede/permafail.log includes packages that already have amd64 packages in the release pocket; e.g. bash which had to have a no-change rebuild in -proposed but whose release version was actually ok from before xz-utils. I guess we really want to filter the list for packages currently missing amd64 in the release pocket, rather than [07:06] just using the original list of bad packages [07:06] hmm britney thinking really, really hard right now about whether to remove libnorm1/amd64 :P [07:07] "really hard" as in for the past 10 minutes [07:08] and as in 100% CPU [07:08] uploaded plantuml. [07:15] hinting cairo [07:15] britney finally unstuck [07:33] hinting librsvg [07:34] update excuses seems a bit strange, e.g. for cmake: alglib is listed as in-progress, but the last time the test was run is 31 of march also nothing is queued https://autopkgtest.ubuntu.com/packages/a/alglib/noble/amd64 - [07:36] hinting policykit-1 [07:37] vpa1977: I think there's a race condition where tests have finished so drop out of 'running' but don't show up yet in the results [07:37] alglib is more than 1 week old ... [07:37] oh [07:38] well yes, we dropped all 'in progress' tests for packages that aren't seeded [07:38] for cmake magic-enum/0.9.5-2 was not triggered. [07:38] cmake is not seeded on any images [07:38] o/ [07:38] so we should retry all "in progress" tests for cmake [07:39] doing now [07:39] I think there is a bug somewhere, I tried it and the test does not appear in the queue [07:39] since it is already in progress [07:39] how did you requeue it? [07:39] I'm doing: retry-autopkgtest-regressions --all-proposed --state=RUNNING |grep cmake | xargs -rn1 -P10 curl --cookie ~/.cache/autopkgtest.cookie -o /dev/null --silent --head --write-out '%{url_effective} : %{http_code}\n' [07:40] How are we looking? Did anyone find any real issues with the new glibc? [07:40] sil2100: I called it at 'q' and hinted glibc [07:40] I see a skiptest \o/ [07:40] vorlon: similar - just output chromium to a shell script [07:40] there are still reported regressed tests later in the alphabet visible in update_excuses if someone wanted to look at them [07:41] vorlon: btw. you mentioned there not being that much ubuntu7 tests but I disagree. When working from a to e maybe even half of the running/regressed tests had passes for ubuntu7 [07:41] Anyway, good that we're letting it through [07:42] sil2100: yeah there was some work later in the evening to try to identify which tests had no pass with either ubuntu7 or ubuntu8; but I noticed some things missing so didn't end up working from that list but visually checking in the browser [07:42] vpa1977: my attempts to queue these tests appear to be working [07:43] vorlon: I do not see alglib in the list of queued tests at https://autopkgtest.ubuntu.com/running [07:43] vpa1977: well my requeuing is still in progress maybe that's why [07:43] vorlon: ack. Sorry :( [07:44] I can at least confirm that the number of references to 'cmake/' is currently increasing :) [07:44] ah, here it is =) alglib {"all-proposed": "1", "requester": "vorlon", "submit-time": "2024-04-05 07:40:52", "triggers": ["cmake/3.28.3-1build6"], "uuid": "1f486378-9113-49ee-8e45-b7064453244e"} [07:47] update_excuses seems to have not updated for over three hours [07:48] andersson1234: I killed one in-progress run to let glibc through; and the current run is taking a strangely long time on deciding whether or not to remove particular individual binaries [07:48] I don't know what that's about really [07:54] sil2100: ok here's roughly what the path to an installable ubuntu-desktop looks like right now: https://paste.ubuntu.com/p/KWCmDcXRBB/ [07:54] note that I've just hinted at-spi2-core, cairo, librsvg, policykit-1 [07:55] looking now at gobject-introspection [07:56] I'll poke people on the first standup to also contribute and then I'll join you [07:57] hinting gobject-introspection [07:59] andersson1234, sil2100: fwiw I think we're at the point now that noble-updates is confusing britney and slowing it down unnecessarily wrt binary package removals. If someone wanted to patch britney to not look at -updates for the devel series, that would likely speed up subsequent runs today [08:00] vorlon: I can try looking o/ [08:00] looking at man-db [08:00] vorlon: fwiw, I regularly patch my retry script to look for dupes in the queues for RUNNING tests too, that's how I found the bug :D [08:00] aha [08:00] juliank: meanwhile, I've gone as far as retrying all the failed tests for all packages [08:01] Sounds alright [08:01] I leave it to you to work with Europe folks to sort out queuing of the non-seeded RUNNING tests [08:01] I'm not sure why we explicitly disable the dedup of running tests [08:02] hinting man-db because no I don't believe it regressed lintian or apparmor :P [08:02] sil2100: and hinting at-spi2-core should also unblock gnome-shell ftr [08:03] Ooh gnome-shell would be nice [08:04] eh. libplist3 means rebuilds against libplist-2.0-4, triggering now [08:05] looking at libgudev [08:05] hinting libgudev [08:06] looking at pygobject [08:07] Ok, standup over, foundations people should be popping up to help in a moment, looking at britney [08:07] hinting pygobject [08:08] libhandy-1 also unblocked by at-spi2-core [08:09] looking at webkit2gtk [08:09] hinting [08:10] looking at vte2.91 [08:10] already hinted and only blocked by at-spi2-core [08:11] yelp unblocked by at-spi2-core [08:11] vorlon: are we referring to https://paste.ubuntu.com/p/KWCmDcXRBB/ or is there another list? [08:11] pushkarnk: that's what I'm working off [08:12] thx [08:12] am confused by rfkill, I thought we already pushed util-linux through [08:13] ok I said I was hinting util-linux but seems missing from the hints repo, gar; hinting for real now [08:15] gnome-control-center is already a candidate but blocked by samba apparently regressing installability [08:16] could somebody look into this please ^ [08:17] sssd is related, hinting that to ignore noble-updates [08:18] hinting ubuntu-advantage-desktop-daemon [08:19] hinting shared-mime-info [08:20] afk for a bit and waiting for britney [08:21] fwiw llvm-toolchain-17 probably needs a force hint since riscv64 is still building [08:23] vorlon: ok, trying to wrap my head around britney code - where is the slowdown exactly so that I know where to start? Are we talking britney2 or britney1? [08:23] sil2100: I do not know [08:23] looking at samba [08:23] ...digging further then! [08:25] pushkrank: samba vs freedombox, I looked at armhf history, tests pass. [08:25] samba vs adsys, test retried. [08:26] samba is already skiptest hinted, the test results don't matter what matters is why it shows regressions in installability on https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_output.txt [08:26] ack [08:26] vorlon: ack [08:26] specifically, why does promoting it make libsmbclient and smbclient uninstallable [08:26] since these are from the same package [08:27] so, shouldn't that unblock gnome-control-center? [08:27] yes, once samba is actually migratable without increasing the uninstallable count which is what happens now [08:29] ok [08:29] ok [08:30] Ok, I think I found *something* in b1, just need to understand better if that's indeed what can disable -updates consideration [08:31] I: [2024-04-05T08:30:26+0000] - trying: glibc [08:31] progress [08:31] \o/ [08:32] I: [2024-04-05T08:31:16+0000] - accepted: glibc [08:32] I: [2024-04-05T08:31:16+0000] - ori: 4449+0: a-1308:a-433:a-1869:i-108:p-257:r-240:s-234 [08:32] I: [2024-04-05T08:31:16+0000] - pre: 2886+0: a-846:a-355:a-1127:i-9:p-187:r-186:s-176 [08:33] gnome-autoar seems to be blocked by libarchive, taking a look [08:34] ah cmake [08:35] [Errno 2] No such file or directory: '/run/amqp-status-collector/running.json' [08:35] autopkgtest died? [08:35] QA explained this issue yesterday on MM and should have deployed a fix for it [08:35] vpa1977: rabbitmq did. is that current? [08:36] andersson1234: ^ [08:36] vorlon: it was just restarted [08:36] k [08:36] afk [08:37] vorlon, FYI mpg123 needs a transition, I'm driving it [08:38] LocutusOfBorg: ack, thanks (had earlier backed out mpg123 to let the previous version migrate and unbreak amd64) [08:38] LocutusOfBorg: btw I saw a lot of node-* packages whose autopkgtests were dying with SIGABRT, is nodejs in -proposed in decent shape? [08:39] britney finishing now [08:43] ok, libarchive is hinted [08:44] so gnome-autoar should sail through [08:44] and perhaps gnome-shell-extension-desktop-icons-ng [08:45] libarchive is not hinted? [08:45] hmmm another case of me claiming I was hinting but failing! [08:45] hinting now [08:45] it is, you hinted it [08:46] (I meant I saw it in the IRC logs :) ) [08:46] pushkarnk: I *said* I hinted it but there was no hint in the hint repo, so thanks for pointing this out [08:47] pushkarnk: if I had actually committed it 8 hours ago you should've seen a line about this in update_excuses ;) [08:47] oh, right [08:50] should we also hint mutter to unblock gnome-shell? [08:52] mutter is blocked only by at-spi2-core which has been hinted [08:53] so it should now migrate at the next run? [08:53] yes [08:53] ok thanks [08:53] accountsservice is blocked by ayatana-indicator-session for which tests have recently passed [08:54] so that should hopefully unblock language-selector-common [08:56] grrr, why can't I push my bzr branch [08:57] can I see somewhere when will be the next britney run? [08:57] upils: it's triggered every 2 minutes, there's one running now [08:57] the completion time however is variable [08:57] I'm wondering if there isn't a britney running right now? [08:58] where can I check this? [08:58] vorlon, thanks [08:58] grrr, LP down? [09:04] Bots are resurrected! [09:05] Back to the grind everyone! ;) [09:06] sil2100: there a potential glibc regression, would you rather have me investigating it or focus on overall migration? [09:06] schopin: what do you mean by regression? [09:07] I'd prefer overall migration, but also depends on how big of a regression we talking right now [09:07] Dunno yet, glibc vs fastqtl filed by steve. Only on armhf though, so I think it can wait. [09:12] Everything that's seeded has a Task field :D [09:12] autopkgtest is back. [09:12] indeed when trying to install that version of coreutils I get error `coreutils breaks usrmerge (<< 39)` [09:13] I am looking at uninstallable packages, the list (Newly uninstallable packages in the target suite:) is empty. https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_output.txt [09:13] I wanted to do the /lib.usr-is-merged -> /.lib.usr-is-merged and so on renames for the diversions for merged-usr for the beta but frankly I did not get to it [09:15] Report for uninstallable release binaries is ready now: https://magenta.jak-linux.org/ubuntu-archive/distcheck/noble/release-binaries.txt [09:15] But surprisingly it only shows you libc6 [09:15] well perhaps unsurprisingly [09:16] So waiting for publisher run with the glibc published and it should get actionable insights hopefully [09:16] isn't glibc hinted in the current britney run? [09:16] It migrated yesa [09:16] Not published yet [09:16] BTW has someone checked that it's still running despite the LP issues? [09:16] looking at policy-kit1 vs colord [09:39] gnome-shell fails to install [09:39] vpa1977: ok, I'll try gnome-shell and go from there. [09:41] FWIW, if we do this again, stage old packages in -security instead of -updates so that the UEFI signing pipeline can still build signed artefacts :D [09:44] I think LP is back [09:46] people.canonical.com is back too [09:47] even mattermost is [09:47] b1 change pushed, -updates should be ignored by britney now (hopefully) [09:48] FWIW I haven't mentioned this yet, but I'd be interested in for 24.10 changing seeding to not add Task: field to dependencies of seeds, and only to explicitly seeded packages :) [09:49] * juliank is distracting a bit, sorry [09:49] sil2100: does that mean that future excuses reports will show the installability issues we're hunting for? [09:49] sil2100, and does that mean a new report is running? [09:50] juliank: I wouldn't get my hopes up on the actual resolution of the incident, it has flickered a couple of times already. [09:50] I'm checking right now, since previous britney run of course had timeout issues [09:50] Maybe best to just kill b2 and wait for a rerun [09:51] Yeah, it was hanged, killed and waiting for the next run [09:56] so right now the last missing piece of the puzzle to install ubuntu-desktop is gnome-shell, which should be unblocked at the next britney run, correct? [10:02] I did not check the status just yet, let me see [10:04] 24.10 action item: Move britney from cronjob to systemd timer [10:04] Then you can just restart britney2.service :D [10:04] Okay, high chances are that gnome-shell will migrate soonish indeed, I see it was blocked by at-spi2-core which was hinted [10:04] I was able to install gnome-shell/46.0-0ubuntu3.1 in a noble chroot. [10:05] ravikant_: \o/ without -proposed? [10:05] yes [10:05] it at least needs mutter from proposed [10:05] I do not have proposed enabled in apt sources. [10:06] which should be unblocked too due to the hint on at-spi2-core [10:06] ravikant_: so how did you install gnome-shell 46.0-0ubuntu3.1 which is in -proposed [10:06] so, what is next? [10:07] sil2100: apt install gnome-shell, and then verified version with dpkg -l|grep -i gnome-shell [10:08] And without -proposed enabled it pulled in 46.0-0ubuntu3.1 for you? [10:09] I may have done something wrong. This is the same chroot I use for sbuild noble-amd64. [10:09] I entered using schroot -c noble-amd64 -u root and simply ran apt update and apt install ... [10:11] ravikant_: we usually have -proposed enabled in our sbuild (since we want to stay close to the buildd configuration) [10:12] sorry, I am looking at apt logs, it did pull some things from -proposed. [10:12] let me disable -proposed and try again. [10:15] bdrung: added a debdiff in LP: #2060214 for the ftbfs you mentioned yesterday [10:15] -ubottu:#ubuntu-release- Launchpad bug 2060214 in mtd-utils (Ubuntu) "mtd-utils 1:2.1.6-1build1 FTBFS" [Undecided, Confirmed] https://launchpad.net/bugs/2060214 [10:18]