On Wed, Feb 18, 2026 at 10:05:22AM +0000, Nick Morrott wrote:
>However, despite having DEP-14 enabled in gbp.conf and building from a >branch called debian/experimental, I have to manually include the >experimental distribution name in the sbuild config otherwise the >package gets built against unstable. Perhaps this is expected?Packages targeting experimental are built against unstable. This is correct. Don't try to break it ;).I agree with all of your statements and yet remain somewhat confused... Without "$distribution = 'experimental'" in the sbuild config, the unstable _tarball_ is being selected by default when building a package targetting experimental. This may be the intended behaviour. However, that tarball knows nothing about the experimental repo and the build fails.
(note that in many cases, where you don't actually need deps from experimental, this is fine)
Is it not expected behaviour for a correctly-configured toolchain to automagically pick e.g. the experimental tarball when building from a suitable branch (debian/experimental, and with the changelog targetting experimental?
It's definitely expected behavior.In practice, though, sbuild can't know about your branches, gbp does but for it their names are opaque, and while sbuild probably supports extracting the distribution from the changelog ("If not specified, the default is the first of schroot name or alias that matches $distribution-$arch-sbuild, $distribution-sbuild, $distribution-$arch or $distribution that exists.") normally your changelog has UNRELEASED when you build your WIP package.
Also it seems you were initially asking about autopkgtest, not building.I haven't tried resolving this and don't run autopkgtest locally for uplods targetting experimental (and it seems like running anything locally is out of fashion anyway).
-- WBR, wRAR
signature.asc
Description: PGP signature
