Hi, I don't think it's a good idea to create a pedantic warning when a package declares Multi-Arch:no. Some packages just cannot technically be multiarched. Such a package should set Multi-Arch:no explicitly to indicate that the maintainer looked at the problem of multiarching their binary package and decided that the right multiarch value is "no".
If this was widely adapted, then we could have an archive wide check about which packages have been converted to multiarch (or decided that they cannot be multiarched) and which ones still need to be decided upon. Such information would be useful for cross building where multiarching of packages is important. If a binary package explicitly sets Multi-Arch:no then a maintainer could quickly decide that a certain other source package cannot be cross built instead of first looking into multiarching said binary package. So if anything I'd put a pedantic warning if the Multi-Arch field is *not* explicitly set. But I agree that this needs wider discussion, so probably the best course of action is to not do anything until that discussion happened. cheers, josch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
