Re: MBF: Packages which FTBFS with the nocheck build profile
On Tue, Sep 30, 2025 at 07:21:52AM +0200, Niels Thykier wrote:
> Could you please provide the template(s) (or drafts thereof) for the bug
> reports as well? Even though they are short, I am still curious about the
> wording.
Sure. I will use this for now, which is the standard I use for regular
FTBFS, plus a link to the wiki, plus a note about raising severities
in two weeks.
[ Note that I will not repeat the mistake of the last time... All the
technical details are in the wiki page now ].
Thanks.
From: {{ email }}
To: Debian BTS <submit@bugs.debian.org>
Subject: {{ source }}: FTBFS with the nocheck build profile
X-Debbugs-Cc: sanvila@debian.org
Package: src:{{ source }}
Version: {{ version }}
Severity: important
Tags: forky sid ftbfs
User: debian-qa@lists.debian.org
Usertags: ftbfs-nocheck-profile
Dear maintainer:
During a rebuild of all packages in unstable using the nocheck build profile,
your package failed to build.
Below you will find how the build ends (probably the most relevant part,
but not necessarily). If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202509/
A wiki page discussing how to reproduce bugs in this category and
possible solutions is available here:
https://wiki.debian.org/qa.debian.org/FTBFS/Nocheck
(It's a wiki, so you are welcome to contribute)
[ Note: This is RC, but I will wait at least two weeks before raising
the severities, there are a lot of gcc-15 and CMake 4 bugs open now ].
About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:{{ source }}, so that this is still
visible in the BTS web page for this package.
Thanks.
--------------------------------------------------------------------------------
[...]
{{ log }}
Reply to: