Bug#797163: lintian: please warn if Arch:all package is not Multi-Archi: foreign

[Jakub Wilk <jwilk@debian.org>]

Hi Fabian!

* Fabian Greffrath <fabian@debian.org>, 2015-08-28, 13:46:
> > Not every "Architecture: all" package can be marked as "Multi-Arch: 
> > foreign". Otherwise, we could just teach dpkg and APT to treat all 
> > arch:all packages as if they were ma:foreign and be done with it. :)
>
> could you please point me to one example of an Arch:all package that 
> must not get flagged Multi-Arch:foreign?

Python used to be the classic example:
"python" was an arch:all meta-package that depended on "python2.X".
But if a Python module depended on "python", it was because it needed a 
Python interpreter of the same architecture.

A more recent example I run into is zathura-dev, which is incorrectly 
marked as M-A:foreign, which can lead to bogus (build-)dependency 
chains, for example:

src:zathura-extras (DEB_HOST_ARCH=i386) -> zathura-dev -> libgirara-dev:amd64

--
Jakub Wilk