On Sat, Mar 21, 2020 at 06:44:34PM +0100, Xavier wrote: > OK, but we have many (not all) packages that have a "node-foo could be > marked Multi-Arch: foreign" even if they are installed in > /usr/share/nodejs and Perl packages don't have such "action needed" in > tracker.d.o
Isn't that simply because either: * those perl packages can't be marked m-a:foreign due to their dependencies not being m-a:foreign/m-a:same/m-a:allowed? note that a single arch-dep dependency not marked m-a:same/m-a:allowed will break the m-a:foreign-ness of the binary. * they are already marked m-a:foreign As an example of a perl module with the same warning you are talking about see: https://tracker.debian.org/pkg/libperl-osnames-perl Else, feel free to show me a perl module that is lacking the warning and I can try to deduce why it's missing. > Looking at Perl practices, it seems that "architecture: all" packages > uses only Build-Depends-Indep except for debhelper-compat > > So is this a way to improve multi-arch ? I don't think that's much relevant to multi-arch, no. That said, it's not a bad thing to do :) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
-- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
