Re: Bug#903158: Multi-Arch: foreign and -dbgsym: too weak dependency

[Simon McVittie <smcv@debian.org>]

On Sat, 08 Oct 2022 at 11:00:30 +0200, Niels Thykier wrote:
> > > On Sat, 7 Jul 2018 11:40:54 +0300 "Yuriy M. Kaminskiy"
> > > <yumkam+debian@gmail.com> wrote:
> > > > I think (at least, 'Multi-arch: foreign' *and* 'Architecture' != all)
> > > > packages should have explicit parent package arch dependency
> > > >    Depend: foo:${Arch} (=${binary:Version})
> > > > instead of
> > > >    Depend: foo (=${binary:Version})

So as a concrete example, for sed:amd64 (which is Multi-Arch: foreign),
sed-dbgsym:amd64 currently depends on sed (= 4.8-1) which can be satisfied
by sed:i386, and the request is for it to explicitly depend on
sed:amd64 (= 4.8-1) instead?

I was under the impression that the Debian archive does not allow
dependencies with an explicit architecture like this, only the :any
qualifier for M-A: allowed packages (like python3:any). Am I basing this
on outdated information?

Policy §7 doesn't currently document multiarch qualifiers at all.
deb-control(5) documents foo:any and foo:amd64.

    smcv