Hi Jakub, Am Freitag, den 28.08.2015, 11:25 +0200 schrieb Jakub Wilk: > 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? > IME, many people (including past me) have poor understanding what > "Multi-Arch: foreign" means, and if Lintian hinted them they could > add it, they would, even when they shouldn't. Present me too. But I was mildly disturbed when I wanted to install a i386 game package on an amd64 system and that game package pulled in libsdl-mixer1.2:i286 which in turn recommended (among others) the musescore-soundfont-gm:i386 soundfont package (note the Arch identifier), which is Arch:all and only contains files in /usr/share. This was extra disturbing, since I have just NMUd a soundfont package literally minutes before and could have easily added that flag if something (i.e. lintian) just gave me a hint. Cheers, Fabian
Attachment:
signature.asc
Description: This is a digitally signed message part