[00:27] hmm, can't set up a Noble sbuild it seems. "dpkg: dependency problems prevent configuration of perl: perl depends on perl-modules-5.38 (>= 5.38.2-3.2build2); however: Version of perl-modules-5.38 on system is 5.38.2-3." [00:27] I thought I saw something about this in here earlier but can't remember for sure. [00:27] Ubuntu Server 24.04 installed just fine, but the mk-sbuild step bombed out with that. [01:02] arraybolt3: yea, perl is sad. if you get into the chroot an `apt -f install` should sort it out. [01:04] awesome, thanks for confirming my fix worked :P [01:04] (I had just apt installed the exact version of perl-modules-5.38 it wanted and it seemed to work) === chris14_ is now known as chris14 [02:43] -queuebot:#ubuntu-release- New: accepted rust-wayland-cursor [armhf] (noble-proposed) [0.31.1-1] [02:43] -queuebot:#ubuntu-release- New: accepted rust-wayland-cursor [riscv64] (noble-proposed) [0.31.1-1] [02:43] -queuebot:#ubuntu-release- New: accepted rust-wayland-protocols [amd64] (noble-proposed) [0.31.0-1] [02:43] -queuebot:#ubuntu-release- New: accepted rust-wayland-protocols [armhf] (noble-proposed) [0.31.0-1] [02:43] -queuebot:#ubuntu-release- New: accepted rust-wayland-protocols [riscv64] (noble-proposed) [0.31.0-1] [02:43] -queuebot:#ubuntu-release- New: accepted rust-wayland-cursor [ppc64el] (noble-proposed) [0.31.1-1] [02:43] -queuebot:#ubuntu-release- New: accepted rust-wayland-protocols [arm64] (noble-proposed) [0.31.0-1] [02:43] -queuebot:#ubuntu-release- New: accepted rust-wayland-protocols [s390x] (noble-proposed) [0.31.0-1] [02:43] -queuebot:#ubuntu-release- New: accepted rust-wayland-cursor [s390x] (noble-proposed) [0.31.1-1] [02:43] -queuebot:#ubuntu-release- New: accepted rust-wayland-protocols [ppc64el] (noble-proposed) [0.31.0-1] [02:43] -queuebot:#ubuntu-release- New: accepted rust-wayland-cursor [amd64] (noble-proposed) [0.31.1-1] [02:43] -queuebot:#ubuntu-release- New: accepted rust-wayland-cursor [arm64] (noble-proposed) [0.31.1-1] [02:44] did anyone get images sorted out wrt imath? it looks like it's still in noble-updates right now [02:46] well, looks like Ubuntu Kylin built, but Ubuntu Studio and Ubuntu Cinnamon have not [02:49] doing no change rebuild against go 1.22 of google-guest-agent google-osconfig-agent ipp-usb ubuntu-report zsys for zhsj [02:55] https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/o/odin/20240408_014940_2585b@/log.gz so I discovered something strange, it failed to install libvtk9.0, but if I manually add libopenmpi3t64 to the test-depends it will work [02:55] Is this some form of apt solver issue? [05:44] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-535-server [amd64] (noble-proposed) [535.161.08-0ubuntu2] [05:44] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-535 [amd64] (noble-proposed) [535.171.04-0ubuntu2] [05:44] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-535-server [arm64] (noble-proposed) [535.161.08-0ubuntu2] [05:44] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-535 [arm64] (noble-proposed) [535.171.04-0ubuntu2] [06:40] vorlon, some i386 missing builds are: gkrellm-volume, abx avrp betaradio blktool blktrace bluez-btsco bro-aux care cbatticon cdcd ciopfs clamz connman-ui cutmp3 daemonlogger dares devilspie [06:42] dhcp-probe dnstop dvblast dynamips esniper fizmo-sdl2 fprobe gperiodic gphotofs gromit gst-plugins-espeak gtk-theme-switch gv gwaterfall gworldclock indicator-multiload ippsample [06:43] ipwatchd kbdd komi kubuntu-debug-installer lazy-object-proxy lcas-lcmaps-gt4-interface lcmaps-plugins-voms libdumb libee libibtk lie lltdscan lrzsz [06:45] lyskom-server madwimax matanza memstat metar moserial mspdebug multiwatch nstreams nuntius-linux obexfs [07:07] hello SRU team :), please take a look at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2058687 [07:07] -ubottu:#ubuntu-release- Launchpad bug 2058687 in libreoffice (Ubuntu Mantic) "[SRU] libreoffice 7.6.6 for mantic" [Medium, In Progress] [07:10] vorlon, I suspect the copy to updates bringed back lots of ppc64el and i386 binaries that were removed from release pocket [07:10] https://paste.ubuntu.com/p/ZNcCvyGBHt/ [07:10] this is an incomplete list of stuff that will migrate if we clean it up again, but I don't know how to double check [07:21] oh lol ubuntu-archive: pyobjcryst was removed from noble, but restored in noble-updates only [07:21] this is holding few transitions to finish [07:22] or maybe just boost to migrate, but hey [07:26] also spek needs kick out on armhf [07:30] morning [07:31] if there is an archive admin around the two syncs for python-* packages in the unapproved queue for noble will unblock the cloudkitty built, which in turn will unblock the failing autopkgtests for this package [07:31] if they could be accepted that would be great - thx! [07:32] and freezer-api needs rm'ing from noble (bug 2060205) - thats also failing autopkgtests and have been removed in debian [07:32] -ubottu:#ubuntu-release- Bug 2060205 in freezer-api (Ubuntu) "RM freezer-api" [Undecided, New] https://launchpad.net/bugs/2060205 [07:52] https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/o/odin/20240408_014940_2585b@/log.gz so I discovered something strange, it failed to install libvtk9.0, but if I manually add libopenmpi3t64 to the test-depends it will work [07:53] I think this might need some Breaks against pre-t64 libraries whacked in somewhere [07:54] Presumably libopenmpi3 wants a Breaks: libevent-pthreads-2.1-7 (<< t64 version) [07:55] Not sure why it's broken in the first place though on amd64 [07:56] Ah libopenmpi3 also got renamed [07:56] Anywhere somewhere further up the chain we need a rebuild and a couple of Breaks added certainly can't hurt [07:58] hi LocutusOfBorg - I see the pyobjcryst you mention but have not yet learned the secret incantation to handle this case (-updates is immutable). Once sil2100 is around this might be a great chance to teach me to I can help on such cases as well. [07:58] until then let me look at the cases of jamespage - starting on the rm bug [07:59] thanks cpaelzer [07:59] I'm also looking at the manila test failures - looks like an compatiblity with newer alembic that should be fixable [08:12] LocutusOfBorg, cpaelzer: boost1.83 already has a hint to ignore the pyobjcryst regression, but boost1.83 is still blocked by openmpi [08:19] thanks ginggs [08:19] jamespage: I checked the removal, it is ok and done [08:20] jamespage: what exactly are the python-* packages in the unapproved queue for noble to unblock cloudkitty? [08:20] jamespage: I see python-influxdb-client and python-reactivex [08:21] cpaelzer: yep those 2 - cloudkitty -> influxdb -> reactivex [08:22] ok, having a look ... [08:27] -queuebot:#ubuntu-release- New sync: liquidsoap (noble-proposed/primary) [2.2.4-1] [08:28] ginggs, openmpi should go in next run [08:28] cpaelzer, thanks! this brings a question to release people, shouldn't we do a NCR every time we kick out an i386 binary? [08:28] this way we have a new LP entry and we don't risk this kind of mismatches [08:33] LocutusOfBorg: You mean NCRs to any rev-b-deps (to pick up most you could think of) or just to the pkg that no more builds the i386 binary (to have an entry there)? [08:33] LocutusOfBorg: in case of the latter that would even serve as a nice place to hold a "here we dropped i386 binaries" message [08:35] LocutusOfBorg: I didn't think into the problem enough to make a good call. And generally hesitate to add more builds (and the triggered tests) right now. But it might be worth to think about that as a good habit going forward [08:36] jamespage: if this would not add support for an older version and not already be covered by influxdb3-python this check would be easier :-) Still reading details ... [08:45] Looking at https://magenta.jak-linux.org/ubuntu-archive/distcheck/noble/release-binaries.txt [08:45] We have 2169 broken packages in noble amd64 release [08:45] Biggest blockers are unbound and llvm-defaults [08:46] Then libopenmpi3t64 [08:46] the latter [08:46] mkukri: if you're looking for something to do on +1 this week ^ [08:46] in terms of package sizes [08:46] * counts [08:47] cpaelzer, also because many times you still see the i386 binary on launchpad package page, but the package is not anymore in devel release [08:47] look e.g. https://launchpad.net/ubuntu/+source/ocaml/4.14.1-1ubuntu1 [08:47] i was looking at update excuses so far [08:47] libunbound8 breaks kubuntu and ubuntustudio [08:47] Noble: [FULLYBUILT] amd64 [FULLYBUILT] arm64 [FULLYBUILT] armhf [FULLYBUILT] i386 [FULLYBUILT] ppc64el [FULLYBUILT] riscv64 [FULLYBUILT] s390x [08:47] but i386 ocaml was dropped months ago [08:47] I find it confusing [08:47] mkukri: well, sure, I'm just suggesting you start by working on migrating those packages ;) [08:48] (but hey! I'm not really asking more rebuilds now!) [08:48] I finished haskell foobar rebuilds, and it migrated [08:48] I'm moving and doing ocaml now [08:50] schopin: suggestion taken :) [08:50] i assume someone is already looking at unbound given it is top of the list? [08:51] Not sure? [08:51] jamespage: python-reactivex is a general yes, but still a no due to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066895 [08:51] -ubottu:#ubuntu-release- Debian bug 1066895 in python3-reactivex "python-reactivex: duplicate of src:python-rx" [Serious, Open] [08:52] i guess ill look at it than [08:52] jamespage: would you mind uploading python-influxdb-client with a delta depending on python3-rx instead of python3-reactivex ? [08:52] https://magenta.jak-linux.org/ubuntu-archive/distcheck/noble/release-binaries.txt now has a summary [08:52] * 235 packages depending on src:unbound [08:52] * 179 packages depending on src:llvm-defaults [08:52] * 152 packages depending on libopenmpi3 [08:52] * 110 packages depending on libopencv-core406 [08:52] It lies a bit, some of those packages may be tasks [08:56] why is spooles showing missing builds on i386? the i386 packages in noble-release are removed [08:57] doko, -updates pocket [08:57] see backlog [08:57] We should have a daily freeze and cleanup updates [08:58] jamespage: if you do not not, I have it ready and test built to act (1 reject, 1 upload, 1 accept) [08:58] jamespage: just tell me to make it happen [08:58] unbound seems to be blocked by ovn autopkgtest. which looks like it wants bzip2 from proposed [08:59] cpaelzer: bah I missed that bug - apologies [08:59] I'll sort that out now with a delta ontop of the synced version [08:59] jamespage: np, just tell me if you are ok with that approach [08:59] cpaelzer: completely [08:59] jamespage: as I said, I already have that delta and test built [08:59] jamespage: I mostly want to hear a yes, do it that way [08:59] I guess zigo just missed the existence of the package and repakaged it! [08:59] cpaelzer: yes please :) [09:00] ok jamespage - the only follow up later is once zigo changed it in some way to ensure things follow accordingly in 24.10 and later [09:00] thanks for the help :) [09:01] -queuebot:#ubuntu-release- New: rejected python-reactivex [sync] (noble-proposed) [4.0.4-1] [09:02] looking at ossp-uuid [09:02] (while ovn test is running) [09:02] -queuebot:#ubuntu-release- New: rejected python-influxdb-client [sync] (noble-proposed) [1.40.0-1] [09:02] looking at opencv/vtk9 [09:02] openmpi should be good [09:03] Looking at src:openvswitch [09:05] -queuebot:#ubuntu-release- New source: python-influxdb-client (noble-proposed/primary) [1.40.0-1ubuntu1] [09:07] -queuebot:#ubuntu-release- New: accepted python-influxdb-client [source] (noble-proposed) [1.40.0-1ubuntu1] [09:08] how to fix packages still depending on perlapi-5.36.0? [09:10] mkukri: which packages, which pocket? [09:10] -queuebot:#ubuntu-release- New binary: python-influxdb-client [amd64] (noble-proposed/none) [1.40.0-1ubuntu1] (no packageset) [09:10] i think this is a case of the rebuild against perl 5.38 not migrating [09:10] libdata-uuid-libuuid-perl it is, but it seems like fix is in proposed, so i am looking at the blockers now [09:11] -queuebot:#ubuntu-release- New: accepted python-influxdb-client [amd64] (noble-proposed) [1.40.0-1ubuntu1] [09:12] jamespage: fully through now [09:13] hmm im not sure why libdata-uuid-libuuid-perl is uninstallable on armhf [09:13] waveform: thanks for checking the pemmican implications with me, resolving that now ... [09:18] cpaelzer: thanks [09:19] cpaelzer, no problem! [09:19] waveform: MR merged and bug updated with step #1 [09:21] same deal for libdata-swap-perl as libdata-uuid-libuuid-perl [09:23] apparently perl itself is uninstallable on armhf somehow? [09:23] even tho it is in -release? [09:23] waveform: the team bug subscription isn't yet set - do you have anyone around that can add that? [09:23] i also get perl uninistallability errors when trying to deboostrap an armhf chroot [09:24] mkukri, it was hinted by silil2100 "force-badtest perl/5.38.2-3.2/armhf" [09:24] maybe then we missed something? [09:25] *sil2100 [09:26] cpaelzer, yes -- I'll do that now [09:27] done [09:28] it is specifically perl-modules-5.38 binary that seems to be the problem [09:31] perl depends on perl-modules-5.38 (>= 5.38.2-3.2build2); however: Version of perl-modules-5.38 on system is 5.38.2-3. where is the old perl-modules coming from? [09:31] rmadison also says both versions exist in noble for some reason [09:35] perl-modules-5.38 = 5.38.2-3 is not published according to launchpad but it is somehow getting installed? [09:37] and i also get the same error on amd64? something seems broken [09:38] looking through the download log, all the other perl binaries seems to be the correct version, but it is pulling the old perl-modules-5.38 for some reason [09:51] Could someone with enough permission retry this build https://launchpad.net/ubuntu/+source/openvswitch/3.3.0-1build2/+build/28008804 please? [09:52] Loking at sendmail [09:52] can someone with a better understanding of the archive provide some insight on the perl situation? the following output seems very weird: [09:52] I: Retrieving perl 5.38.2-3.2build2 [09:52] I: Validating perl 5.38.2-3.2build2 [09:52] I: Retrieving perl-base 5.38.2-3.2build2 [09:52] I: Validating perl-base 5.38.2-3.2build2 [09:52] I: Retrieving perl-modules-5.38 5.38.2-3 [09:52] I: Validating perl-modules-5.38 5.38.2-3 [09:54] o/ [09:54] Let me try freezing the noble archive just for a moment to do a quick removal [09:58] sil2100: I have ruby3.1 to be removed as well, which isn't possible as long as not frozen - could you or me remove that as well while you freeze shortly? [10:02] ovn autopkgtest passed, unbound should be unblocked soon [10:09] Could someone with enough permission also retry this armhf build https://launchpad.net/ubuntu/+source/sendmail/8.18.1-1build3/+build/27994669please? [10:11] looking at astrometry.net meanwhile [10:12] upils: done [10:13] just went over https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-impfuncdef;users=lucas@debian.org and synced ~140 package to fix ftbfs [10:13] thanks waveform, done [10:13] doko, thanks, can you also do this one I requested earlier https://launchpad.net/ubuntu/+source/openvswitch/3.3.0-1build2/+build/28008804 please? [10:16] Ok, imath removed [10:16] cpaelzer: aaaa [10:18] cpaelzer: missed your message, sorry about that. Is it needed right now to unblock some builds, or can this wait when we're official in Beta freeze? [10:21] sil2100: it can wait [10:21] sil2100: I just wanted to use the chance when frozen anyway [10:22] sil2100: I can just as much keep my reminder open and act once we are there [10:29] upils: done. also synced https://launchpad.net/ubuntu/+source/sendmail/8.18.1-2 [10:31] Thanks. Ok, thanks. Then I will for it to be synced and build to check if the armhf build failure persist [10:35] upils: it's always good to have a look at newer Debian uploads before investing time into a build failure [10:38] I'm syncing debian NMUs for time64_t armhf build fixes [10:50] fix uploaded for alembic compat for manila - I think that should sort out the last few autopkgtest failures blocking stuff in the ubuntu-openstack package set [10:57] sil2100: next time you freeze, please remove the spooles i386 binaries, blocking openmpi [10:57] doko: is that the only thing blocking openmpi? Maybe we can just force hint it into then [10:58] Uploading langpacks for Beta [11:02] sil2100: no, still walking through packages with missing builds [11:14] Rebuilding cinnamon and studio [11:32] Oh no, LP died [11:33] Sad, because it looked like the cinnamon and studio livefses seemed to have been building correctly up to this point [11:34] need to insert 50p into the launchpad meter to make it work again... [11:36] is launchpad dying a "we're all doomed!" situation or a "someone give it a kick" situation? [11:44] Nah, just a normal outage, nothing to worry about [11:44] The right people are on it right now [11:46] nice [12:01] arraybolt3: there are still unity related ftbfs, like hud, indicator-* [12:18] am looking at c2esp [12:20] I found that sendmail is part of the auto-db5.3 transition. Should I set it aside for now then? [12:21] also the old perl-modules being installed is still an issue [12:31] also looking at tree proposed migration [12:38] pul-lp-source is timeouting 503ing after really long timeouts currently [12:44] there was a lp outage just a few moments ago [12:44] sil2100: ubuntucinnamon built! yay :) https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntucinnamon/+build/602282 ... just the LP issues causing the built ISO to be transferred properly. [12:44] not to be transferred... [12:47] jamespage: openvswitch ftbfs on arm64 (test failure) [12:47] sil2100, sendmail/8.18.1-1build3 is now replaced with sendmail/8.18.1-2 (sync). Should we update the force-skiptest hint? [12:50] fnordahl: have you got https://launchpad.net/ubuntu/+source/openvswitch/3.3.0-1build2/+build/28008804 on your todo list? [12:51] jamespage: yes, looking at that atm [12:51] fnordahl: great thanks :) [12:52] the arm64 machines are quite loaded due to other release stuff, so it takes some time, the build failure reproduced over lunch so will hopefully have it patched soon [12:52] oh, I was also looking at it. I may have missed when it was taken. [12:54] upils: was that a comment for the openvswitch arm64 build failure or something else? I might have forgotten to switch bug status O8-) How far were you along if that was the case? [12:56] yes it was about openvswitch. Well I requested before launch a retry to make sure it was still broken and I was trying to understand what went wrong. So you can go ahead [12:56] ack, thx upils [12:57] *lunch [12:58] upils: re sendmail I wouldn't blindly change the hint since it's not a NCR. [13:04] schopin, good point. I guess I will wait for the next britney run to see if it migrates. If it does, then I can request for the hint to be removed or will we clean every xz-related hint at once when we are done? [13:04] I think we'll clean all hints afterwards. [13:05] ok, cool [13:11] * mkukri is looking at bash [13:13] sil2100: I think I addressed all openmpi depending packages, either by removing, or fixing issues [13:15] Ubuntu Cinnamon built successfully \o/ [13:15] Now doing the same for studio [13:16] doko: checking, we can hint it in then if -updates is confusing britney [13:22] sil2100: still needs some publisher runs [13:22] hm, and I noticed I lost some of my cdimage commits, guess I again forgot a git push [13:41] is faketime expected to be broken on armhf? [13:41] and should i be trying to do anything about that? [13:43] mkukri: yes, no (I think) [13:44] mkukri: I think you could fix it but it's low priority [13:44] and mid-to-high complexity [13:44] it's blocking bash migration (indirectly) [13:46] Is it blocking because its tests are broken? In which case a baseline test should be enough. [13:46] Studio also successfully built \o/ [13:47] \o/ [13:47] vorlon: I think the last one is the x13s, checking the logs [13:47] it's blocking because dkim-rotate autopkgtest seems to be broken by faketime [13:47] and dkim-rotate is blocking bash [13:50] So, yes, faketime is broken, but the fix is pretty involved: you need to modify it to 1/ dlsym() the t64 symbols from glibc on armhf rather than the standard ones and 2/ export those symbols rather than the standard ones, but only on armhf. [13:50] And there are a *lot* of symbols. [13:51] i am not sure if that is something i want to do as part of +1 [13:52] what about hintign dkim-rotate test, or removing it on armhf? [13:53] mkukri: you can't remove it, it's arch:all. [13:54] LocutusOfBorg: please could you track your ftbfs at this stage? https://launchpad.net/ubuntu/+source/ferret-vis/7.6.0-7ubuntu1 [13:55] ah i see yes. it seems plausible tho that only its tests need faketime. so maybe hinting it is better? [13:55] mkukri: but isn't the baseline also broken? [13:57] maybe the migration-reference/0 test is out of date? [13:57] i can't re-trigger it tho 'You submitted an invalid request: You are not allowed to upload dkim-rotate or migration-reference/0 to Ubuntu, thus you are not allowed to use this service.' didnt see one of these before [13:58] doko, I am [13:58] I have like 60 tabs opened and I'll track them all [13:59] btw, I'm syncing stuff that is already FTBFS on armhf, so there should be no risk of regressions [13:59] qa-help: please see mkukri's msg above as of 2mn ago [13:59] where can I see if we decided not to build a given package for i386? (at looked on LP, in hints-ubuntu)? I would like to understand why the version of uw-imap in proposed was not built for i386. See https://launchpad.net/ubuntu/+source/uw-imap [14:00] (*I looked) [14:00] fwiw; there are some subtle differences between python3.12.2-4ubuntuX and python3.12.2-5ubuntuX which causes the build failure for openvswitch bug 2060434 [14:00] -ubottu:#ubuntu-release- Bug 2060434 in openvswitch (Ubuntu) "[noble] FTBFS on failure in test vlog - Python3, change of behavior between Python 3.11 and 3.12" [Undecided, In Progress] https://launchpad.net/bugs/2060434 [14:00] we'll patch it, but worth highlihgting as this was an unexpected change to me [14:03] andersson1234, ^^ can that be related to the charm update? [14:04] when did that happen? i could trigger tests this morning [14:04] didnt try any migration-reference/0s before this tho [14:05] (that is not today, it worked in the past) [14:05] LocutusOfBorg: are you fixing ferret-vis? the armhf ftbfs is blocking openmpi [14:06] mkukri: meanwhile what's the link? :) [14:06] (in a meeting but I can still click things) [14:06] https://autopkgtest.ubuntu.com/request.cgi?release=noble&arch=armhf&package=dkim-rotate&trigger=migration-reference/0 [14:07] done [14:07] thanks [14:11] doko, not yet [14:11] but it built [14:11] so yes its fixed [14:11] fix was in syncing of xgks 2.6.1+dfsg.2-15 [14:11] but slow LP was slow [14:17] dkim-rotate migration-reference/0 also failed now, so i guess that means bash migrating? [14:17] it it was the last holdout, yes. [14:17] it looks like it yes [14:40] -queuebot:#ubuntu-release- New: accepted lxml-html-clean [source] (noble-proposed) [0.1.0-0ubuntu1] [14:42] -queuebot:#ubuntu-release- New binary: lxml-html-clean [amd64] (noble-proposed/none) [0.1.0-0ubuntu1] (no packageset) [14:45] Doing 211 no-change rebuilds for time_t on amd64 [14:47] This will improve solver reliability [14:54] vorlon: ubuntu-sru: I'd like to ask for a blanket SRU exception for 24.04 until 24.04.1 or so for no-change uploads without SRU bugs [14:57] doko, vorlon do we now when the gcc was published for time_t transition? I'm trying to write a report to see which packages haven't been rebuilt for time_t and frame pointers [14:57] * know [14:57] 211 uploads done [14:58] -queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (focal-proposed) [24.1.3-0ubuntu1~20.04.1] [14:58] -queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (jammy-proposed) [24.1.3-0ubuntu1~22.04.1] [14:58] -queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (mantic-proposed) [24.1.3-0ubuntu1~23.10.1] [15:01] I have identified 88 source packages with binaries on armhf that still use old library names [15:02] * stunnel4 depends on conflicting packages: libssl3t64=3.0.13-0ubuntu3 vs libssl3=3.0.10-1ubuntu4 [15:02] - chain 2: libssl3:armhf (>= 3.0.0) [15:02] This doesn't look nice [15:03] Ah this still needs to migrate [15:04] It's funny how some packages are recurring pains. [15:05] stunnel4 just didn't migrate yet [15:06] I'll go do the (unseeded) armhf uploads too, after all that shouldn't block anything and it makes britney sadder perhaps :) [15:06] vorlon we have other packages not supporting yet ruby-rack 3.x, so we should keep thos packages just in -proposed for now. I filed some bugs to upstream projects but not all of them fixed the issues yet [15:08] Note I miss anything that is already in proposed [15:08] Which is good for not blocking in-progress stuff [15:08] stunnel4 should be a priority due to being an apt test depends [15:09] I really want to keep/get the armhf apt tests working in noble release pocket [15:10] -queuebot:#ubuntu-release- New: accepted lxml-html-clean [amd64] (noble-proposed) [0.1.0-0ubuntu1] [15:12] sil2100: o/ I see you mentioned ubuntu-cdimage, and I'm actually working on an MP for Lubuntu right now. :) [15:12] Would you be interested in reviewing? [15:18] juliank: https://launchpad.net/ubuntu/+source/gcc-13/13.2.0-16ubuntu1 [15:18] ubuntu-release: Feel free to discuss with me here or on the MP: https://code.launchpad.net/~lubuntu-dev/ubuntu-cdimage/+git/ubuntu-cdimage/+merge/463825 [15:23] doko: Not really helpful [15:23] Superseded on 2024-02-29 by armhf build of gcc-13 13.2.0-16ubuntu1 in ubuntu noble RELEASE [15:23] hmm [15:24] I guess just taking 1st of April is fine [15:24] 2024-02-29 23:44:37 CET ~ 22:44 [15:29] Can someone retry the 4 failing builds for https://launchpad.net/ubuntu/+source/astrometry.net/0.93+dfsg-1.1build3 please? I retried the arm64 one locally and it worked fine. [15:30] upils: I retriggered the arm64 one, if it passes I'll retrigger the others [15:32] thanks, good call! [15:37] schopin, bdrung, sil2100, vorlon: https://magenta.jak-linux.org/ubuntu-archive/distcheck/noble/missing-rebuilds.txt now contains packages not rebuilt since the start of the t64 transition [15:37] # main: 1372 old packages [15:37] # restricted: 5 old packages [15:37] # universe: 27443 old packages [15:37] # multiverse: 411 old packages [15:38] bdmurray, vorlon, I would be *very* interested in checking why rust-sequoia-wot got pulled from -proposed, but it migrated in the meantime, so I can't easily try to reproduce the issue and follow what's happening there. [15:38] bdmurray, vorlon, if you spot something similar again please raise it with me [15:38] Counts include packages that have a newer version in proposed [15:38] juliank: how many package do we have in the archive? 27k untouched packages seems rather big. [15:39] $ grep ^Package root/var/lib/apt/lists/snapshot.ubuntu.com_ubuntu_dists_noble_*_source_Sources | wc -l [15:39] 74818 [15:39] schopin: ^ [15:40] 75k packages total, about 29k missing builds [15:40] So we rebuilt about 60% [15:40] Huh. That's a lot of packages... [15:40] schopin: Oops bug [15:40] I forgot a : [15:41] grep ^Package: root/var/lib/apt/lists/snapshot.ubuntu.com_ubuntu_dists_noble_*_source_Sources | wc -l [15:41] 37422 [15:41] Ah. That's more like it. [15:41] So yeah we rebuild barely ~21% [15:41] *rebuilt [15:42] Sure but we can filter out quite a bit. [15:42] Many a Perl, Go, or Rust [15:42] Indeed. [15:42] Let me filter out packages only building Architecture: all [15:43] much better [15:43] You'll still get the Rust packages though, because their -dev are arch:any for some reason related to apt solver. [15:43] # main: 465 old packages [15:43] # restricted: 5 old packages [15:43] # universe: 9750 old packages [15:43] # multiverse: 152 old packages [15:44] sil2100: can you remove the "xz-utils worklist" note from the topic? Those logs are offline right now, that list of seeded packages is no longer the focus. [15:44] Ah! Yes [15:44] On it [15:44] thanks === sil2100 changed the topic of #ubuntu-release to: Released: 23.10 Mantic Minotaur, 22.04.4 Jammy Jellyfish | Archive: Feature Freeze | Beta Freeze delayed till 8th of April | Highlight ubuntu-archive for archive admin help | We accept payment in cash, cheque or scotch | melius malum quod cognoscis | infinity, you are missed [15:45] I can filter out src:rust-* src:golang-* src:haskell-* [15:45] src:r-cran-* [15:45] ? [15:45] Also I guess those that are not actually for armhf [15:46] But then we lose frame pointer information for amd64 [15:47] # main: 465 old packages [15:47] # restricted: 5 old packages [15:47] # universe: 6408 old packages [15:47] # multiverse: 152 old packages [15:49] juliank, upload no-change rebuilds for those now? [15:49] Do we want to issue additional 465 (minus ones in proposed) rebuilds for main to make sure all of main has frame pointers? [15:49] I need to wait for my previous round to be processed to get a new report without them I suppose [15:49] 465 doesn't sound too bad to not do it. [15:50] yeah I wonder about universe though [15:50] 453 without newer version in proposed [15:51] Let's see how many rebuilds it is if we ignore the ones I just did [15:55] Uploading [15:55] "No change rebuild for 64-bit time_t and frame pointers." [15:56] Could check seeded packages in universe but annoying hackery [15:56] Well slightly annoying [15:57] Seriously need to integrate all tooling [15:59] I think cpio probably was a good idea: https://launchpad.net/ubuntu/+source/cpio/2.15+dfsg-1ubuntu2 [15:59] I mean that would get funny timestamps [16:00] Ah shoot, doko I uploaded gcc-defaults no-change rebuild but that's a bit pointless [16:00] please remove that :D [16:00] My script could have checked maybe if we actually have ELF binaries in the binary packages to avoid uploading meta packages [16:01] Running all the signing operations via the yubikey (without tap to sign turned off temporarily) takes a long time [16:02] It can sign one file at a time and each file takes like 500ms or so [16:02] each upload has 3 files [16:02] so 1.5s for signing each upload [16:03] so ~10 minutes to upload everything [16:04] the on-disk format for cpio uses 8 bytes for a hex representation. so you could store 4 bytes aka 32 bit in it. so the on-disk format is still affected by the year 2038 bug [16:04] oof [16:04] hopefully it is unsigned [16:05] then it wouldn't be affected [16:07] *NOT* touching anything already in proposed (again) [16:08] Who volunteers to run an armhf system set to 2040? [16:08] should be unsigned. so it will be hit by the year 2106 bug. i hope i retire before that date. [16:08] I guess just do 2044 so you can remember the 20 year offset [16:08] then you can make sure everything works :D [16:09] i have a zero 2 that i can use for this kind of test [16:10] mtd-utils needs to be fixed to get it updated [16:10] -queuebot:#ubuntu-release- Unapproved: fwupd-efi (noble-proposed/main) [1:1.4-1 => 1:1.4-1build1] (no packageset) [16:10] I expect anything that has a newer version in proposed to get picked up by people working on other reports [16:11] Oh please reject fwupd-efi [16:11] Oh ubuntu-archive please reject fwupd-efi [16:11] (and remove gcc-defaults from proposed) [16:11] busybox FTBFS on arm* [16:12] /<>/networking/tc.c:237:27: error: ‘TCA_CBQ_MAX’ undeclared (first use in this function); did you mean ‘TCA_CBS_MAX’? [16:12] fun [16:12] bunch more similar ones [16:12] bdrung: icu ftbfs [16:12] but with python3-distutils : Depends: python3-lib2to3 (= 3.12.2-3ubuntu1.1) but it is not going to be installed [16:12] this is weird [16:13] python3-distutils was dropped [16:13] we need to get rid of that one [16:13] Ah yes [16:13] bdrung: I'll graciously say that's something for you to look at :) [16:14] but maybe someone else already is, idk? [16:14] i can work on the icu failure, but first let me take a bike break before it gets cold and dark [16:14] We had python3-distutils reverse-build-depends fixup report, no? [16:14] bdrung: Go bike your brains out [16:14] see you later [16:20] Uploading all the fan favorites today; cpio, , schroot, screen [16:21] Regarding the blanket SRU exception: It just makes sense, then we can keep the no-change uploads in proposed right where they are and release them once they look good [16:22] ooh valgrind I'm uploading too, i did not know [16:24] It's amazing how many packages haven't been rebuild since the ppc64el baseline bump in jammy [16:24] -queuebot:#ubuntu-release- Unapproved: servicelog (noble-proposed/main) [1.1.16-1 => 1.1.16-1build1] (core) [16:24] -queuebot:#ubuntu-release- Unapproved: shadow (noble-proposed/main) [1:4.13+dfsg1-4ubuntu1 => 1:4.13+dfsg1-4ubuntu2] (core, i386-whitelist) [16:24] -queuebot:#ubuntu-release- Unapproved: skiboot (noble-proposed/main) [7.0+dfsg-1build1 => 7.0+dfsg-1build2] (core) [16:24] -queuebot:#ubuntu-release- Unapproved: sg3-utils (noble-proposed/main) [1.46-3ubuntu3 => 1.46-3ubuntu4] (core) [16:24] -queuebot:#ubuntu-release- Unapproved: simplejson (noble-proposed/main) [3.19.2-1build1 => 3.19.2-1build2] (no packageset) [16:25] -queuebot:#ubuntu-release- Unapproved: smartmontools (noble-proposed/main) [7.4-2 => 7.4-2build1] (kubuntu) [16:25] -queuebot:#ubuntu-release- Unapproved: snowball (noble-proposed/main) [2.2.0-4 => 2.2.0-4build1] (core, i386-whitelist) [16:25] -queuebot:#ubuntu-release- Unapproved: sosreport (noble-proposed/main) [4.5.6-0ubuntu2 => 4.5.6-0ubuntu3] (ubuntu-desktop, ubuntu-server) [16:25] -queuebot:#ubuntu-release- Unapproved: sqlalchemy (noble-proposed/main) [1.4.50+ds1-1 => 1.4.50+ds1-1build1] (ubuntu-budgie) [16:25] -queuebot:#ubuntu-release- Unapproved: startup-notification (noble-proposed/main) [0.12-6build2 => 0.12-6build3] (desktop-core, i386-whitelist) [16:25] -queuebot:#ubuntu-release- Unapproved: swedish (noble-proposed/main) [1.4.5-3 => 1.4.5-3build1] (ubuntu-desktop) [16:25] -queuebot:#ubuntu-release- Unapproved: sysfsutils (noble-proposed/main) [2.1.1-6 => 2.1.1-6build1] (core, i386-whitelist) [16:25] -queuebot:#ubuntu-release- Unapproved: sysstat (noble-proposed/main) [12.6.1-1ubuntu1 => 12.6.1-1ubuntu2] (ubuntu-server) [16:25] -queuebot:#ubuntu-release- Unapproved: tar (noble-proposed/main) [1.35+dfsg-3 => 1.35+dfsg-3build1] (core, i386-whitelist) [16:25] -queuebot:#ubuntu-release- Unapproved: tidy-html5 (noble-proposed/main) [2:5.6.0-11ubuntu1 => 2:5.6.0-11ubuntu2] (ubuntu-server) [16:25] Oh did someone turn on freeze during this batch of uploads, huh [16:25] -queuebot:#ubuntu-release- Unapproved: snappy (noble-proposed/main) [1.1.10-1 => 1.1.10-1build1] (core, i386-whitelist) [16:25] -queuebot:#ubuntu-release- Unapproved: speex (noble-proposed/main) [1.2.1-2ubuntu1 => 1.2.1-2ubuntu2] (desktop-core, i386-whitelist, ubuntu-server) [16:25] -queuebot:#ubuntu-release- Unapproved: strace (noble-proposed/main) [6.6-0ubuntu1 => 6.6-0ubuntu2] (core, i386-whitelist) [16:25] -queuebot:#ubuntu-release- Unapproved: syslinux (noble-proposed/main) [3:6.04~git20190206.bf6db5b4+dfsg1-3ubuntu2 => 3:6.04~git20190206.bf6db5b4+dfsg1-3ubuntu3] (no packageset) [16:25] -queuebot:#ubuntu-release- Unapproved: tftp-hpa (noble-proposed/main) [5.2+20150808-1.4 => 5.2+20150808-1.4build1] (ubuntu-server) [16:25] -queuebot:#ubuntu-release- Unapproved: sonic (noble-proposed/main) [0.2.0-13 => 0.2.0-13build1] (i386-whitelist, ubuntu-desktop) [16:25] -queuebot:#ubuntu-release- Unapproved: sysconfig (noble-proposed/main) [0.0.14ubuntu2 => 0.0.14ubuntu3] (core) [16:25] -queuebot:#ubuntu-release- Unapproved: time (noble-proposed/main) [1.9-0.2 => 1.9-0.2build1] (core, i386-whitelist) [16:25] -queuebot:#ubuntu-release- Unapproved: squashfs-tools (noble-proposed/main) [1:4.6.1-1 => 1:4.6.1-1build1] (core, i386-whitelist) [16:25] -queuebot:#ubuntu-release- Unapproved: t1utils (noble-proposed/main) [1.41-4build2 => 1.41-4build3] (core, i386-whitelist) [16:25] -queuebot:#ubuntu-release- Unapproved: sysvinit (noble-proposed/main) [3.08-6ubuntu2 => 3.08-6ubuntu3] (core, i386-whitelist) [16:25] -queuebot:#ubuntu-release- Unapproved: tdb (noble-proposed/main) [1.4.10-1 => 1.4.10-1build1] (core, i386-whitelist) [16:25] -queuebot:#ubuntu-release- Unapproved: twolame (noble-proposed/main) [0.4.0-2build2 => 0.4.0-2build3] (desktop-core, i386-whitelist, ubuntu-server) [16:25] -queuebot:#ubuntu-release- Unapproved: unzip (noble-proposed/main) [6.0-28ubuntu3 => 6.0-28ubuntu4] (core, i386-whitelist) [16:25] -queuebot:#ubuntu-release- Unapproved: usbutils (noble-proposed/main) [1:017-3 => 1:017-3build1] (core, i386-whitelist) [16:25] -queuebot:#ubuntu-release- Unapproved: vulkan-loader (noble-proposed/main) [1.3.275.0-1 => 1.3.275.0-1build1] (core, i386-whitelist) [16:25] -queuebot:#ubuntu-release- Unapproved: taglib (noble-proposed/main) [1.13.1-1 => 1.13.1-1build1] (desktop-core, i386-whitelist, ubuntu-server) [16:25] -queuebot:#ubuntu-release- Unapproved: uchardet (noble-proposed/main) [0.0.8-1 => 0.0.8-1build1] (core, i386-whitelist) [16:25] -queuebot:#ubuntu-release- Unapproved: voikko-fi (noble-proposed/main) [2.5-1 => 2.5-1build1] (ubuntu-desktop) [16:25] -queuebot:#ubuntu-release- Unapproved: tinycdb (noble-proposed/main) [0.81-1 => 0.81-1build1] (ubuntu-desktop, ubuntu-server) [16:25] -queuebot:#ubuntu-release- Unapproved: wdiff (noble-proposed/main) [1.2.2-6 => 1.2.2-6build1] (core, i386-whitelist) [16:25] -queuebot:#ubuntu-release- Unapproved: usb-modeswitch (noble-proposed/main) [2.6.1-3ubuntu2 => 2.6.1-3ubuntu3] (desktop-core) [16:26] wc -l rebuild-for.log [16:26] -queuebot:#ubuntu-release- Unapproved: uucp (noble-proposed/main) [1.07-28 => 1.07-28build1] (core) [16:26] -queuebot:#ubuntu-release- Unapproved: virglrenderer (noble-proposed/main) [1.0.0-1ubuntu1 => 1.0.0-1ubuntu2] (ubuntu-server) [16:26] 446 rebuild-for.log [16:26] -queuebot:#ubuntu-release- Unapproved: wayland (noble-proposed/main) [1.22.0-2.1 => 1.22.0-2.1build1] (core, i386-whitelist, xorg) [16:26] -queuebot:#ubuntu-release- Unapproved: websockify (noble-proposed/main) [0.10.0+dfsg1-5build1 => 0.10.0+dfsg1-5build2] (no packageset) [16:26] -queuebot:#ubuntu-release- Unapproved: valgrind (noble-proposed/main) [1:3.22.0-0ubuntu2 => 1:3.22.0-0ubuntu3] (i386-whitelist, ubuntu-desktop) [16:26] -queuebot:#ubuntu-release- Unapproved: webrtc-audio-processing (noble-proposed/main) [0.3.1-0ubuntu5 => 0.3.1-0ubuntu6] (desktop-core, i386-whitelist) [16:26] -queuebot:#ubuntu-release- Unapproved: wavpack (noble-proposed/main) [5.6.0-1 => 5.6.0-1build1] (desktop-core, i386-whitelist, ubuntu-server) [16:26] -queuebot:#ubuntu-release- Unapproved: wireguard (noble-proposed/main) [1.0.20210914-1ubuntu3 => 1.0.20210914-1ubuntu4] (no packageset) [16:26] -queuebot:#ubuntu-release- Unapproved: xauth (noble-proposed/main) [1:1.1.2-1 => 1:1.1.2-1build1] (core, i386-whitelist) [16:26] -queuebot:#ubuntu-release- Unapproved: xcb-util-keysyms (noble-proposed/main) [0.4.0-1build3 => 0.4.0-1build4] (desktop-core, i386-whitelist) [16:26] -queuebot:#ubuntu-release- Unapproved: xcb-util (noble-proposed/main) [0.4.0-1build2 => 0.4.0-1build3] (desktop-core, i386-whitelist) [16:26] -queuebot:#ubuntu-release- Unapproved: woff2 (noble-proposed/main) [1.0.2-2 => 1.0.2-2build1] (desktop-core, i386-whitelist) [16:26] -queuebot:#ubuntu-release- Unapproved: xcb-util-renderutil (noble-proposed/main) [0.3.9-1build3 => 0.3.9-1build4] (desktop-core, i386-whitelist) [16:26] -queuebot:#ubuntu-release- Unapproved: xcb-util-image (noble-proposed/main) [0.4.0-2 => 0.4.0-2build1] (desktop-core, i386-whitelist) [16:27] -queuebot:#ubuntu-release- Unapproved: fwupd-efi (noble-proposed/main) [1:1.4-1build1 => 1:1.4-1build1] (no packageset) [16:27] -queuebot:#ubuntu-release- Unapproved: xdg-user-dirs (noble-proposed/main) [0.18-1 => 0.18-1build1] (core) [16:27] -queuebot:#ubuntu-release- Unapproved: xfonts-utils (noble-proposed/main) [1:7.7+6build2 => 1:7.7+6build3] (desktop-core, i386-whitelist) [16:27] -queuebot:#ubuntu-release- Unapproved: xft (noble-proposed/main) [2.3.6-1 => 2.3.6-1build1] (core, i386-whitelist, xorg) [16:27] -queuebot:#ubuntu-release- Unapproved: xinput (noble-proposed/main) [1.6.4-1 => 1.6.4-1build1] (desktop-core) [16:27] -queuebot:#ubuntu-release- Unapproved: xserver-xorg-video-amdgpu (noble-proposed/main) [23.0.0-1 => 23.0.0-1build1] (desktop-core) [16:27] -queuebot:#ubuntu-release- Unapproved: xserver-xorg-video-dummy (noble-proposed/main) [1:0.4.0-1 => 1:0.4.0-1build1] (desktop-core, xorg) [16:27] -queuebot:#ubuntu-release- Unapproved: xserver-xorg-video-qxl (noble-proposed/main) [0.1.6-1 => 0.1.6-1build1] (desktop-core, xorg) [16:27] -queuebot:#ubuntu-release- Unapproved: xserver-xorg-video-vmware (noble-proposed/main) [1:13.4.0-1 => 1:13.4.0-1build1] (desktop-core, xorg) [16:27] -queuebot:#ubuntu-release- Unapproved: yajl (noble-proposed/main) [2.1.0-5 => 2.1.0-5build1] (ubuntu-desktop, ubuntu-server) [16:27] -queuebot:#ubuntu-release- Unapproved: xcb-util-wm (noble-proposed/main) [0.4.1-1.1build2 => 0.4.1-1.1build3] (desktop-core, i386-whitelist) [16:27] -queuebot:#ubuntu-release- Unapproved: xfsdump (noble-proposed/main) [3.1.11-0.1 => 3.1.11-0.1build1] (core) [16:27] -queuebot:#ubuntu-release- Unapproved: xorg (noble-proposed/main) [1:7.7+23ubuntu2 => 1:7.7+23ubuntu3] (core, xorg) [16:27] -queuebot:#ubuntu-release- Unapproved: xserver-xorg-video-fbdev (noble-proposed/main) [1:0.5.0-2build1 => 1:0.5.0-2build2] (desktop-core, xorg) [16:27] -queuebot:#ubuntu-release- Unapproved: xxhash (noble-proposed/main) [0.8.2-2 => 0.8.2-2build1] (core, i386-whitelist) [16:27] -queuebot:#ubuntu-release- Unapproved: zip (noble-proposed/main) [3.0-13 => 3.0-13build1] (desktop-core, i386-whitelist, ubuntu-server) [16:27] -queuebot:#ubuntu-release- Unapproved: xf86-input-wacom (noble-proposed/main) [1:1.2.0-1ubuntu1 => 1:1.2.0-1ubuntu2] (desktop-core, xorg) [16:27] -queuebot:#ubuntu-release- Unapproved: xserver-xorg-video-ati (noble-proposed/main) [1:22.0.0-1 => 1:22.0.0-1build1] (desktop-core, xorg) [16:27] -queuebot:#ubuntu-release- Unapproved: yaml-cpp (noble-proposed/main) [0.8.0+dfsg-6 => 0.8.0+dfsg-6build1] (ubuntu-desktop) [16:27] -queuebot:#ubuntu-release- Unapproved: xinit (noble-proposed/main) [1.4.1-0ubuntu4 => 1.4.1-0ubuntu5] (desktop-core) [16:27] -queuebot:#ubuntu-release- Unapproved: zope.interface (noble-proposed/main) [6.1-1 => 6.1-1build1] (ubuntu-desktop, ubuntu-server, zope) [16:27] -queuebot:#ubuntu-release- Unapproved: xserver-xorg-video-vesa (noble-proposed/main) [1:2.6.0-1 => 1:2.6.0-1build1] (desktop-core, xorg) [16:27] -queuebot:#ubuntu-release- Unapproved: xserver-xorg-video-intel (noble-proposed/main) [2:2.99.917+git20210115-1 => 2:2.99.917+git20210115-1build1] (desktop-core, xorg) [16:27] -queuebot:#ubuntu-release- Unapproved: zsh (noble-proposed/main) [5.9-6ubuntu1 => 5.9-6ubuntu2] (core, i386-whitelist) [16:32] -queuebot:#ubuntu-release- Unapproved: fwupd-efi (noble-proposed/main) [1:1.4-1build1 => 1:1.4-1build1] (no packageset) [16:35] ubiquity currently build-depends on NBS gir1.2-webkit2-4.0. as far as I can see, all flavors are now migrated to a different installer than ubiquity for noble. Should I just drop building of ubiquity-frontend-gtk in noble? leaving only oem-config [16:36] vorlon: I believe that's correct, we discussed that a lot during flavor sync with seb128 and jbicha. [16:37] If it's wrong we'll see either way :D [16:37] juliank: If it's wrong I'm sure someone is getting bonked. :D [16:38] One warning: even oem-config uses the slideshow, so I'm not sure if that needs all of the webkit components or not. === halves8 is now known as halves [16:43] busybox ftbfs everywhere [16:43] it's very bad [16:44] main: src:linux-ibm [16:44] main: src:linux-laptop [16:44] main: src:linux-meta-ibm [16:44] main: src:linux-meta-starfive [16:44] main: src:linux-signed-ibm [16:44]