On Wed, Dec 10, 2025 at 5:51 PM Santiago Vila <[email protected]> wrote: > On Wed, Dec 10, 2025 at 03:56:20PM -0500, Jeremy Bícha wrote: > > Control: severity -1 normal > > I think this is wrong, because it's a violation of Policy 4.2. > Policy 4.2 is "must" directive.
https://www.debian.org/doc/debian-policy/ch-source.html#package-relationships Debian Policy §4.2 is about build dependencies. Here's the heart of the section: "If build-time dependencies are specified, it must be possible to build the package and produce working binaries on a system with only essential and build-essential packages installed and also those required to satisfy the build-time relationships" The package builds ok as is on Debian's buildds. It also builds for me ok with sbuild. You can build libgusb on your system by using the nocheck build profile. > Moreover, flaky tests are considered RC since trixie, and we already > discussed about this in the gcr4 bug. I am sorry for the gcr situation and that it took so long to resolve. This situation is different as it's not been demonstrated yet that the test is too unreliable for Debian's purposes. We don't have enough information about why your system is different and your simple patch (don't run the test in the official Debian build) isn't necessarily something Debian maintainers should be eager to accept. https://tests.reproducible-builds.org/debian/history/libgusb.html Thank you, Jeremy Bícha
