/srv/irclogs.ubuntu.com/2024/03/12/#ubuntu-release.txt

vorlontriggering first round of rebuilds for libqt6core6t6401:49
vorlonLocutusOfBorg: you mention fixing llvms... looks like qt6-tools blocks on libclang-15-dev02:10
vorlonLocutusOfBorg: anything I can do to help, or do you have it in hand?02:11
=== chris14_ is now known as chris14
=== RAOF_ is now known as RAOF
vorlonah the openldap armhf test failure involves a time_t in a format string, because of course it does02:41
RikMillsvorlon: do you know if we are near at all to having qt5 qtbase build on armhf?03:44
arraybolt3RikMills: 15:25 <vorlon> seb128: heh I just answered that question in parallel.  I'm currently estimating a week before we start getting the main clusters (freedesktop; qt) in a position to migrate.  But there's a lot of risk in that estimate, because we don't have all the bootstrap loops broken yet04:29
vorlonRikMills: qtbase is built on armhf05:50
RikMillsvorlon: not according to https://launchpad.net/ubuntu/+source/qtbase-opensource-src/5.15.12+dfsg-3ubuntu305:51
RikMillsdo you mean qt6?05:51
vorlonRikMills: you're reading it wrong05:51
vorlonthere is a successful build and a failed build05:51
RikMillsvorlon: that link is the lastes in proposed it seems05:52
RikMills*latest05:52
RikMillsvorlon: do you mean a build in the bootstrap ppa?05:54
vorlonRikMills: no, look at that page you just linked to. armhf is listed twice05:54
RikMillsohhhhhh05:54
RikMillsnevers seen that before05:54
vorlonone source package, two build records because it was buit in the bootstrap ppa and copied back over05:55
RikMillsvorlon: right. didn't know that was possible. thanks!05:55
=== pushkarnk1 is now known as pushkarnk
LocutusOfBorgvorlon, it was waiting lp to pick it up07:41
vorlonLocutusOfBorg: on llvm-15? because https://launchpad.net/ubuntu/+source/llvm-toolchain-15/1:15.0.7-13 shows a build failure on armhf07:42
LocutusOfBorgSource llvm-toolchain-15 -> noble/Proposed: current version 1:15.0.7-13, new version 1:15.0.7-1407:42
LocutusOfBorgDownloading llvm-toolchain-15_15.0.7-14.dsc from deb.debian.org (0.008 MiB)07:42
LocutusOfBorgI uploaded 10h ago on Debian07:42
vorlonah , for lp to import the new Debian version so it could sync, ok07:42
LocutusOfBorg14 15 16 17 18 should be ok in 12h or so07:44
vorlonperfect, thanks07:44
vorlon(also just found out we're waiting on 18 for doxygen)07:45
LocutusOfBorghopefully07:45
LocutusOfBorg18 is already mostly built=?07:45
LocutusOfBorgNoble: [FULLYBUILT] amd64 [BUILDING] arm64 [FULLYBUILT] armhf [FULLYBUILT] i386 [FULLYBUILT] ppc64el [BUILDING] riscv64 [FULLYBUILT] s390x07:45
vorlonLocutusOfBorg: for https://launchpad.net/ubuntu/+source/llvm-toolchain-18/1:18.1.0-1ubuntu2 ?07:46
vorlonif that's confirmed good I can upload doxygen now07:46
vorlonor would building with the previous version on arm64 and riscv64 cause misbuilds...07:47
LocutusOfBorgif previous you mean https://launchpad.net/ubuntu/+source/llvm-toolchain-18/1:18.1.0-1ubuntu1?07:53
LocutusOfBorgit was a run with no tests, but the code should be good07:53
LocutusOfBorgthe ubuntu2 has spirv support07:53
vorlonLocutusOfBorg: ok I have no idea what the impact would be of building doxygen with an llvm without spirv support08:02
-queuebot:#ubuntu-release- Unapproved: accepted cockpit-machines [source] (jammy-backports) [307-1~bpo22.04.1]08:59
-queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (jammy-backports) [311-1~bpo22.04.1]08:59
-queuebot:#ubuntu-release- Unapproved: accepted cockpit-podman [source] (jammy-backports) [84-1~bpo22.04.1]08:59
-queuebot:#ubuntu-release- Unapproved: accepted cockpit-machines [source] (mantic-backports) [307-1~bpo23.10.1]09:02
-queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (mantic-backports) [311-1~bpo23.10.1]09:02
-queuebot:#ubuntu-release- Unapproved: accepted cockpit-podman [source] (mantic-backports) [84-1~bpo23.10.1]09:02
-queuebot:#ubuntu-release- Unapproved: accepted rpki-client [source] (jammy-backports) [9.0-1~bpo22.04.1]09:14
LocutusOfBorgvorlon, I would say none09:28
LocutusOfBorg(in any case spirv support was added just in that upload, we usually don't have spirv until spirv is available and built with older llvm, then we rebuild with it09:29
LocutusOfBorge.g. in Debian llvm is still without it09:29
-queuebot:#ubuntu-release- Unapproved: accepted libreoffice [source] (jammy-backports) [4:7.6.5-0ubuntu0.23.10.1~bpo22.04.1]09:30
LocutusOfBorgok so now I need just to do ubuntu-build --batch --retry09:34
LocutusOfBorgnice indeed09:34
LocutusOfBorgI merged and updated changelog (with only a subset of your changes!)09:39
-queuebot:#ubuntu-release- New binary: pipewire [i386] (noble-proposed/main) [1.0.3-1.1ubuntu1] (desktop-core, i386-whitelist)10:03
-queuebot:#ubuntu-release- New binary: pipewire [amd64] (noble-proposed/main) [1.0.3-1.1ubuntu1] (desktop-core, i386-whitelist)10:05
-queuebot:#ubuntu-release- New binary: pipewire [arm64] (noble-proposed/main) [1.0.3-1.1ubuntu1] (desktop-core, i386-whitelist)10:06
-queuebot:#ubuntu-release- New binary: pipewire [ppc64el] (noble-proposed/main) [1.0.3-1.1ubuntu1] (desktop-core, i386-whitelist)10:08
-queuebot:#ubuntu-release- New binary: pipewire [s390x] (noble-proposed/main) [1.0.3-1.1ubuntu1] (desktop-core, i386-whitelist)10:13
-queuebot:#ubuntu-release- New: accepted pipewire [amd64] (noble-proposed) [1.0.3-1.1ubuntu1]10:27
-queuebot:#ubuntu-release- New: accepted pipewire [i386] (noble-proposed) [1.0.3-1.1ubuntu1]10:27
-queuebot:#ubuntu-release- New: accepted pipewire [s390x] (noble-proposed) [1.0.3-1.1ubuntu1]10:27
-queuebot:#ubuntu-release- New: accepted pipewire [arm64] (noble-proposed) [1.0.3-1.1ubuntu1]10:27
-queuebot:#ubuntu-release- New: accepted pipewire [ppc64el] (noble-proposed) [1.0.3-1.1ubuntu1]10:27
-queuebot:#ubuntu-release- Unapproved: php8.1 (jammy-proposed/main) [8.1.2-1ubuntu2.14 => 8.1.2-1ubuntu2.15] (i386-whitelist, ubuntu-server)10:32
-queuebot:#ubuntu-release- New: accepted libdfx [source] (noble-proposed) [2023.2-0ubuntu3]11:49
-queuebot:#ubuntu-release- New binary: libdfx [amd64] (noble-proposed/none) [2023.2-0ubuntu3] (no packageset)11:52
-queuebot:#ubuntu-release- New binary: libdfx [ppc64el] (noble-proposed/none) [2023.2-0ubuntu3] (no packageset)12:15
-queuebot:#ubuntu-release- New binary: libdfx [s390x] (noble-proposed/none) [2023.2-0ubuntu3] (no packageset)12:20
dokoapw, xnox: we really need a linux build, making linux-tools-6.8.0-11 installable again12:34
dokoon armhf12:34
apwarighi, ^^12:35
arighidoko, problem is that the build time is relly slow... we have a new build in progress in the c-k-t/bootstrap ppa (6.8.0-17.17)13:11
dokoarighi: URL?13:13
dokoarighi: is that PPA building against -proposed?13:13
dokoarighi, apw: you have to ask people to bump scores. now done13:16
arighidoko, https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+sourcepub/15848070/+listing-archive-extra13:17
arighidoko, and yes, it's building against -proposed13:18
dokoarighi: wtf, why do you have a b-d on a shared library? clang-17, libclang1-17  that cannot work13:24
arighidoko, we need clang-17 to enable Rust-for-linux13:24
arighiwhy it cannot work to depend on libclang?13:25
dokosure, but you don't need libclang1-1713:25
dokobecause the library was renamed13:25
arighihm... we can try to remove the dep on libclang-17, but I'm not sure if rust is happy13:26
dokoThe following packages have unmet dependencies:13:26
doko libllvm17t64 : Breaks: libllvm17 (< 1:17.0.6-9) but 1:17.0.6-5build1 is to be installed13:26
dokorust will be happy13:26
arighiok I can remove the libclang dep13:26
dokoarighi: do you also have that one as a dependency?13:26
arighinope, we only have the dep on libclang13:27
dokojust drop it, clang-17 depends on the correct library13:29
arighialright so to recap, I'll keep the dep on clang-17 and drop libclang-1713:30
dokocorrect13:30
dokoalso note, the clang-17 package currently is uninstallable on riscv64, failing to build due to whatever instability, so that will also take a little bit longer13:31
-queuebot:#ubuntu-release- New binary: libdfx [armhf] (noble-proposed/universe) [2023.2-0ubuntu3] (no packageset)13:31
-queuebot:#ubuntu-release- New: accepted libdfx [amd64] (noble-proposed) [2023.2-0ubuntu3]13:33
-queuebot:#ubuntu-release- New: accepted libdfx [ppc64el] (noble-proposed) [2023.2-0ubuntu3]13:33
-queuebot:#ubuntu-release- New: accepted libdfx [armhf] (noble-proposed) [2023.2-0ubuntu3]13:33
-queuebot:#ubuntu-release- New: accepted libdfx [s390x] (noble-proposed) [2023.2-0ubuntu3]13:33
arighidoko, hm.. so we are not able to build the kernel because of that, we need to do some tricks or exclude riscv6413:33
arighiis it the same on armhf?13:34
dokoarighi: no, just upload. the kernel will be buildable on riscv64, once llvm-toolchain-17 is built.13:34
arighidoko, ack13:35
dokothe armhf build should work without the libclang1-17 b-d13:35
-queuebot:#ubuntu-release- New binary: libdfx [arm64] (noble-proposed/universe) [2023.2-0ubuntu3] (no packageset)13:35
-queuebot:#ubuntu-release- New: accepted libdfx [arm64] (noble-proposed) [2023.2-0ubuntu3]13:36
-queuebot:#ubuntu-release- Unapproved: pulseaudio (jammy-proposed/main) [1:15.99.1+dfsg1-1ubuntu2.1 => 1:15.99.1+dfsg1-1ubuntu2.2] (core, i386-whitelist)13:42
-queuebot:#ubuntu-release- Unapproved: pulseaudio (mantic-proposed/main) [1:16.1+dfsg1-2ubuntu4 => 1:16.1+dfsg1-2ubuntu4.1] (core, i386-whitelist)13:42
arighidoko, new kernel without the libclang b-d uploaded to the bootstrap ppa: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+sourcepub/15851940/+listing-archive-extra13:56
dokoarighi: ta, at least armhf is building now13:57
-queuebot:#ubuntu-release- Unapproved: hexchat (mantic-proposed/universe) [2.16.1-1build2 => 2.16.1-1ubuntu0.1] (xubuntu)14:00
-queuebot:#ubuntu-release- Unapproved: hexchat (jammy-proposed/universe) [2.16.0-4build1 => 2.16.0-4ubuntu0.1] (xubuntu)14:06
-queuebot:#ubuntu-release- New: accepted freerdp3 [source] (noble-proposed) [3.3.0+dfsg1-0ubuntu1]15:16
=== mfo_ is now known as mfo
-queuebot:#ubuntu-release- New binary: freerdp3 [amd64] (noble-proposed/none) [3.3.0+dfsg1-0ubuntu1] (no packageset)15:20
-queuebot:#ubuntu-release- New binary: freerdp3 [ppc64el] (noble-proposed/none) [3.3.0+dfsg1-0ubuntu1] (no packageset)15:22
-queuebot:#ubuntu-release- Unapproved: snapd (mantic-proposed/main) [2.60.4+23.10.1 => 2.61.3+23.10] (desktop-core, ubuntu-server)15:22
-queuebot:#ubuntu-release- New binary: freerdp3 [s390x] (noble-proposed/none) [3.3.0+dfsg1-0ubuntu1] (no packageset)15:24
-queuebot:#ubuntu-release- Unapproved: snapd (jammy-proposed/main) [2.58+22.04.1 => 2.61.3+22.04] (desktop-core, ubuntu-server)15:24
-queuebot:#ubuntu-release- Unapproved: snapd (focal-proposed/main) [2.58+20.04.1 => 2.61.3+20.04] (core)15:27
-queuebot:#ubuntu-release- New: accepted freerdp3 [amd64] (noble-proposed) [3.3.0+dfsg1-0ubuntu1]15:30
-queuebot:#ubuntu-release- New: accepted freerdp3 [s390x] (noble-proposed) [3.3.0+dfsg1-0ubuntu1]15:30
-queuebot:#ubuntu-release- New: accepted freerdp3 [ppc64el] (noble-proposed) [3.3.0+dfsg1-0ubuntu1]15:30
-queuebot:#ubuntu-release- New binary: freerdp3 [arm64] (noble-proposed/none) [3.3.0+dfsg1-0ubuntu1] (no packageset)15:30
-queuebot:#ubuntu-release- New: accepted freerdp3 [arm64] (noble-proposed) [3.3.0+dfsg1-0ubuntu1]15:31
-queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (mantic-proposed) [2.61.3+23.10]15:51
-queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (jammy-proposed) [2.61.3+22.04]16:01
-queuebot:#ubuntu-release- Unapproved: software-properties (xenial-proposed/main) [0.96.20.12 => 0.96.20.13] (desktop-core, ubuntu-server)16:20
-queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (focal-proposed) [2.61.3+20.04]16:59
vorlonbandali: hi, I see that you're on +1 maintenance this week, and wanted to give some guidance on priorities19:41
-queuebot:#ubuntu-release- New binary: libreoffice [amd64] (jammy-backports/main) [4:7.6.5-0ubuntu0.23.10.1~bpo22.04.1] (ubuntu-desktop)19:45
vorlonbandali: basically, the priority needs to be "getting t64 transition done".  So what that looks like is, starting chronologically from about 28Feb (currently '13 days old'), go through update_excuses and work out why those particular packages are not migrating; trigger no-change rebuilds as necessary, fix sources as necessary, get their build-deps built first if necessary, and if you find a19:46
vorlonbuild-dependency loop you can kick this to the Foundations Team to resolve19:46
vorlonand fwiw I just found the first package on the list was 'apophenia', which has been ftbfs in Ubuntu in a while but not in Debian.  I've ripped the package out of the release pocket peremptorily but left it in -proposed for now19:53
vorlon(no bug filed about the ftbfs; wild guess is that this is a mariadb vs mysql issue)19:53
-queuebot:#ubuntu-release- New binary: llvm-toolchain-snapshot [amd64] (noble-proposed/universe) [1:19~++20240304085905+c7fdd8c11e54-1ubuntu2] (i386-whitelist)19:55
-queuebot:#ubuntu-release- New: accepted llvm-toolchain-snapshot [amd64] (noble-proposed) [1:19~++20240304085905+c7fdd8c11e54-1ubuntu2]20:01
dokoThe following packages have unmet dependencies:20:03
doko libcom-err2 : Breaks: libcom-err2t64 (< 1.47.0-2.4~exp1ubuntu1)20:03
dokoerr, on arm64?20:03
dokodbungert, vorlon: ^^^ the reversion seems to be wrong20:05
vorlonit's correct to revert it20:05
vorlonbecause com-err2 does not have an ABI change20:05
vorlonbut I just hit this in a build failure, haven't had a chance to look at why, currently in stand-up20:06
vorlonwe do want to rebuild everything that has picked up a dependency on libcom-err2t64, to depend again on libcom-err220:06
vorlonand libcom-err2 should Provides; libcom-err2t64 on all archs20:06
dokoI think it should have a versioned Provides ...20:06
doko+Provides: libss2t6420:07
doko+Breaks: libss2t64 (<< ${source:Version})20:07
dokoit doesn't know what is provided. Plus the breaks should be hard-coded20:08
dokothe version in the breaks20:08
dbungertnot sure but I can look in an hour.  if you know the correct answer doko feel free to take action.20:08
bandalihi vorlon, thanks for the tips, appreciate it20:10
bandalii'll keep them in mind and will try to organize my work accordingly20:10
dokodbungert: testing such changes before upload would be good ;p20:12
dokoI'm trying something, can't make it worse20:12
-queuebot:#ubuntu-release- New: accepted libreoffice [amd64] (jammy-backports) [4:7.6.5-0ubuntu0.23.10.1~bpo22.04.1]20:13
vorlondo we need to delete the existing package?20:24
vorlonI guess not; e2fsprogs doesn't have a self-build-dep so doesn't care20:26
dokoso that's my guess: http://launchpadlibrarian.net/719023849/e2fsprogs_1.47.0-2.4~exp1ubuntu1_1.47.0-2.4~exp1ubuntu2.diff.gz20:30
vorlon19 packages needing rebuilt for the revert; includes krb5 which I think is likely where things get hung up currently20:30
-queuebot:#ubuntu-release- New source: runc-app (mantic-proposed/primary) [1.1.12-0ubuntu2~23.10.1]20:30
vorlongoing to go ahead and trigger those rebuilds, which can't hurt (either they build or they get bd-uninstallable failures)20:31
-queuebot:#ubuntu-release- New source: runc-app (focal-proposed/primary) [1.1.12-0ubuntu2~20.04.1]20:31
-queuebot:#ubuntu-release- New source: runc-app (jammy-proposed/primary) [1.1.12-0ubuntu2~22.04.1]20:31
=== mfo_ is now known as mfo
vorlondoko: well, interestingly enough krb5 built fine on armhf switching back to libcom-err2, but has ftbfs on amd64 https://launchpad.net/ubuntu/+source/krb5/1.20.1-5.1build320:51
dokoI saw it. so the versioned provides is necessary, the change in the breaks harmless20:52
* vorlon nods20:52
dokoapw (arighi not here):21:12
doko# Compress kernel modules, on mantic+21:12
dokofind debian/linux-image-6.8.0-18-generic-dbgsym -name '*.ko' -print0 | xargs -0 -n1 -P 4 -r zstd -19 --quiet --rm21:12
dokozstd: ../lib/compress/zstd_opt.c:722: ZSTD_insertBtAndGetAllMatches: Assertion `memcmp(match, ip, matchLength) == 0' failed.21:12
dokoCaught SIGABRT signal, printing stack:21:12
dokoxargs: zstd: terminated by signal 621:12
dokomake: *** [debian/rules.d/2-binary-arch.mk:567: binary-generic] Error 12521:12
dokoso that fails for a different reason :-(21:12
apwdoko, bah it is not our lifetime ... i also pinged him internally, so he is aware of the other issue.21:12
apwdoko, will make sure he knows about this also.21:13
dokoapw: looks like it's optional, so can be worked around by not compressing for a first build ...21:17
apwdoko, i am sure we have been compressing for a very long time, so dunno why that has exploded today21:18
arighidoko, sorry I was offline and I may have missed some messages, about the zstd error (on the 6.8.0-18 armhf kernel build), I've seen it before, it happens when we're running out of disk space22:06
arighiand sometimes it can be solved by restarting the build... alternatively we could disable zstd compression, but it'd be quite bad to disable compression just because we don't have enough space on the armhf builders22:07
dokoarighi: I figured out how to disable that. I'm building a package in one of my PPAs just to bootstrap bpfcc and bpftrace. but we really need a first build for the tools package.  you could even hack around before that compress line to remove some build stuff that isn't needed anymore. ugly, but it helps22:13
dokowgrant: ^^^ do we have armhf buildds with different disk sizes?22:13
vorlondoko: krb5 rebuilt now against libcom-err2, so everything should be sorted now I think22:20
dokota22:21
dokothat was using my e2fs upload?22:22
vorlonyes22:22
vorlon(it ftbfs with the ubuntu1)22:23
dokogood, it works22:23
vorlonkanashiro: how is the ruby transition coming along?23:41
vorlon(I am reminded to ask because qtwebkit-opensource-src is ftbfs with a ruby issue, sigh)23:42
vorlonlooking at afflib, preexisting ftbfs in Ubuntu but not Debian, part of the t64 transition with reverse-dependencies23:55
=== chris14_ is now known as chris14

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!