El 7/1/25 a las 15:57, atzli...@debian.org escribió:
I don't think there is a way to force uploads for experimental to use
also experimental packages in the buildds.
Thanks let I know this.
But I don't very like this policy in experimental.
IMHO, package upload to experimental should build use experimental first.
The problem with that is that experimental has too many breaking packages
(i.e. packages which break other packages), so it is likely that many
packages would not build at all if all build-dependencies are taken
from experimental by default.
Currently, experimental is used as a "staging area", so that people
can test, for example, sid + imagemagick7, or sid + python3.13,
or sid + gettext-0.23.1 as in this case, i.e. one thing at a time,
but not everything at the same time.
In this particular case, I would try creating a branch in
salsa, put experimental in the changelog, and use something
like this:
Build-Depends: gettext (>= 0.23), autopoint (>= 0.23)
Maybe that way Salsa CI can tell you if the package will
work with gettext 0.23.x or not.
If you try that, I would be curious to know the outcome.
(Naturally, we don't want those special build-depends
for the unstable version, it would be only a trick to force
build-dependencies from experimental).
Thanks.
