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

vorlonyou said 'gtksourceview' which is not a source package00:00
vorlonsame issue for gtksourceview300:00
vorlonso, 2 ppa publishing cycles + 1 archive publishing cycle and then we'll have libproxy sorted00:01
dokook, time for me to go to bed then00:01
vorlondoko: I can retrigger gtksourceview* later.  Is there anything after those are built that you also want me to look at?00:01
dokoI have been looking at lablgtk3 (and then frama-c), mrpt, ros-perception-pcl00:07
vorlon        Expected call was not made to mocked function [__wrap_setsockopt]00:13
vorlon\o/00:13
vorlondoko: ack.00:13
vorloninteresting, I can't work out how gvm-libs is actually doing its wrapping of glibc calls00:20
vorlonset (UTIL_TEST_LINKER_WRAP_OPTIONS00:20
vorlon    "-Wl,-wrap,socket,-wrap,setsockopt")00:20
vorlonoh nooo00:20
vorlonthat's horribly non-portable and also beautiful and why am I only learning about it now00:23
-queuebot:#ubuntu-release- New binary: symfony [amd64] (noble-proposed/universe) [6.4.5+dfsg-3ubuntu1] (no packageset)00:50
vorlonjbicha: fyi, the only reason startup-notification's ABI isn't affected by time_t is because someone decided to improperly use an 'unsigned long *' in the API instead of a 'time_t *' for sn_startup_sequence_get_last_active_time().  that causes compiz to ftbfs, which I am now fixing; but the library has a lot of revdeps and maybe others are affected, I don't know yet01:00
vorlonjbicha: not filing a bug because the chances of anybody running a desktop on a 32-bit system in 2038 where this API will *actually* fail are slim to none01:01
vorlonkconfig built; libproxy needs kconfig published, then we can finish that bootstrap01:21
vorlonlol @ ecl building on armhf and riscv64 but no other archs02:52
-queuebot:#ubuntu-release- New sync: sagemath (noble-proposed/primary) [9.5-6ubuntu0.1]02:58
=== chris14_ is now known as chris14
-queuebot:#ubuntu-release- New binary: compiz [amd64] (noble-proposed/universe) [1:0.9.14.2+22.10.20220822-0ubuntu10] (no packageset)03:00
-queuebot:#ubuntu-release- New binary: compiz [ppc64el] (noble-proposed/universe) [1:0.9.14.2+22.10.20220822-0ubuntu10] (no packageset)03:01
-queuebot:#ubuntu-release- New binary: compiz [s390x] (noble-proposed/universe) [1:0.9.14.2+22.10.20220822-0ubuntu10] (no packageset)03:01
-queuebot:#ubuntu-release- New: accepted compiz [amd64] (noble-proposed) [1:0.9.14.2+22.10.20220822-0ubuntu10]03:06
-queuebot:#ubuntu-release- New: accepted compiz [s390x] (noble-proposed) [1:0.9.14.2+22.10.20220822-0ubuntu10]03:06
-queuebot:#ubuntu-release- New: accepted compiz [ppc64el] (noble-proposed) [1:0.9.14.2+22.10.20220822-0ubuntu10]03:06
vorlondoing a round of NBS removals from -proposed... mostly library packages with pre-t64 names03:14
-queuebot:#ubuntu-release- New binary: compiz [amd64] (noble-proposed/universe) [1:0.9.14.2+22.10.20220822-0ubuntu11] (no packageset)03:22
-queuebot:#ubuntu-release- New binary: compiz [ppc64el] (noble-proposed/universe) [1:0.9.14.2+22.10.20220822-0ubuntu11] (no packageset)03:24
-queuebot:#ubuntu-release- New binary: compiz [s390x] (noble-proposed/universe) [1:0.9.14.2+22.10.20220822-0ubuntu11] (no packageset)03:24
-queuebot:#ubuntu-release- New: accepted compiz [amd64] (noble-proposed) [1:0.9.14.2+22.10.20220822-0ubuntu11]03:43
-queuebot:#ubuntu-release- New: accepted compiz [s390x] (noble-proposed) [1:0.9.14.2+22.10.20220822-0ubuntu11]03:43
-queuebot:#ubuntu-release- New: accepted compiz [ppc64el] (noble-proposed) [1:0.9.14.2+22.10.20220822-0ubuntu11]03:43
-queuebot:#ubuntu-release- New: accepted sagemath [sync] (noble-proposed) [9.5-6ubuntu0.1]03:43
vorlonhallelujah, curl built on armhf without any new bootstrap loops04:30
-queuebot:#ubuntu-release- New: accepted curl [arm64] (noble-proposed) [8.5.0-2ubuntu7]04:30
-queuebot:#ubuntu-release- New: accepted curl [armhf] (noble-proposed) [8.5.0-2ubuntu7]04:30
vorlonwell, scotch has a preexisting ftbfs (buffer overflow in testsuite) that blocks sundials -> octave; cool, cool04:39
vorlon/usr/include/x86_64-linux-gnu/bits/string_fortified.h:59:10: warning: ‘__memset_chk’ specified size between 18446744071562067969 and 18446744073709551615 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=]04:50
vorlonquite04:50
vorlonironically not the test that fails tho04:51
LocutusOfBorgdoko, no idea about nodejs :) I'm not actively retrying or deleting any build05:59
vorlonLocutusOfBorg: 15:35 < vorlon> doko: the in-archive one is cancelled, the bootstrap ppa one is published06:02
LocutusOfBorgvorlon, time to do curl NCR?06:09
LocutusOfBorgI see lots blocked by it...06:09
vorlonLocutusOfBorg: doing right now06:09
LocutusOfBorgnice thanks!06:09
LocutusOfBorgquestion, I see some packages having hardcoded runtime depencies on old packages06:09
LocutusOfBorgis it ok to 0 day NMU in debian?06:10
vorlonI'm not the authority on this06:10
vorlonbut I would do it06:10
LocutusOfBorgI'll HFDI :)06:21
LocutusOfBorg*JFDI06:21
LocutusOfBorgbtw please welcome our new nodejs upload!06:21
LocutusOfBorgI'm afk for a couple of days, today llvm-18 should finish build on riscv64, and then doxygen become finally buildable06:25
vorlonexcellent06:26
vorlonLocutusOfBorg: uh I see llvm-toolchain-14 being rebuilt for libcurl4t64; do I need to put a stay on llvm-toolchain-18 to let riscv64 build?06:32
LocutusOfBorgyes please06:33
LocutusOfBorgso we unblock doxygen?06:33
LocutusOfBorgalso, in 2 days, newer llvm-18 will come from Debian, so maaaaaaaaaaaybe we can avoid a build06:34
vorlonwell we can't avoid needing a build on armhf in the meantime06:34
vorlonanyway, ok I'll pull llvm-18 back after it's accepted, so the riscv64 build can make it through (I can't sanely interrupt my mass rebuild script to stop it from being uploaded)06:35
LocutusOfBorgthanks!06:36
LocutusOfBorgonce doxygen is built, you can probably copy back and do whatever is needed06:37
LocutusOfBorgbtw, please remove snort on ppc64el. Missing build dependencies: libluajit-5.1-dev06:37
LocutusOfBorgthis is spot on NCR for libdaq206:37
vorlonhow did we still have any ppc64el binaries left referencing luajit06:39
vorlonFri, 03 Dec 202106:40
vorlon:/06:40
vorlonoh; we don't though06:41
LocutusOfBorgoh, when we remove a binary we should do a NCR, otherwise launchpad will fail to show that the binary is not there anymore06:44
vorlonit shows it at https://launchpad.net/ubuntu/noble/ppc64el/snort06:49
vorlon(and the removal here: https://launchpad.net/ubuntu/kinetic/ppc64el/snort)06:50
-queuebot:#ubuntu-release- Unapproved: s390-tools (noble-proposed/main) [2.31.0-0ubuntu3 => 2.31.0-0ubuntu3] (core)07:21
-queuebot:#ubuntu-release- New binary: nodejs [amd64] (noble-proposed/universe) [18.19.1+dfsg-6ubuntu1] (kubuntu)07:27
-queuebot:#ubuntu-release- Unapproved: rejected s390-tools [s390x] (noble-proposed) [2.31.0-0ubuntu2]07:29
-queuebot:#ubuntu-release- Unapproved: accepted s390-tools [s390x] (noble-proposed) [2.31.0-0ubuntu3]07:29
vorlonllvm-toolchain-18 rolled back as discussed to let riscv64 build complete07:31
vorlonmight as well leave the riscv64 build of the next version running, so we can copy the new llvm-18 back in in time for it to be accepted07:32
vorlonwell, libproxy needs bootstrapped again for curl, sigh07:34
-queuebot:#ubuntu-release- New binary: nodejs [arm64] (noble-proposed/universe) [18.19.1+dfsg-6ubuntu1] (kubuntu)07:52
-queuebot:#ubuntu-release- New binary: nodejs [ppc64el] (noble-proposed/universe) [18.19.1+dfsg-6ubuntu1] (kubuntu)07:52
LocutusOfBorgvorlon, dpkg uploaded08:01
LocutusOfBorgthe diff is really minimal except for documentation and adding back files autogenerated to keep delta small08:03
LocutusOfBorgplease fixup in case something bad happens, I won't be at laptop for 24h or so08:05
vorlonhave queued up a clean rebuild of libproxy in the ppa following a bootstrap build which is currently awaiting publishing; when that succeeds it'll be copied back to the archive and I've queued up rebuilds for the wxwidgets3.2 stack after that as well as gtksourceview308:05
vorlonLocutusOfBorg: ok. I won't be at the laptop for 6 hours or so starting around now ;P08:05
LocutusOfBorg:D08:07
LocutusOfBorgg night08:07
-queuebot:#ubuntu-release- New binary: nodejs [s390x] (noble-proposed/universe) [18.19.1+dfsg-6ubuntu1] (kubuntu)08:29
-queuebot:#ubuntu-release- New binary: nodejs [armhf] (noble-proposed/universe) [18.19.1+dfsg-6ubuntu1] (kubuntu)09:31
tjaaltonvorlon: ack, will remember the next time09:54
-queuebot:#ubuntu-release- New: accepted symfony [amd64] (noble-proposed) [6.4.5+dfsg-3ubuntu1]12:08
dokothat was a lie ;-P "I won't be at the laptop for 6 hours or so starting around now"16:56
dokotesseract needed a rebuild, also git, but tests were failing.16:57
dokowxwidgets built17:02
vorlondoko: 9 hours is close to 617:53
vorlongnuplot finally fixed once wxwidgets3.2 publishes (finished "1 hour ago")18:04
vorlonxerces-c ftbfs because something wants harfbuzz but it's not installed :|18:08
vorlon(only on amd64)18:08
athos7~/1718:11
dokovorlon: please wait with any llvm rebuilds until grpc is published, building with the merged abseil18:12
vorlonoh, glad that grpc is fixed18:13
vorlondoes that impact the llvm build itself?18:13
vorlonyes, build-dep on protobuf-compiler-grpc.  Ok18:14
vorlondoko: I can leave these for you to schedule, if you like?18:14
vorlonI'm going to be afk for another 2 hours starting shortly18:14
vorlonanyway the previous riscv64 build hasn't cancelled yet so I can't do the sourceful copy yet18:15
dokook, I'll prepare these then18:19
vorlondoko: given that grpc takes around 5hours to build on armhf and around 20 hours to build on riscv64, I think it's a good idea to start the armhf build as soon as grpc is published on armhf18:20
vorlonshould be possible to do it in archive, do you think it's safe for me to copy to the archive now and cancel the builds?18:20
vorlonor should we build it in the ppa first18:20
dokoarchive sounds fine18:23
vorlondoxygen building now on riscv64 so not a blocker https://launchpad.net/ubuntu/+source/doxygen/1.9.8+ds-2build318:25
jbichavorlon: gtk4 is broken on ppc64el somehow after the deletion of 4.13.8+ds-0ubuntu3 https://launchpad.net/ubuntu/+source/granite-7/7.4.0-1build2/+latestbuild/ppc64el18:42
-queuebot:#ubuntu-release- Unapproved: yt-dlp (jammy-backports/universe) [2023.11.16-1~bpo22.04.1 => 2024.03.10-1~bpo22.04.1] (no packageset)20:11
vorlonjbicha: I don't recall why we removed that, do you?20:18
vorlonah I think it was unnecessary and was a rebuild triggered incorrectly20:18
vorlonlooking20:18
-queuebot:#ubuntu-release- New binary: nodejs [riscv64] (noble-proposed/universe) [18.19.1+dfsg-6ubuntu1] (kubuntu)20:21
vorlonjbicha: well rmadison didn't show anything wrong but https://launchpad.net/ubuntu/noble/ppc64el/libgtk-4-1 shows that my removal command just deleted something hmmmm20:21
vorlonjbicha: removed the other binaries now20:22
vorlondoxygen built. grpc built for all archs except arm64 and riscv64.  I will copy llvm-toolchain-18 back to the archive in a bit to get the armhf build going asap20:46
vorlondoko: you said you wanted to wait for grpc before building llvm-toolchain-18 but I see you've done a new upload which is now building on all archs?21:18
vorlondoko: so, killing the arm64+riscv64 builds now21:19
dokoit was built on armhf21:24
Eickmeyervorlon: Looks like zita-rev1 needs another NCR against libclthreads2t64.21:28
EickmeyerI can do.21:28
Eickmeyer(it broke Studio)21:29
vorlonEickmeyer: how did it break? because in general the t64 and non-t64 lib names are interchangeable on 64-bit archs and when they're not, it's a bug21:31
vorlonEickmeyer: and I see on amd64 that it's already built against libclthreads2t64 in -proposed21:32
EickmeyerYeah, I'm seeing that too.21:32
vorlondoko: was it only armhf you needed it built on?  Sorry, I didn't understand that, you only said "fixed"21:33
EickmeyerThat's why I hesitated.21:33
EickmeyerLatest Studio build:21:33
EickmeyerThe following packages have unmet dependencies:21:33
Eickmeyer libclthreads2t64 : Breaks: libclthreads2 (< 2.4.2-1.1)21:33
EickmeyerOnly thing that installs that which we seed is zita-rev121:33
vorlonEickmeyer: the error message suggests that's not accurate; for that breaks: message to appear you must have packages that it's trying to seed which depend on both the old and new package names.  Anyway, you can work around this temporarily using the trick of early-seeding libclthreads2t6421:35
EickmeyerYep, sounds like I'll just have to do that and trigger a rebuild. *shrug*21:36
EickmeyerHeh, update excuses still crashes my browser.21:37
dokovorlon: what were the usertags for time_t64 issues in Debian?21:46
Eickmeyervorlon: Early seeding alone didn't do it. I also had to blacklist libclthreads2 *and* libdv4. Had two build failures in a row for failing to do that.22:56
vorlondoko: user debian-arm@lists.debian.org, usertag time-t23:26
vorlonEickmeyer: ack23:26
vorlonslowly working my way up the KDE stack (kio -> kparts -> kmediaplayer&c)23:28
dokovorlon: ta. https://bugs.debian.org/106702123:34
-ubottu:#ubuntu-release- Debian bug 1067021 in src:mrpt "mrpt ftbfs on armhf (32bit time_t64 architecture)" [Serious, Open]23:34
-queuebot:#ubuntu-release- New: accepted nodejs [amd64] (noble-proposed) [18.19.1+dfsg-6ubuntu1]23:48
-queuebot:#ubuntu-release- New: accepted nodejs [armhf] (noble-proposed) [18.19.1+dfsg-6ubuntu1]23:48
-queuebot:#ubuntu-release- New: accepted nodejs [riscv64] (noble-proposed) [18.19.1+dfsg-6ubuntu1]23:48
-queuebot:#ubuntu-release- New: accepted nodejs [arm64] (noble-proposed) [18.19.1+dfsg-6ubuntu1]23:48
-queuebot:#ubuntu-release- New: accepted nodejs [s390x] (noble-proposed) [18.19.1+dfsg-6ubuntu1]23:48
-queuebot:#ubuntu-release- New: accepted nodejs [ppc64el] (noble-proposed) [18.19.1+dfsg-6ubuntu1]23:48

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