Hi Aquila, * [email protected] <[email protected]> [2026-01-23 06:09]:
That said, one small drawback is that this makes the sbuild invocation grow with the number of injected binaries, since each extra .deb turns into an additional --add-depends entry. It is workable, but can get a bit unwieldy for sources producing lots of binaries.
Agreed. You could create a dependency package to pass all the relations, similar to debootsnap, in devscripts, does it.
If it makes sense from sbuild's perspective, having an opt-in switch to treat --extra-package versions as preferred during build-dep resolution would make this workflow a bit cleaner, while keeping the current default behavior unchanged.
The problem here is that you are using the aspcud solver which, from my tests, does not use the apt pinning mechanism. Is there any reason for it?
Switching to the default, apt, will fix your problem. I am also working on dropping the aspcud (experimental) and aptitude (backports) solver usage in Debian. The apt developers proposed to replace it by apt --no-strict-pinning but I still need to add a proper interface to sbuild for that.
Cheers Jochen
signature.asc
Description: PGP signature
