[04:34] mwhudson: not sure I had seen it before but it looks perfect, thanks :) === cpaelzer_ is now known as cpaelzer [10:37] I didn't configure my PPA for vtk9-related stuff with -proposed last week and got an ftbfs for gdcm as a result; I'm hopeful I can get the package to build today and that should open up vtk9 to migrate and therefore opencascade and maybe petsc too [11:14] @pilot in === 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-Noble | Patch Pilots: waveform [13:18] I'm looking for a sponsor for https://code.launchpad.net/~adrien/ubuntu/+source/gdcm/+git/gdcm/+merge/467594 so that the long chain of vtk9/opencascade/petsc migrations can start being unravelled [14:02] adrien, I see that's a universe package -- I'm just working through the (quite long) sponsoring queue at the moment but I'll try and take a look before my shift ends [14:07] waveform: yes, it's universe but it's involved in blocking three transitions and around 30 packages, maybe more :D [14:07] yeah, I was mainly commenting on universe because I can upload that ;) [14:07] waveform: anyway, thanks, and no hurry: there are several other packages after this one and they all take ages to build because they're all C++ with templates :P [14:08] oh, didn't remember you weren't core dev! [15:21] does anyone know why squid-deb-proxy does this? "launchpad personal package archives (disabled by default) [15:22] I think this gives me a 403 and therefore I needed to completely disable the proxy (until I understood the issue) [15:25] adrien I simply uncommented all PPA-related lines from the conf file after the line that says "disabled by default" and never really had an issue [15:42] I don't really understand the reason; and also, it's launchpadusercontent, not launchpad; and I can confirm that was the source of my 403 (I was confused at first because LP also gave an error when the repo didn't exist yet and I thought it had been cached!) [15:55] well, new kind of error with camitk: "c++: fatal error: environment variable ‘DPKG_BUILDPACKAGE_PACKAGE_ARCH’ not defined", which I think is due to some spec file [16:11] dpkg-buildpackage is setting that env var [16:11] is something in that package build process clearing out env vars? [17:13] @pilot out === 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-Noble | Patch Pilots: N/A [18:00] bluca: good question, no idea; and I checked https://ubuntu.dcln.fr/update_excuses.html#dpkg , there are several failures during tests but it seems there may be even more during package build [18:05] this is introduced by https://lists.ubuntu.com/archives/ubuntu-devel/2024-June/043023.html and there is an opt-out available, but root-causing would be better than adding workarounds [18:32] yup, saw that and I might actually use it at least as a first step (there are already too many vtk9 9.3-related failures) [18:33] and I'm not sure how to tackle the issue, I'm not sure this would be the right place [18:34] just from tests, I see cmake, go and autoconf having troubles so I'm wondering if using the environment is reliable enough [18:56] it was in fedora [18:58] and I have used it in debian in packages using cmake, like rpm [19:09] my point is that there are errors in at least three different settings so it seems pretty widespread and maybe not related to a specific build system [19:10] yeah it's more likely related to d/rules [21:09] can anyone please click on this link - https://autopkgtest.ubuntu.com/request.cgi?release=oracular&package=r10k&arch=amd64&trigger=r10k%2F4.0.2-1ubuntu1~ppa1&ppa=sudipmuk%2Ftest-ppa [21:12] adrien, bluca: which packages are affected by this? === john-cabaj1 is now known as john-cabaj [22:29] sudip: done. Test queued [22:29] https://autopkgtest.ubuntu.com/running#pkg-r10k [22:33] bdrung, adrien, bluca: https://lists.ubuntu.com/archives/ubuntu-devel/2024-June/043035.html fwiw [22:58] tsimonq2: Thank you for sponsoring the ruff sync! However because the package is in the sync blocklist so it seems like we still need an AA to get the package removed from the list in order for the sync to get through