Re: +1 maintenance report
Hi, Em sex., 21 de out. de 2022 19:47, Sergio Durigan Junior < sergio.duri...@canonical.com> escreveu: > * golang-github-containerd-stargz-snapshotter > - FTBFSing on Ubuntu, but not on Debian, which is strange. > - I've started investigating it but couldn't progress much further > before my EOW. > This one requires a new containerd version to get fixed. The update will happen in the "L" cycle. And this is not reproducible in Debian because our containerd package differs from there. Cheers! Lucas Kanashiro > -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: +1 maintenance report
On Friday, October 21 2022, Steve Langasek wrote: > Hi Sergio, Hello, > On Fri, Oct 21, 2022 at 06:47:09PM -0400, Sergio Durigan Junior wrote: >> * cryfs >> - FTBFS on ppc64el due to RLIMIT_MEMLOCK being too low. >> - After spending some time playing with setrlimit et al, it's clear to >> me that the problem cannot be easily fixed in the source code. I >> believe we will need to increase RLIMIT_MEMLOCK in the ppc64el >> builders. >> - Debian isn't affected by this problem. >> - There's also an s390x dep8 failure, which is also affecting Debian. >> I opened an upstream issue. >> - https://bugs.launchpad.net/ubuntu/+source/cryfs/+bug/1993578 > > Is there any reason not to instead change the package to skip these tests > when RLIMIT_MEMLOCK is too low (which seems detectable)? My initial reason would be that the package is in universe and in sync with Debian. On top of that, after reading #ubuntu-devel's log, it seems like we've encountered similar situations where RLIMIT_MEMLOCK got in the way. As far as I have investigated, these other cases were solved (correctly) by using setrlimit to properly extend RLIMIT_MEMLOCK when needed, but the packages in question had the necessary capabilities to do that. cryfs doesn't. Since cryfs in Debian doesn't suffer from this problem, and given that, based on local experiments, the RLIMIT_MEMLOCK value necessary to trigger this problem seems rather low, I think it's worth at least considering increasing it in our ppc64el builders. Please take the above with more than a grain of salt, since I obviously don't have access to our builders and didn't try to do a deep-dive into how their resource limits are configured. Thanks, -- Sergio GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14 -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: +1 maintenance report
Hi Sergio, On Fri, Oct 21, 2022 at 06:47:09PM -0400, Sergio Durigan Junior wrote: > * cryfs > - FTBFS on ppc64el due to RLIMIT_MEMLOCK being too low. > - After spending some time playing with setrlimit et al, it's clear to > me that the problem cannot be easily fixed in the source code. I > believe we will need to increase RLIMIT_MEMLOCK in the ppc64el > builders. > - Debian isn't affected by this problem. > - There's also an s390x dep8 failure, which is also affecting Debian. > I opened an upstream issue. > - https://bugs.launchpad.net/ubuntu/+source/cryfs/+bug/1993578 Is there any reason not to instead change the package to skip these tests when RLIMIT_MEMLOCK is too low (which seems detectable)? Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
+1 maintenance report
Investigations == * spaln - Upstream (and therefore Debian) dropped support for 32-bit architectures, so the armhf binary had to be removed. - On top of that, there as an FTBFS happening on riscv64 due to LTO. "Fixed" in Debian (with the proper "LP:..." mark). The fix should land in Ubuntu when the archive reopens. - https://bugs.launchpad.net/ubuntu/+source/spaln/+bug/1993202 * cryfs - FTBFS on ppc64el due to RLIMIT_MEMLOCK being too low. - After spending some time playing with setrlimit et al, it's clear to me that the problem cannot be easily fixed in the source code. I believe we will need to increase RLIMIT_MEMLOCK in the ppc64el builders. - Debian isn't affected by this problem. - There's also an s390x dep8 failure, which is also affecting Debian. I opened an upstream issue. - https://bugs.launchpad.net/ubuntu/+source/cryfs/+bug/1993578 * luajit2 - Debian has removed ppc64el from the list of supported architectures for this package. We need to make sure this change is also reflected in Ubuntu. I left a message on #ubuntu-release asking for an AA to act on it. Also filed the bug below, and subscribed ~ubuntu-release. - https://bugs.launchpad.net/ubuntu/+source/luajit2/+bug/1993752 * loggerhead - Filed a bug against the Debian package and provided a patch to fix the current autopkgtest issue. - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022140 - Also update the details on our bug: - https://bugs.launchpad.net/debian/+source/loggerhead/+bug/1991613 * osslsigncode - FTBFS on s390x; tests failing due to endianess. There a Debian and an upstream bugs filed for this, and an upstream PR is open. I filed a bug on our side to keep track of this. - https://bugs.launchpad.net/ubuntu/+source/osslsigncode/+bug/1993757 * bpftrace - FTBFS because one of the binaries isn't being compiled. This doesn't affect Debian. - I tracked it down to a missing bpftool binary package in the archive. This has been reported already. - https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/1981089 - Added bpftrace as one of the affected packages in the bug above. * ipykernel - FTBFS on amd64 due to missing dependency: python3-debugpy. - python3-debugpy is FTBFSing as well, including on Debian. - Filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022188. - Also: https://bugs.launchpad.net/ubuntu/+source/debugpy/+bug/1993849. * resampy - Failing to test on s390x, possibly due to endianess. - This has been reported against Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019101 - The Debian maintainer said he's waiting to obtain access to a porterbox so that he can work on this. I will contact him and see if I can help in any way. - I filed our own bug to keep track of the failure. - https://bugs.launchpad.net/debian/+source/resampy/+bug/1993858 * golang-github-containerd-stargz-snapshotter - FTBFSing on Ubuntu, but not on Debian, which is strange. - I've started investigating it but couldn't progress much further before my EOW. Misc Some retriggers here and there, nothing really important. -- Sergio GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14 -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
