Bug#760642: lintian: False positive for space-in-std-shortname-in-dep5-copyright with alternative licenses (as common with Perl modules)
control: tags -1 + pending
Already fixed in git.
Bastien
On Wed, Sep 10, 2014 at 9:44 AM, Riley
<BM-2cVqnDuYbAU5do2DfJTrN7ZbAJ246S4Xix@bitmessage.ch> wrote:
> Package: lintian
> Version: 2.5.26
> Followup-For: Bug #760642
>
> I'd also like to point out that "with OpenSSL exception" is also acceptable
> language for d/copyright. (See section "Syntax" under "License specification"
> at https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ )
>
>
>
> -- System Information:
> Debian Release: jessie/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: i386 (i686)
>
> Kernel: Linux 3.13-1-686-pae (SMP w/4 CPU cores)
> Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages lintian depends on:
> ii binutils 2.24.51.20140903-1
> ii bzip2 1.0.6-7
> ii diffstat 1.58-1
> ii file 1:5.19-2
> ii gettext 0.19.2-2
> ii hardening-includes 2.5+nmu1
> ii intltool-debian 0.35.0+20060710.1
> ii libapt-pkg-perl 0.1.29+b2
> ii libarchive-zip-perl 1.38-1
> ii libclass-accessor-perl 0.34-1
> ii libclone-perl 0.37-1+b1
> ii libdpkg-perl 1.17.13
> ii libemail-valid-perl 1.194-1
> ii libfile-basedir-perl 0.03-1
> ii libipc-run-perl 0.92-1
> ii liblist-moreutils-perl 0.33-2+b1
> ii libparse-debianchangelog-perl 1.2.0-1
> ii libtext-levenshtein-perl 0.09-1
> ii libtimedate-perl 2.3000-2
> ii liburi-perl 1.64-1
> ii man-db 2.6.7.1-1
> ii patchutils 0.3.3-1
> ii perl [libdigest-sha-perl] 5.20.0-6
> ii t1utils 1.37-2.1
>
> Versions of packages lintian recommends:
> ii libautodie-perl 2.25-1
> ii libperlio-gzip-perl 0.18-3+b1
> ii perl 5.20.0-6
> ii perl-modules [libautodie-perl] 5.20.0-6
>
> Versions of packages lintian suggests:
> pn binutils-multiarch <none>
> ii dpkg-dev 1.17.13
> ii libhtml-parser-perl 3.71-1+b2
> ii libtext-template-perl 1.46-1
> pn libyaml-perl <none>
> ii xz-utils 5.1.1alpha+20120614-2
>
> -- no debconf information
>
Reply to: