On Thu, Apr 02, 2026 at 10:37:44AM +0900, Simon Richter wrote:
> https://wiki.debian.org/BuildProfileSpec talks about the idea of using
> release names as build profile names to allow for easier backporting, but
> the table doesn't list them.
Could you describe some use cases for this feature?
In addition to the things others mentioned, this also affects the review
of the backports people, as changes in (build-)deps are not longer
visible in the diff. (Okay, backports allows for alternative build-deps
already, so you also need to look at them)
> Does that already exist, or if it doesn't, would it make sense to implement
> that (basically, "backports autobuilders set -Ptrixie or -Pbookworm")?
This is not even enough, as it would only allow to add build-deps, not
remove them. As mentioned, build profiles are not taken into account in
a lot of parts of the Debian machinery, so with a simple implementation
you could add them like:
| Build-Depends: package <trixie>
But you can't remove them like this:
| Build-Depends: package <!trixie>
But then, why would you name it trixie, if you mean trixie-backports?
We have packages that are updated both to unstable and trixie-security
at the same time. If we start, this use case needs to work as well.
So, it gets complicated pretty fast.
Bastian
--
Insults are effective only where emotion is present.
-- Spock, "Who Mourns for Adonais?" stardate 3468.1
