Bug#904985: lintian: Check for R packages wrongly set Architecture to any instead all

2018-07-31 Thread Chris Lamb 
tags 904985 + pending
thanks

Implemented in Git, pending upload:

  
https://salsa.debian.org/lintian/lintian/commit/124c32986759de84aee76cdb135edca7267ba304

  checks/fields.desc | 12 +
  checks/fields.pm   |  9 +++
  debian/changelog   |  3 +++
  .../debian/debian/control.in   | 29 ++
  .../debian/debian/r-cran-false-positive.install|  1 +
  .../debian/debian/r-cran-positive.install  |  1 +
  t/tests/fields-r-package-not-arch-all/desc |  7 ++
  t/tests/fields-r-package-not-arch-all/tags |  1 +
  .../upstream/DESCRIPTION   | 19 ++
  9 files changed, 82 insertions(+)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#904985: lintian: Check for R packages wrongly set Architecture to any instead all

2018-07-30 Thread Dylan Aïssi 
Package: lintian
Version: 2.5.94
Severity: wishlist

Hi,
A common mistake in R packaging is to set Architecture to any instead
all [1]. Only R packages with "NeedsCompilation: yes" in their
DESCRIPTION files (Debian Control File format) must be marked any [1].
So, all R packages (r-cran- or r-bioc- or r-other-) with this field
set to "no" must be marked as all and not any.

I fixed a batch of deb R packages but to avoid new one incorrectly
marked any, a lintian test would be great.

Best,
Dylan

[1] https://qa.debian.org/bls/bytag/I-no-compiler-commands.html
[2] 
https://cran.r-project.org/doc/manuals/r-devel/R-exts.html#The-DESCRIPTION-file