Bug#729096: lintian: new policy version 3.9.5 available
Package: lintian
Version: 2.5.19
Severity: normal
Dear Maintainer,
the new policy version 3.9.5 was released on 2013-01-22. I was just building my
package for that version, but lintian does not know of it yet:
> Now running lintian...
> W: rohieb.name-repo-keyring source: newer-standards-version 3.9.5 (current is 3.9.4)
$ apt-cache policy debian-policy
debian-policy:
Installed: 3.9.5.0
Candidate: 3.9.5.0
Version table:
*** 3.9.5.0 0
500 http://debian.tu-bs.de/debian/ testing/main amd64 Packages
1 http://ftp2.de.debian.org/debian/ sid/main amd64 Packages
100 /var/lib/dpkg/status
Thanks for looking into this.
-- System Information:
Debian Release: jessie/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'testing'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.10-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lintian depends on:
ii binutils 2.23.90.20131017-1
ii bzip2 1.0.6-5
ii diffstat 1.57-1
ii file 1:5.14-2
ii gettext 0.18.3.1-1
ii hardening-includes 2.4
ii intltool-debian 0.35.0+20060710.1
ii libapt-pkg-perl 0.1.29+b1
ii libarchive-zip-perl 1.30-7
ii libclass-accessor-perl 0.34-1
ii libclone-perl 0.35-1
ii libdpkg-perl 1.16.12
ii libemail-valid-perl 1.192-1
ii libfile-basedir-perl 0.03-1
ii libipc-run-perl 0.92-1
ii liblist-moreutils-perl 0.33-1+b2
ii libparse-debianchangelog-perl 1.2.0-1
ii libtext-levenshtein-perl 0.06~01-2
ii libtimedate-perl 1.2000-1
ii liburi-perl 1.60-1
ii man-db 2.6.5-2
ii patchutils 0.3.2-2
ii perl [libdigest-sha-perl] 5.18.1-4
ii t1utils 1.37-2
Versions of packages lintian recommends:
pn libperlio-gzip-perl <none>
ii perl-modules [libautodie-perl] 5.18.1-4
Versions of packages lintian suggests:
pn binutils-multiarch <none>
ii dpkg-dev 1.16.12
ii libhtml-parser-perl 3.71-1+b1
ii libtext-template-perl 1.46-1
ii xz-utils 5.1.1alpha+20120614-2
-- no debconf information
Reply to: