On Sat, Sep 27, 2025 at 08:37:16AM +0200, Paul Gevers wrote: >... > The devref recommends [2] to inform/discuss this on [email protected]. I > recommend you follow the devref recommendation and state your intentions > before doing such a new mass bug filing. I suggest to use some or all of the > text from [1] in both the message to d-devel as well as in your bug reports; > at the very least reference it.
One option would be linking to a wiki page listing common problems and their usual solutions. This is also more updatable than the text of an email. > I'm slightly concerned about good > communications here, because I believe this is delicate. For maintainers, the > trivial way to avoid this RC issue is to no longer annotate Build-Depends with > <!nocheck>, but we are also asking people to actively do that. Your mass bug > filing should not lead to the wrong mindset. That's only one class of bugs. m68k and sh4 build with nocheck for years but do install <!nocheck> build dependencies during the build, and while the resulting number of (so far non-RC) FTBFS bugs filed and fixed for that over the years was not huge it has been a constant source of bugs. There are also non-FTBFS issues regarding nocheck: The contents of the packages must not change with nocheck. Is running tests despite nocheck now RC? > Paul >... cu Adrian
