Bug#901228: lintian: False positive for "r => littler (usr/lib/R/site-library/rjson/rpc_server/server.r) #!/usr/bin/r"
Package: lintian
Severity: normal
Hi,
https://lintian.debian.org/maintainer/r-pkg-team@alioth-lists.debian.net.html#r-cran-rjson
shows
E missing-dep-for-interpreter
r => littler (usr/lib/R/site-library/rjson/rpc_server/server.r) #!/usr/bin/r
r => littler (usr/lib/R/site-library/rjson/rpc_server/server.r) #!/usr/bin/r
That's a false positive since r-cran-rjson depends r-cran-littler which
provides /usr/bin/r.
Thanks for maintaining lintian
Andreas.
-- System Information:
Debian Release: 9.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-5-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages lintian depends on:
ii binutils 2.28-5
ii bzip2 1.0.6-8.1
pn diffstat <none>
ii dpkg 1.18.24
ii file 1:5.30-1+deb9u1
pn gettext <none>
pn intltool-debian <none>
ii libapt-pkg-perl 0.1.32
pn libarchive-zip-perl <none>
pn libclass-accessor-perl <none>
pn libclone-perl <none>
ii libdpkg-perl 1.18.24
pn libemail-valid-perl <none>
pn libfile-basedir-perl <none>
pn libipc-run-perl <none>
ii liblist-moreutils-perl 0.416-1+b1
pn libparse-debianchangelog-perl <none>
ii libperl5.24 [libdigest-sha-perl] 5.24.1-3+deb9u3
pn libtext-levenshtein-perl <none>
ii libtimedate-perl 2.3000-2
ii liburi-perl 1.71-1
pn libxml-simple-perl <none>
pn libyaml-libyaml-perl <none>
ii man-db 2.7.6.1-2
pn patchutils <none>
ii perl 5.24.1-3+deb9u3
pn t1utils <none>
ii xz-utils 5.2.2-1.2+b1
Versions of packages lintian recommends:
ii dpkg 1.18.24
pn libperlio-gzip-perl <none>
ii perl 5.24.1-3+deb9u3
ii perl-modules-5.24 [libautodie-perl] 5.24.1-3+deb9u3
Versions of packages lintian suggests:
pn binutils-multiarch <none>
pn dpkg-dev <none>
ii libhtml-parser-perl 3.72-3
ii libtext-template-perl 1.46-1
Reply to: