/srv/irclogs.ubuntu.com/2024/12/04/#ubuntu-devel.txt

=== liushuyu1 is now known as liushuyu
tjaaltonhe's off until jan06:19
adrienHey, there have been many build failures due to an issue with gnupg2 during the week-end; I think it's now solved but dozens of builds probably failed. The common error message includes "devscripts : Depends: gnupg but it is not installable or". Is it possible to do large-scale retries of builds? Is there anyone to contact to do that?09:19
adrienTo be clear, I'm not saying to do it right now, I'm just asking at the moment. However, could someone retry this build? https://launchpad.net/ubuntu/+source/vtk9/9.3.0+dfsg1-1.1build2/+build/29342140 We'll see if the issue is effectively solved. Thanks. :)09:20
RikMillsadrien: retried09:22
adrienRikMills: thanks!09:22
jbichaathos: good morning. What are your plans for php version for Ubuntu 25.04? Debian just began their php 8.4 transition12:20
athosjbicha: I will follow Debian. I wish I could be more active in the transition and help unblocking things on their end (the plan was to perform the transition here right away as well). But I am currently working on other stuff ATM, so this is on hold. Cc jchittum12:36
athosjbicha: is anything blocking you ATM?12:36
mateus-moraisHi! Could somebody retry the failed builds for https://launchpad.net/ubuntu/+source/newt/0.52.24-4ubuntu1 please? The ones that failed have no buildlogs13:12
sudipmateus-morais: done13:18
mateus-moraissudip: thank you!13:18
jbichaathos: it's not blocking me, but Debian php-* packages are autosyncing and are unbuildable until we begin the transition13:25
athosack13:58
adrienI'm trying to push the openmpi transition through and due to issues with gnupg2 during the week-end, a number of related packages have failed building on !amd64 ; according to the transition tracker, the first candidate is ruby-mpi: can someone retry the builds of https://launchpad.net/ubuntu/+source/ruby-mpi/0.3.2-4ubuntu2 ? Thanks14:21
adrien(and yes, I'll prepare my core dev application whenever I have some time)14:21
adriennote that the transition tracker lists openmpi at level 1 due to armhf and i386 but that's due to it dropping 32-bit support; as for genomicsdb, the build issue is unrelated to the one that occured during the week-end14:23
ginggsadrien: .14:23
adrienthanks!14:24
ginggsadrien: note that debian has ruby-mpi 0.4.0-1, can you check if it can be synced or merged?14:24
adriensure14:26
adrienafter some confusion, the conclusion is that we cannot: there's an added entry in d/rules that hardcodes "3.1.0" as the ruby version while we're with ruby 3.3 now14:50
ginggsadrien: thanks!14:52
seb128@pilot in15:02
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Oracular | Patch Pilots: seb128
adrienand can someone retry the builds at https://launchpad.net/ubuntu/+source/hypre/2.32.0-2build1 ? the failures are related to libxml2 complaining about building and running with a different library version AFAIU (combined with the fact that some tools/steps/rules look at the presence of anything on stderr and assume failure)15:35
adrienhmmm, no, that's too recent: 5 hours ago; I doubt things have changed in the meantime, so I'm missing something15:35
adrienbut we'll need to do something to ruby-mpi anyway because of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076063 which is fixed in 0.4.0-1 (FTBFS with mpich, so 32-bit arches)16:53
-ubottu:#ubuntu-devel- Debian bug 1076063 in src:ruby-mpi "ruby-mpi: FTBFS with mpich as default MPI implementation on 32 bit architectures: mpi.c:64:13: error: ‘MPI_2COMPLEX’ undeclared (first use in this function); did you mean ‘MPI_COMPLEX’?" [Serious, Fixed]16:53
adrien=> tomorrow16:54
ginggsadrien: ruby-mpi was already removed on armhf in oracular, so it won't block this transition17:16
sudiprpuby-mpi is ftbfs on riscv6417:17
sudips/rpuby-mpi/ruby-mpi/17:17
ginggssudip: that looks the the gnupg2 problem adrien mentioned earlier17:20
sudipyeah. but isn't that fixed?17:20
ginggsi thought it was, but maybe something got another upload17:21
sudipretried again. the riscv64 build of gnupg2 finished just an hour before the last retry.17:28
adrienginggs: oh, I wasn't aware; I had assumed that it was kept along since it could work with mpich, thanks (and thanks sudip for retrying the build too :) )17:29
sudipthe ftbfs of abyss is something else17:31
ginggstsimonq2 dropped the delta when he sync'd abyss17:32
sudipI can add it back if you have not already started17:35
adrienyay, I spammed the php8.4 test on ppc64el using various triggers just so one would eventually pass; I feel slightly ashamed but the arch is problematic :'(17:35
adrien(hopefully libxml2 will migrate and we'll properly get rid of the version difference warning messages)17:36
ginggssudip: i have not started, but i'm actually more interested why abyss builds in debian without the explicit -latomic18:07
sudipginggs: might be because of '-Bsymbolic-functions' which is in Ubuntu builds but not in Debian18:15
seb128@pilot out19:04
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Oracular | Patch Pilots: N/A
adrienlibxml2 is migrating; can someone retry builds in https://launchpad.net/ubuntu/+source/hypre/2.32.0-2build1 ? the architectures that built did so because the build-time tests are disabled there20:04
tsimonq2sudip, ginggs: Happy to sponsor or fix something (abyss) if I broke it via syncpackage -f20:04
adriens/is migrating/has migrated/ (I wrote that two hours ago and was waiting for it to actually be in the apt repository :) )20:04
tsimonq2adrien: looking20:05
tsimonq2adrien: . :)20:05
adrienthanks!20:07
sudiptsimonq2: I have abyss ready to be uploaded with the delta, but just trying to find out first why its not failing in Debian.20:13
tsimonq2sudip: I'll be around for a few hours+, no rush.20:34
adrienhypre failed building again and still has the same libxml2 warnings; I guess it's a dependency that built with another libxml2 version and that is actually consistent with libxml2-dev not being installed during the build so maybe it makes sense to find how it determines that version thing, download all the dependencies, and find out which ones are concerned20:43
adrien(tomorrow)20:43
vpa1977adrien: I'll try to handle it after standup20:44
adrienvpa1977: thanks, I remember you opened bugs on that; note that I'm not 100% sure the warning is the cause of the build failure (but let me check something)20:45
vpa1977https://bugs.launchpad.net/ubuntu/+source/libxml-libxml-perl/+bug/2089307 - just for the reference if we need to do any other no change rebuilds20:45
-ubottu:#ubuntu-devel- Launchpad bug 2089307 in libxslt (Ubuntu) "llibxml-libxml-perl autopkgtest fails due to non-whitelisted output vs libxml 2.12.7+dfsg+really2.9.14-0.2build1" [Undecided, Fix Released]20:45
tsimonq2vpa1977: I don't remember off the top of my head if you have upload perms but I'll offer to sponsor/retry if you need it :)20:45
tsimonq2adrien: ditto20:45
vpa1977tsimonq2: Thank you =)20:46
adrienI just checked hypre's testsuite and it indeed checks if there are any non-empty ".err" files and uses that as a criteria to determine success or failure; which means that libxml2's warning is indeed going to make it consider that a failure20:50
adrien(but again, which one of its dependencies... lots of fun)20:50
vpa1977I have uploaded ncr for hwloc, will retrigger hypre once it builds22:31
tsimonq2Is http://sponsoring-reports.ubuntu.com/ down for everyone, or just me?22:44
arraybolt3Am I the only one who can't sbuild things properly anymore since the latest updates? Trying to build something with `sbuild -d noble-amd64-shm` results in `error: Unmet build dependencies: abc def ghi` (obviously those are placeholder package names). Why is sbuild looking on my host for build dependencies that belong in the schroot?22:45
arraybolt3for avoidance of doubt, I'm on Plucky22:46
arraybolt3or at least my build infra is22:46
arraybolt3ahem, I'm being a bit vague I see. What I usually do when I build a package is:22:48
arraybolt3* cd to the unpacked source package tree22:48
arraybolt3* sbuild -d whatever-amd64-shm22:48
arraybolt3* let sbuild make the source package for me and build it22:48
tsimonq2(I usually do -c instead of -d so it doesn't set the actual distribution to noble-amd64-shm.)22:49
arraybolt3But now I'm getting the error above when I do that. To work around it, I have to cd to the unpacked source package tree, run `debuild -S -d us -uc` to make the source package, and then `sbuild -d whatever-amd64-shm ../my-source-package.dsc`.22:49
tsimonq2arraybolt3: Try purging your schroot and re-making it?22:49
arraybolt3That's a lot of extra typing, cannot tolerate, fix plz kthxbye :P22:49
tsimonq2XD22:50
arraybolt3tsimonq2: it's not the chroot's fault, it's sbuild looking for build deps on my host.22:50
arraybolt3If I use the aforementioned workaround, everything's peachy.22:50
tsimonq2arraybolt3: show logs22:50
* tsimonq2 runs `ssh arraybolt3 cat logs/*`22:50
arraybolt3please hold22:51
arraybolt3and this is a local build silly :P22:51
arraybolt3https://dpaste.com/AL9WKKYBD <-- behold, the logs22:52
arraybolt3(this is for a package I'm building for my job, but this same thing has happened with other packages so this impacts my Ubuntu work too)22:52
tsimonq2When you figure this one out, let me know. Sometimes there's checks done in an earlier stage of debuild which look for build dependencies locally. I *think* it's a packaging/rules thing22:52
arraybolt3ugh, and don't use the workaround I use, it put the build output in the wrong directory and now my source tree and binary artifacts are nicely mixed together22:53
tsimonq2XD22:53
arraybolt3(put everything in a box and shake vigorously, why don't you sbuild?!)22:53
arraybolt3anyway it wasn't doing this just the other day so I'm sure it's a recent change, probably worth a bug report22:54

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