[00:25] -queuebot:#ubuntu-release- New binary: afflib [amd64] (noble-proposed/universe) [3.7.20-1.1ubuntu1] (no packageset)
[00:25] -queuebot:#ubuntu-release- New binary: afflib [armhf] (noble-proposed/universe) [3.7.20-1.1ubuntu1] (no packageset)
[00:25] -queuebot:#ubuntu-release- New binary: afflib [arm64] (noble-proposed/universe) [3.7.20-1.1ubuntu1] (no packageset)
[00:28] -queuebot:#ubuntu-release- New binary: afflib [ppc64el] (noble-proposed/universe) [3.7.20-1.1ubuntu1] (no packageset)
[00:28] -queuebot:#ubuntu-release- New binary: afflib [s390x] (noble-proposed/universe) [3.7.20-1.1ubuntu1] (no packageset)
[00:42] -queuebot:#ubuntu-release- Unapproved: ubuntu-dev-tools (jammy-proposed/universe) [0.193ubuntu4~22.04.2 => 0.201ubuntu2~22.04.1] (no packageset)
[00:48] -queuebot:#ubuntu-release- Unapproved: ubuntu-dev-tools (mantic-proposed/universe) [0.196 => 0.201ubuntu2~23.10.1] (no packageset)
[00:50] <vorlon> adns looks like a fun armhf-specific build failure for someone to debug
[00:51] <vorlon> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065725
[00:51] -ubottu:#ubuntu-release- Debian bug 1065725 in src:adns "adns: FTBFS on arm{el,hf}: FAILED ./case-1stservbroken - WRONG OUTPUT - lines of syscall remaining 0" [Serious, Open]
[00:52] <vorlon> 165: [mutex_test.cc : 313] RAW: Check absl::Seconds(0.4) <= elapsed && elapsed <
[00:52] <vorlon> = absl::Seconds(0.9) failed: TestTime failed
[00:52] <vorlon> so if we ever manage to get all these libraries to build from source... then we'll be golden wrt Y2038
[00:59] <vorlon> LocutusOfBorg: fwiw doxygen ftbfs with llvm-18: https://launchpad.net/ubuntu/+source/doxygen/1.9.8+ds-2build2
[01:03] <doko> both Debian and Ubuntu. most likely missing symlinks
[01:29] <mwhudson> vorlon: i think you are lying about that adns failure looking fun
[01:59] <vorlon> mwhudson: just need to find the right someone
[02:09] -queuebot:#ubuntu-release- New binary: afflib [riscv64] (noble-proposed/universe) [3.7.20-1.1ubuntu1] (no packageset)
[02:10] -queuebot:#ubuntu-release- New: accepted afflib [amd64] (noble-proposed) [3.7.20-1.1ubuntu1]
[02:10] -queuebot:#ubuntu-release- New: accepted afflib [armhf] (noble-proposed) [3.7.20-1.1ubuntu1]
[02:10] -queuebot:#ubuntu-release- New: accepted afflib [riscv64] (noble-proposed) [3.7.20-1.1ubuntu1]
[02:10] -queuebot:#ubuntu-release- New: accepted afflib [arm64] (noble-proposed) [3.7.20-1.1ubuntu1]
[02:10] -queuebot:#ubuntu-release- New: accepted afflib [s390x] (noble-proposed) [3.7.20-1.1ubuntu1]
[02:10] -queuebot:#ubuntu-release- New: accepted afflib [ppc64el] (noble-proposed) [3.7.20-1.1ubuntu1]
[04:04] <vorlon> mwhudson: would you rather adns, or abseil - which very clearly presents time everywhere in its API as int64_t and yet somehow manages to have regressions when time_t is promoted to this size on armhf
[04:05] <mwhudson> vorlon: heh
[04:07] <mwhudson> vorlon: they're not just bad tests that fail on overloaded hosts?
[04:07] <vorlon> mwhudson: nope
[04:08] <mwhudson> it looks like the time values are out by a factor of like 10,000
[04:08] <mwhudson> how do you do that
[04:08] <vorlon> with 8,000 C++ operators
[04:14] <arraybolt3> um, what happened here: https://launchpad.net/ubuntu/+source/kubuntu-settings/ https://launchpad.net/ubuntu/+source/kubuntu-settings/1:24.04.4
[04:14] <arraybolt3> somehow the 1:24.04.4 package *was* in -proposed and was visible on the first page, but now it's vanished?
[04:17] <mwhudson> arraybolt3: um at a guess it's in the process of moving from proposed to release
[04:17] <mwhudson> https://launchpad.net/ubuntu/+source/kubuntu-settings/+publishinghistory
[04:18] <arraybolt3> ah, that makes sense
[04:18] <arraybolt3> I just caught it at a bad time
[04:19] <mwhudson> it isn't usually like this for very long. but it should resolve
[04:23] -queuebot:#ubuntu-release- New: accepted fwupd-snap [source] (noble-proposed) [1.9.x-0ubuntu1]
[04:26] -queuebot:#ubuntu-release- New binary: fwupd-snap [amd64] (noble-proposed/none) [1.9.x-0ubuntu1] (no packageset)
[04:35] -queuebot:#ubuntu-release- New: accepted performance-tools [source] (noble-proposed) [0ubuntu1]
[04:38] -queuebot:#ubuntu-release- New binary: performance-tools [amd64] (noble-proposed/none) [0ubuntu1] (no packageset)
[04:48] <liushuyu> https://launchpad.net/ubuntu/+source/rpcbind/1.2.6-7build1 still depends on libtirpc3 (non-t64) version despite the previous no-change rebuild was targeted to fix that
[04:48] <liushuyu> I have looked at both libtirpc and rpcbind and can't find any clues why this happens
[04:49] <liushuyu> (probably the build was run when publisher hasn't fully published the builds?)
[04:52] -queuebot:#ubuntu-release- New: accepted ubuntu-boot-test [source] (noble-proposed) [1]
[04:56] -queuebot:#ubuntu-release- New binary: ubuntu-boot-test [amd64] (noble-proposed/none) [1] (no packageset)
[04:56] -queuebot:#ubuntu-release- New binary: ubuntu-boot-test [ppc64el] (noble-proposed/none) [1] (no packageset)
[04:56] -queuebot:#ubuntu-release- New binary: ubuntu-boot-test [armhf] (noble-proposed/none) [1] (no packageset)
[04:56] -queuebot:#ubuntu-release- New binary: ubuntu-boot-test [s390x] (noble-proposed/none) [1] (no packageset)
[04:57] -queuebot:#ubuntu-release- New binary: ubuntu-boot-test [arm64] (noble-proposed/none) [1] (no packageset)
[05:39] -queuebot:#ubuntu-release- New binary: ubuntu-boot-test [riscv64] (noble-proposed/universe) [1] (no packageset)
[05:48] <vorlon> liushuyu: rpcbind> the problem is that libtirpc-dev is already in the build chroot due to the previous libc6-dev dependency on it; so since rpcbind doesn't declare a versioned build-dependency, it doesn't get updated
[05:50] <liushuyu> vorlon: I see
[05:53] <liushuyu> so the build chroot itself is immutable to some extent
[05:53] <vorlon> liushuyu: so I guess someone needs to prepare uploads of all libtirpc3 revdeps with bumped build-dependencies
[10:41] -queuebot:#ubuntu-release- Unapproved: dotnet6 (mantic-proposed/universe) [6.0.127-0ubuntu1~23.10.1 => 6.0.128-0ubuntu1~23.10.1] (no packageset)
[10:47] -queuebot:#ubuntu-release- Unapproved: dotnet6 (jammy-proposed/universe) [6.0.127-0ubuntu1~22.04.1 => 6.0.128-0ubuntu1~22.04.1] (no packageset)
[13:32] -queuebot:#ubuntu-release- New binary: ubuntukylin-meta [ppc64el] (noble-proposed/universe) [0.54] (ubuntukylin)
[13:44] -queuebot:#ubuntu-release- New binary: ubuntukylin-meta [s390x] (noble-proposed/universe) [0.54] (ubuntukylin)
[13:51] -queuebot:#ubuntu-release- New binary: ubuntukylin-meta [amd64] (noble-proposed/universe) [0.54] (ubuntukylin)
[14:13] -queuebot:#ubuntu-release- Unapproved: accepted mutter [source] (jammy-proposed) [42.9-0ubuntu7]
[14:32] -queuebot:#ubuntu-release- New binary: ubuntukylin-meta [armhf] (noble-proposed/universe) [0.54] (ubuntukylin)
[14:38] <LocutusOfBorg> vorlon, openmpi wants patchelf on i386...
[14:38] -queuebot:#ubuntu-release- New binary: ubuntukylin-meta [arm64] (noble-proposed/universe) [0.54] (ubuntukylin)
[14:38] <LocutusOfBorg> (due to dh-fortran-mod)
[15:03] <kanashiro> vorlon re ruby transition: the blockers are related to the armhf FTBFSes due to the 64 bits time_t transition
[15:24] <ginggs> LocutusOfBorg: can dh-fortran-mod use chrpath instead?
[15:35] <vorlon> kanashiro: any in particular?
[15:36] <vorlon> LocutusOfBorg: patchelf lol
[15:38] <vorlon> LocutusOfBorg: trying to find the thread in my mailbox, I thought there was discussion about openmpi dropping 32-bit support altogether and mpi-default-dev moving to mpich
[15:38] <vorlon> LocutusOfBorg: but of course mpich is not currently built on i386
[15:40] <vorlon> LocutusOfBorg: should we change whatever is build-depending on mpi on i386
[15:47] <vorlon> bandali: https://launchpad.net/ubuntu/+source/gst-plugins-good1.0/1.24.0-1ubuntu1 so uploading packages that are in the process of being bootstrapped for time_t is not advisable right now
[15:48] <vorlon> bandali: I'll copy this to the bootstrap ppa to get it built on armhf now, and in this case it isn't slowing us down, but if it were I would be reverting the upload
[16:11] <jbicha> vorlon: ok, but some gstreamer packages were unbuildable without updating -good and -bad
[16:11] <jbicha> I've uploaded libproxy 0.5.4-3 to Debian to bootstrap it and plan to sync it late today. Let me know if you need it in Ubuntu sooner
[16:37] <bandali> vorlon, noted. the upload was indeed per Jeremy's suggestion, to help unblock the gstreamer 1.24 transition
[16:43] -queuebot:#ubuntu-release- Packageset: Added php8.3 to ubuntu-server in noble
[16:43] -queuebot:#ubuntu-release- Packageset: Added postgresql-16 to ubuntu-server in noble
[17:34] <vorlon> jbicha: uh what do you mean wrt bootstrapping libproxy?
[17:34] <vorlon> jbicha: we have libproxy in the bootstrap ppa and it's the biggest problem right now because of the webkit2gtk nonsense
[17:35] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (mantic-proposed/main) [0.142ubuntu15.1 => 0.142ubuntu22] (core, i386-whitelist)
[17:35] <vorlon> ah you intend to do a stage1 build?
[17:36] <vorlon> well, you can.  I've been trying to avoid pushing things to the main archive with temporary bootstrap hacks
[17:36] <vorlon> so if you do push it, I know that will speed things up
[17:36] <jbicha> vorlon: yes, it's basically the same as liushuyu's work but more targeted on architectures. And Debian can use it too
[17:37] <vorlon> sure
[17:57] <bandali> hey RikMills, kosmindoormap says it wants libkopeninghours-dev (>= 23.08.5~) but kopeninghours 23.08.5 isn't even in -proposed - would y'all please investigate? thanks
[17:58] <bandali> (itinerary in turn needs kosmindoormap)
[18:09] <santa_> bandali: I have been looking into that and I think some things were uploaded but not accepted by LP because they are not in the kubuntu package set
[18:09] <santa_> but they should be
[18:12] <santa_> missing things of plasma: https://pastebin.ubuntu.com/p/bhXf48r6fk/
[18:12] <santa_> missing things of applications: https://pastebin.ubuntu.com/p/Rgwmk4Prgh/
[18:14] <santa_> build status of plasma: https://groomlake.tritemio.org/ka-iron-hand_reports/applications_archive/23.08.5_noble_retry_builds.pdf
[18:14] <bandali> santa_, i see, thanks for the update. i'm guessing you'll want to work with vorlon or one of the other ubuntu-archive folks to get those packages added to the kubuntu set?
[18:16] <santa_> bandali: I was thinking about sending a mail to the devel-permissions list with the info above
[18:16] <vorlon> yes, packageset changes go via devel-permissions
[18:16] <santa_> so the wiki is updated
[18:17] <santa_> https://wiki.ubuntu.com/DeveloperMembershipBoard/KnowledgeBase
[18:17] <santa_> I tried to get subscribed to the list in question but I guess my request is pending on mods
[18:17] <vorlon> I'm not sure it's open to subscriptions
[18:18] <vorlon> and you don't have to be subscribed to send a request there
[18:18] <santa_> oh well, if it's not open no problem. I can send a mail there anyway
[18:18] <vorlon> you're definitely not *expected* to subscribe to the list to send requests :)
[18:20] <bandali> thanks in advance santa_ :)
[18:21] <vorlon> LocutusOfBorg: any insight into the doxygen build failure w/ llvm-18?
[18:21] <vorlon> LocutusOfBorg: should we switch it to llvm-17 in the near term?
[18:28] <doko> vorlon: I fixed it
[18:31] <vorlon> doko: ok, so we should retry the doxygen/armhf build as soon as llvm-18 publishes?
[18:31] <vorlon> looks like we hit a slow builder, 2x the build time of the previous build :/
[18:32] <doko> yes, that sucks. I also seem to be unluck with openjdk-lts bootstraps and the openjdk-8 build
[18:41] <bdrung> question for the SRU team: I want to backport a fix for the network code in initramfs-tools. noble has more autopkgtests for the network code. What is your take on backporting those autopkgtest changes to increase the test coverage?
[18:45] <rbasak> bdrung: improving tests in SRUs is always welcome. No need for an SRU bug either, just an explanation in the changelog. Of course we will then expect the tests to pass before releasing the SRU :)
[18:45] <rbasak> s/in/as part of/
[18:46] <bdrung> rbasak, okay thanks. Then I'll prepare the SRU. The autopkgtest change will be the biggest part in the diff.
[18:57] <athos> Hi ubuntu-release, could anyone have a look at this FFe for Symfony (php): https://bugs.launchpad.net/ubuntu/+source/symfony/+bug/2057636 This should be useful to fix issues with the PSR stack support across different php packages which has been facing issues for a while now...
[18:57] -ubottu:#ubuntu-release- Launchpad bug 2057636 in symfony (Ubuntu) "[FFe] Symfony 6" [Undecided, New]
[19:31] <LocutusOfBorg> yeah
[19:51] <kanashiro> vorlon spglib, libguestfs and libprelude
[20:09] <vpa1977> Hi, would it be possible to take a look at FFe request for jruby merge https://bugs.launchpad.net/ubuntu/+source/jruby/+bug/2056521 ?
[20:09] -ubottu:#ubuntu-release- Launchpad bug 2056521 in jruby (Ubuntu) "[ffe] please merge jruby 9.4.6.0+ds-1 from debian unstable" [Undecided, New]
[20:23] <vorlon> would it be faster to kill the llvm-toolchain-18/armhf build and get a different builder, or let it finish...
[20:30] <vorlon> kanashiro: libguestfs> oh nooooooo
[20:30] <vorlon> ok well that's one we're working on. slowly.
[20:31] <kanashiro> once those three packages are built in armhf ruby-defaults should migrate
[20:31] <kanashiro> then we need to remove ruby3.1 from noble
[20:31] <vorlon> vpa1977: did you mean ruby3.2 compatibility
[20:31] <vorlon> (in your ffe bug)
[20:33] <vpa1977> 3.1
[20:33] <vpa1977> they are catching up
[20:38] <vorlon> vpa1977: so it still won't be compatible with ruby3.2 that we're shipping in noble?
[20:39] <vorlon> vpa1977: ah but this is a separate implementation of the interpreter anyway so it doesn't have to be on par with ruby3.2, it just has to be compatible with the ruby code being run against it
[20:39] <vpa1977> yes, but it fixes 77 bugs related to 3.1 compatibility
[20:39] <vorlon> vpa1977: approved
[20:39] <vpa1977> thank you!!!
[21:29] -queuebot:#ubuntu-release- Unapproved: runc (focal-proposed/main) [1.1.7-0ubuntu1~20.04.2 => 1.1.7-0ubuntu1~20.04.3] (no packageset)
[21:29] -queuebot:#ubuntu-release- Unapproved: runc (jammy-proposed/main) [1.1.7-0ubuntu1~22.04.2 => 1.1.7-0ubuntu1~22.04.3] (ubuntu-server)
[21:30] -queuebot:#ubuntu-release- Unapproved: runc (mantic-proposed/main) [1.1.7-0ubuntu2.2 => 1.1.7-0ubuntu2.3] (ubuntu-server)
[21:43] -queuebot:#ubuntu-release- Packageset: Added nvidia-graphics-drivers-550-server to i386-whitelist in focal
[21:43] -queuebot:#ubuntu-release- Packageset: Added nvidia-graphics-drivers-550-server to i386-whitelist in jammy
[21:43] -queuebot:#ubuntu-release- Packageset: Added nvidia-graphics-drivers-550-server to i386-whitelist in mantic
[21:43] -queuebot:#ubuntu-release- Packageset: Added nvidia-graphics-drivers-550-server to i386-whitelist in noble
[21:43] -queuebot:#ubuntu-release- Unapproved: containerd-app (focal-proposed/universe) [1.7.2-0ubuntu1~20.04.1 => 1.7.12-0ubuntu2~20.04.1] (no packageset)
[21:45] -queuebot:#ubuntu-release- Unapproved: containerd-app (jammy-proposed/universe) [1.7.2-0ubuntu1~22.04.1 => 1.7.12-0ubuntu2~22.04.1] (no packageset)
[21:49] -queuebot:#ubuntu-release- Unapproved: containerd-app (mantic-proposed/main) [1.7.2-0ubuntu2 => 1.7.12-0ubuntu2~23.10.1] (no packageset)
[22:34] -queuebot:#ubuntu-release- New binary: fabric-manager-550 [amd64] (noble-proposed/none) [550.54.14-0ubuntu2] (no packageset)
[22:34] -queuebot:#ubuntu-release- New binary: libnvidia-nscq-550 [amd64] (noble-proposed/none) [550.54.14-0ubuntu1] (no packageset)
[22:35] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-550-server [i386] (noble-proposed/none) [550.54.14-0ubuntu3] (i386-whitelist)
[22:37] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-550-server [amd64] (noble-proposed/none) [550.54.14-0ubuntu3] (i386-whitelist)
[22:48] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (jammy-proposed) [3.192.54.8]
[22:55] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (focal-proposed) [3.192.30.19]
[22:59] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (bionic-proposed) [3.192.1.21]
[23:08] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (xenial-proposed) [3.168.22]
[23:18] -queuebot:#ubuntu-release- New binary: libnvidia-nscq-550 [arm64] (noble-proposed/none) [550.54.14-0ubuntu1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: fabric-manager-550 [arm64] (noble-proposed/none) [550.54.14-0ubuntu2] (no packageset)
[23:35] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-550-server [arm64] (noble-proposed/multiverse) [550.54.14-0ubuntu3] (i386-whitelist)