Hi, Quoting Ralf Treinen (2014-11-13 21:00:27) > Hm, shouldn't all architecture=all packages be automatically considered as > M-A=foreign ? See also [1]
no this would be incorrect. Arch:all does not mean that the interface the package provides is architecture independent. It only means that the package contains the same data across all architectures. An example for this is the haskell-devscripts package which is Architecture:all and which I thought can also be Multi-Arch:foreign, see #769377 but Helmut Grohne made me aware that the problem is actually much more complex and making the package Multi-Arch:foreign would be wrong. See that bug for more details. Now that I look at it, a similar probably holds for dh-ocaml as well. For example /usr/share/ocaml/ocamlvars.mk calls ocamlc and is thus a test for the build architecture, whereas in a cross setup, these tests should be done for the host architecture instead. So this bug is not that easy to fix and probably has to wait until ocamlc supports cross compilation. cheers, josch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
