Hi, On 12/9/25 13:34, Bastian Blank wrote:
On Mon, Dec 08, 2025 at 09:22:47PM +0100, Paul Gevers wrote:Reading the britney2 code, it seems like it's supposed to support this. But obviously if that's true, there is a bug somewhere. Let me try to find it.Why would britney consider uploads with build profiles enabled at all.
britney2 currently doesn't care about build profiles (it strips out build dependencies with build profile annotation). What I meant yesterday with "britney2 seems like it supposed to support it" is that britney checks per binary if the build happened on the buildd and if not the verdict depends on the component.
However, the current implementation uses the component of the source, with an explicit note that source packages in main can build binaries in contrib. If we want to allow the current way of uploading of src:ggml, the change to britney2 looks extremely simple. However, the issue raised by Adrian makes me lean towards the idea that we don't want to do that.
Policy [1] says this about it: """Source packages in main with a mixture of main and contrib binary packages are more complex for archive tooling to handle, and therefore should be limited to situations where it would be inconvenient to split the source package. If it is straightforward to split the source package into a main part and a contrib part that are built separately, then those parts should be represented as separate source packages.
""" and """In particular, source packages in main must not have build dependencies outside main, but the contrib binary packages may have runtime dependencies outside main.
"""I'm reading this as "all build dependencies for binaries built from a source in main must be in main".
Those have all the described problems. Or is this information just missing?
And I'm not seeing the information in either the Sources or Packages files. Paul[1] https://www.debian.org/doc/debian-policy/ch-archive.html#the-main-archive-area
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature