MBF: Packages which FTBFS with the nocheck build profile
Hello.
This is to announce that I plan to report bugs in this category
("FTBFS when using the nocheck build profile") on a regular basis for
forky and beyond.
To keep the bug template short, I've created this page explaining how
to reproduce the bugs, and (in some cases) how to fix them:
https://wiki.debian.org/qa.debian.org/FTBFS/Nocheck
In summary, I believe there are two main categories:
- The trivial case: Packages which use <!nocheck> on build-dependencies
that are actually required even when the tests are skipped. The right
fix is to drop <!nocheck>, but this should not be done lightly,
because (for the same package contents) we want as many <!nocheck>
annotations as possible.
- Packages which fail in the install stage because they rely on stuff
which is only created by dh_auto_test. In some cases it is possible
to tweak the build system so that such stuff is created in all cases,
but without running the tests.
If you find a failure pattern different than those two having a
significant number of occurrences, you are welcome to add it to the
wiki page above.
Note that this category of bugs is considered to be RC, as it was
announced here by Paul Gevers, where the rationale for making
those bugs RC is also explained:
https://lists.debian.org/debian-devel-announce/2022/10/msg00004.html
However, for my first MBF of this type aimed at forky, I'm going to
report the bugs initially as "important" and will only raise the
severities after at least two weeks, because there are currently too
many gcc-15 and CMake 4 bugs still open.
The already reported bugs from my last MBF, which may be found here:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-qa@lists.debian.org;tag=ftbfs-nocheck-profile
will receive a ping and the severities will also be raised after at
least two weeks.
Thanks.
Reply to: