Current versions of sbuild (I'm looking at 0.62.5-1ubuntu2) have changed how the apt resolver works. It now creates a dummy package whose dependencies match the build-depends of the package being built, puts that dummy package into an apt repository, adds the apt-repository to the sources.list, and installs the dummy package using apt.
Using a resolver with that behavior would fix this bug, so we may not need to use a different resolver on different pockets. I think this makes Adam's (1) the right long-term solution.
But given recent discussion, I don't think people generally have well-formed expectations of how the backports pocket *should* work (see the most recent Tech Board meeting, for example). I would prefer that we override NotAutomatic on builds in the backport pocket quickly than fix the resolver slowly, since that would be consistent with past behavior on backports builds.
Current versions of sbuild (I'm looking at 0.62.5-1ubuntu2) have changed how the apt resolver works. It now creates a dummy package whose dependencies match the build-depends of the package being built, puts that dummy package into an apt repository, adds the apt-repository to the sources.list, and installs the dummy package using apt.
Using a resolver with that behavior would fix this bug, so we may not need to use a different resolver on different pockets. I think this makes Adam's (1) the right long-term solution.
But given recent discussion, I don't think people generally have well-formed expectations of how the backports pocket *should* work (see the most recent Tech Board meeting, for example). I would prefer that we override NotAutomatic on builds in the backport pocket quickly than fix the resolver slowly, since that would be consistent with past behavior on backports builds.