NQP 2015.07.2

[Daniel Dehennin]

Daniel Dehennin <daniel.dehennin at baby-gnu.org> writes:

> Could we make the “nqp-m” and “nqp-j” packages “Architecture: all” or
> should we stick with the same architectures as their respective backend?

According to the policy[1]:

    Specifying only all indicates that the source package will only
    build architecture-independent packages.

Peter Green on #debian-mentor confirmed that we should use
“Architecture: all” if we only have arch indep files in packages.

Regards.

NB: I didn't see that NQP was part of the ongoing testing transition
    known as auto-icu[2], I hope pushing into master will not cause any
    kind of trouble.

Footnotes: 
[1]  https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Architecture

[2]  https://tracker.debian.org/pkg/nqp

-- 
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6  2AAD CC1E 9E5B 7A6F E2DF
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 342 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-rakudo-devel/attachments/20150804/ac4b3e12/attachment.sig>