Hi Andreas, On Tue, Jan 24, 2023 at 03:13:29PM +0100, Andreas Beckmann wrote: > One package affected by this is src:reprepro in experimental where > dpkg-checkbuilddeps now rejects db-util:native (which gained > M-A: foreign in bookworm).
The reason to allow :native on M-A:foreign is to ease such transitions. Nothing else. We could always drop :native in such cases. This allowance is a convenience only. > It may be useless to annotate an arch:all B-D package with :native (as > src:reprepro/exoerimental currently does), or does the :native propagate to > the non-arch:all dependencies of the annotated arch:all package? An Arch:all package that isn't M-A:foreign, is implicitly considered to have the "native" architecture (which is defined as the architecture of the dpkg package). All dependencies of Arch:all packages are native regardless of whether it is M-A:foreign or whether the dependency is annotated :native or not. None of this influences the architecture of indirect dependencies. Helmut
