#1011875 golang-github-opencontainers-runtime-tools: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/opencontainers/runtime-tools/api/socket github.com/opencontainers/runtime-tools/cgroups github.com/opencontainers/runtime-tools/error github.com/opencontainers/runtime-tools/filepath github.com/opencontainers/runtime-tools/generate github.com/opencontainers/runtime-tools/generate/seccomp github.com/opencontainers/runtime-tools/specerror github.com/opencontainers/runtime-tools/validate returned exit code 1 #1011875
- Submitter:
- Lucas Nussbaum
- Date:
- 2022-06-24 23:09:03 UTC
- Severity:
- serious
- Tags:
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): The full build log is available from: http://qa-logs.debian.net/2022/05/25/golang-github-opencontainers-runtime-tools_0.9.0+git20220423.g0105384-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lucas@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220525&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Thank you for reaching out. I've been looking into this report and am a bit confused. I'm trying to reproduce it on my laptop, but it builds just fine for me. Can you please help me understand why it would fail on your end?
Hi Reinhard, I just confirmed that it still fails (and that was in a different environment, not on AWS, but still using sbuild). Maybe you can provide your build log? Lucas
Please find the buildlog of my attempt attached to this email As far as I can tell, the tests are executing in the same way as in your logs, but I may be missing something.
Just a hunch, is it possible that your build environment did not have the package 'ca-certificates' present whereas mine does? I wonder whether I need to add 'ca-certificates' to "Build-Depends". What do you think?
Hello, Bug #1011875 in golang-github-opencontainers-runtime-tools reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/golang-github-opencontainers-runtime-tools/-/commit/2a5b1ca2b214bf7ce354492592ebd73788607203 (this message was generated automatically) -- Greetings https://bugs.debian.org/1011875
We believe that the bug you reported is fixed in the latest version of golang-github-opencontainers-runtime-tools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1011875@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reinhard Tartler <siretart@tauware.de> (supplier of updated golang-github-opencontainers-runtime-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) Format: 1.8 Date: Wed, 08 Jun 2022 16:25:54 -0400 Source: golang-github-opencontainers-runtime-tools Architecture: source Version: 0.9.0+git20220423.g0105384-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team <pkg-go-maintainers@lists.alioth.debian.org> Changed-By: Reinhard Tartler <siretart@tauware.de> Closes: 1011875 Changes: golang-github-opencontainers-runtime-tools (0.9.0+git20220423.g0105384-2) unstable; urgency=medium . * Build-depend on ca-certificates, Closes: #1011875 Checksums-Sha1: ef3bb4f6ed05bc402dded78d1dd054f6d03b0009 3249 golang-github-opencontainers-runtime-tools_0.9.0+git20220423.g0105384-2.dsc 673ba4647cea44b5fbfbe91dbc4f610c4b2b6eb1 2724 golang-github-opencontainers-runtime-tools_0.9.0+git20220423.g0105384-2.debian.tar.xz Checksums-Sha256: 132f8945fc1a3a5738c4596b8a90a69c842de3422cbfea24c240c6613c98a54c 3249 golang-github-opencontainers-runtime-tools_0.9.0+git20220423.g0105384-2.dsc 81f1893783b93dba02b84de2316aa0c3429211a3ab8b91ed37c402f6e0bccdc7 2724 golang-github-opencontainers-runtime-tools_0.9.0+git20220423.g0105384-2.debian.tar.xz Files: 9bfd90589c3376f122011ab407ddc240 3249 devel optional golang-github-opencontainers-runtime-tools_0.9.0+git20220423.g0105384-2.dsc e65e54269e9e23e1ea902cf5c2341669 2724 devel optional golang-github-opencontainers-runtime-tools_0.9.0+git20220423.g0105384-2.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmKhBp4UHHNpcmV0YXJ0 QHRhdXdhcmUuZGUACgkQSadpd5QoJsu3qRAAii94ZLFz9l5O0JX2arBBEHwWVSGN 8nZ7o5fdIeA4TqmScPFzbB6pCXKqxiKzfFpZPFowSojqO6+56NH06o/8l9y4tjBl uyOESor0HpO4di3q6KBV4QKsK8RGwFohmWfLYyPcGs0kbNG5TeEV+PngNNbqzu6u MJ0CjBp+WYA/4RwT4Ep6TEAFJfZKSIL8yuTPthV+EASKqPgd5EGfKyq+ykCyDJik 4LdOGf2nbCR90LCc5ADmykluCCUsSicYWJYPTKeht6Ecsj+Cr4Yg61hlIcBlJeNu oD0zSm5CIXl2uqyWtUc8pIAkFXOLG/AuK6Dy51A/2MQ4kfTL3ZSw28U16jkutsL5 7ZeaC8hAvN5ZzjDF4fuAZrH+zkDzT9NtqJXFJr/sXSMfwmLrTRAEEm3utPNMcSan HByKSbINdG3UibA3vc6/4kcdwkOpamS9Uxx5X+RgMKHrBCiqjofdY/iDTNZC1H21 uu2hKT/4aT08/aTAUmziyCfwsDut4IISGEjf5kLOUVM5ukuYn/9Umx3wel9MaU+h 7C/mF3McbqiRfo21FDuScWMboosm7/2JCWvDVf2QBox/3RNGMgtxwb3jgKQk7rO4 QLaCsJPdx4K6EMBXPTWj4GjDyk76jYjkJsebmyp0x8oyRSuyWwYLLukY04cU4Wze p5hxLokudp/pXjQ= =1xjL -----END PGP SIGNATURE-----
My hunch might have been correct, the fresh upload did build successfully on buildds. yay!
Hi there. Just a side note: The test fails on my test builds (with the same error as in the original report. Because it relies on having a working network connection. Which it shouldn't do. (my test builds are on a connection that only allows access to a Debian mirror). Cheers, Sven