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/2023/09/25/lmod_8.6.19-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lucas@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230925&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 mark 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.
Control: severity -1 important Control: retitle -1 lmod: FTBFS: testsuite fails if 'hostname -f' fails This is a testsuite failure, the differing lines are +hostname: Name or service not known and
tags 1052807 - ftbfs thanks El 18/10/24 a las 12:16, Andreas Beckmann escribió: Hello. Actually, this is a bug that Lucas fixed in the collab-qa-tools repository here: https://salsa.debian.org/lucas/collab-qa-tools/-/commit/6d75fa24ecf5f2c9e1378e9d0804190ca56fec82 and was refined a little bit here: https://salsa.debian.org/lucas/collab-qa-tools/-/commit/182d02914edc58fd14293ae9bedb022d2e8e54cb Those fixes are from late 2023-10 and this bug report was filed in late 2023-09, so I'm almost sure that using the current framework, this bug would not have been reported at all. So, I'm dropping the ftbfs tag because IMO this is not a "proper" FTBFS bug. Sorry that this package was undeservedly removed from testing because of this bug. Should not really have happened. [ I'm keeping the bug open because you said it happens in Salsa, but maybe it could be reassigned to some salsa pseudopackage, if any. The problem in AWS was in the images (or their default behavior), and the collab-qa-tools fix was just a workaround. Maybe the nature of the problem in Salsa is similar ]. Thanks.