Package: dpkg Version: 1.21.9+b1 X-Debbugs-Cc: debian-cr...@lists.debian.org
Hi Guillem, I think dpkg-checkbuildeps should not reject a Multi-Arch: foreign package satisfying a build dependency annotated :native. The internal resolver of sbuild definitely considers this valid and iirc, apt and dose also think this is valid. While it is kinda useless, I see two reasons to allow it. 1. Migrating packages to Multi-Arch: foreign. As packages are not yet fully tagged foreign, maintainers add :native annotations to help cross building. Once their dependency gets annotated foreign, the dependee FTBFS. This makes the transition unnecessarily hard. 2. In some ecosystems, we have a mix of foreign and same packages. This is popular in scripted languages with extension modules. If you need parts of this stack as a build tool, it is far more convenient to just annotate the whole stack :native than checking which of it is modules and which of it is extensions. Hope this makes sense. Ccing to d-cross@l.d.o to get more eyeballs on this. Helmut
