[SCM] Debian package checker branch, master, updated. 2.3.1-6-g43dc297

The following commit has been merged in the master branch: commit 43dc297502bebe2584f47d2ea88800fced448dcc Author: Russ Allbery Date: Sun Jan 3 20:49:49 2010 -0800 Improved checks for architectures in build relations * checks/fields{,.desc}: + [RA] Reject "all" and "any" in a

Re: lintian.d.o upgraded to 2.3.1

Raphael Geissert writes: > Russ Allbery wrote: >> Since then, though, the new NEWS.Debian check has a Perl warning bug. >> :/ I hate leaving those alone, so now I'm tempted to upload 2.3.2 with >> that fix and whatever else we have time for in the next couple of days. > Okay. I probably won't co

Re: lintian.d.o upgraded to 2.3.1

Russ Allbery wrote: > > Since then, though, the new NEWS.Debian check has a Perl warning bug. :/ > I hate leaving those alone, so now I'm tempted to upload 2.3.2 with that > fix and whatever else we have time for in the next couple of days. > Okay. I probably won't commit much then, as I will b

Re: lintian.d.o upgraded to 2.3.1

Raphael Geissert writes: > Russ Allbery wrote: >> I think this version should be good for propagation into testing unless >> something urgent crops up, so I'm tentatively planning the next release >> for the 16th, depending on whether we've accumulated enough changes by >> then to make it worth i

Bug#563585: Use of uninitialized value $next in pattern match (m//) at /usr/share/lintian/checks/changelog-file line 179, line 6.

Hi Russ On Sun, Jan 03, 2010 at 02:34:26PM -0800, Russ Allbery wrote: > Salvatore Bonaccorso writes: > > > Checking a package (in my case dh-make-perl and libmodule-build-perl) > > I get a warning from lintian: > > > Use of uninitialized value $next in pattern match (m//) at > > /usr/share/lint

Re: lintian.d.o upgraded to 2.3.1

Russ Allbery wrote: > I've upgraded lintian.d.o to 2.3.1, but I haven't regenerated the entire > archive. This means that the warnings about upstream man page spelling > errors are still showing as warnings unless a new version of the package > has been uploaded. I can regenerate the archive if

Processed: limit source to lintian, tagging 563585

Processing commands for cont...@bugs.debian.org: > #lintian (2.3.2) UNRELEASED; urgency=low > # > # * checks/changelog-file: > #+ [RA] Avoid Perl warning when the NEWS file ends immediately after > # the most recent entry. (Closes: #563585) > # > limit source lintian Limiting to bugs wi

Bug#563585: Use of uninitialized value $next in pattern match (m//) at /usr/share/lintian/checks/changelog-file line 179, line 6.

Salvatore Bonaccorso writes: > Checking a package (in my case dh-make-perl and libmodule-build-perl) > I get a warning from lintian: > Use of uninitialized value $next in pattern match (m//) at > /usr/share/lintian/checks/changelog-file line 179, line 6. > It is related to the NEWS file only h

[SCM] Debian package checker branch, master, updated. 2.3.1-5-g015b582

The following commit has been merged in the master branch: commit 015b58286c92871d1454b6996908cc9b6c64c3e9 Author: Russ Allbery Date: Sun Jan 3 14:33:56 2010 -0800 Avoid Perl warning when checking NEWS for a trailing blank line * checks/changelog-file: + [RA] Avoid Perl warni

Bug#563585: Use of uninitialized value $next in pattern match (m//) at /usr/share/lintian/checks/changelog-file line 179, line 6.

Package: lintian Version: 2.3.1 Severity: minor Hi Checking a package (in my case dh-make-perl and libmodule-build-perl) I get a warning from lintian: Use of uninitialized value $next in pattern match (m//) at /usr/share/lintian/checks/changelog-file line 179, line 6. It is related to the NEWS

[SCM] Debian package checker branch, master, updated. 2.3.1-4-gb0c55de

The following commit has been merged in the master branch: commit b0c55def8316710d14febbf7d59b8be8a267dcf2 Author: Russ Allbery Date: Sun Jan 3 13:57:44 2010 -0800 Update copyright dates for 2010 changes diff --git a/debian/copyright b/debian/copyright index a88da3c..ac61c52 100644 --- a/d

lintian.d.o upgraded to 2.3.1

I've upgraded lintian.d.o to 2.3.1, but I haven't regenerated the entire archive. This means that the warnings about upstream man page spelling errors are still showing as warnings unless a new version of the package has been uploaded. I can regenerate the archive if it bothers people, but that t

[SCM] Debian package checker branch, master, updated. 2.3.1-3-gbef51b1

The following commit has been merged in the master branch: commit bef51b1b69dc8cdf9101ad9f32e8f7c5fc49a2a6 Author: Russ Allbery Date: Sun Jan 3 13:44:38 2010 -0800 Really fix display of area for binary packages in HTML reports * reporting/templates/maintainer.tmpl: + [RA] Rea

Re: Changes as first-class objects

Raphael Geissert writes: > But before you start working on it I'd like to bring up one of the > points I mentioned on : why not turn .dsc > files into another file type that lintian checks handle? The scheduler > and the frontend will need to be modified so that .dsc and .changes > files parsing

Processed: limit source to lintian, tagging 563571

Processing commands for cont...@bugs.debian.org: > #lintian (2.3.2) UNRELEASED; urgency=low > # > # * checks/copyright-file: > #+ [RA] Relax the regex for matching dh-make-perl boilerplate to catch > # the current text. Thanks, gregor herrmann. (Closes: #563571) > # > limit source lint

Bug#563571: lintian: copyright-contains-dh-make-perl-boilerplate not triggered with newer dh-make-perl

gregor herrmann writes: > Another option would be to check only for > /This copyright info was automatically extracted/ > which hits both cases and is also what the description for the tag > says :) I think I'll just do that. Thanks! -- Russ Allbery (r...@debian.org)

[SCM] Debian package checker branch, master, updated. 2.3.1-2-gf523a55

The following commit has been merged in the master branch: commit f523a558a48524a508f4547fc4bf24b48beeba39 Author: Russ Allbery Date: Sun Jan 3 13:18:27 2010 -0800 More fixes to dh-make-perl boilerplate check Remove the anchoring of the regex so that it will really match the new

Re: [SCM] Debian package checker branch, master, updated. 2.3.1-1-g01ed4c0

Raphael Geissert writes: > Russ Allbery wrote: >> -if (m/^This copyright info was automatically extracted from the perl >> module\./m) { >> +if (m/^This copyright info was automatically extracted/m) { >> tag 'copyright-contains-dh-make-perl-boilerplate'; >> } > You forgot to remove the ^

Re: [SCM] Debian package checker branch, master, updated. 2.3.1-1-g01ed4c0

Russ Allbery wrote: > > -if (m/^This copyright info was automatically extracted from the perl > module\./m) { > +if (m/^This copyright info was automatically extracted/m) { > tag 'copyright-contains-dh-make-perl-boilerplate'; > } You forgot to remove the ^ character. Cheers, -- Raphael

[SCM] Debian package checker branch, master, updated. 2.3.1-1-g01ed4c0

The following commit has been merged in the master branch: commit 01ed4c0cddcb55dde242d5a7e34079041d888c43 Author: Russ Allbery Date: Sun Jan 3 13:08:28 2010 -0800 Improve the regex for matching dh-make-perl boilerplate * checks/copyright-file: + [RA] Relax the regex for matc

Re: Changes as first-class objects

Russ Allbery wrote: > "Adam D. Barratt" writes: >> On Sun, 2009-12-27 at 00:03 -0800, Russ Allbery wrote: > >>> (The logic of Lintian::Tags will get simpler when we promote changes >>> files to a first-class checkable object with its own check scripts.) > >> Has anyone started working on the nec

Bug#563571: lintian: copyright-contains-dh-make-perl-boilerplate not triggered with newer dh-make-perl

Package: lintian Version: 2.3.1 Severity: minor Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 dh-make-perl creates debian/copyright more or less according to DEP5 since some time. copyright-contains-dh-make-perl-boilerplate checks for /^This copyright info was automatically ext

Re: Bits from the Lintian maintainers

2010/1/3 Osamu Aoki : > On Sat, Jan 02, 2010 at 11:34:53AM -0800, Russ Allbery wrote: [...] > I think Martin Ågren understood the autoconversion script well and has done > hardwork part of manually touching up converted file.  Thanks. I've gone through the document, adding information that went MI

Re: Changes as first-class objects

"Adam D. Barratt" writes: > On Sun, 2009-12-27 at 00:03 -0800, Russ Allbery wrote: >> (The logic of Lintian::Tags will get simpler when we promote changes >> files to a first-class checkable object with its own check scripts.) > Has anyone started working on the necessary modifications for this

Changes as first-class objects [was: Re: RFC: further parallelisation (dependency-based collection and check scripts)]

On Sun, 2009-12-27 at 00:03 -0800, Russ Allbery wrote: > (The logic of Lintian::Tags will get simpler when we promote changes files > to a first-class checkable object with its own check scripts.) Has anyone started working on the necessary modifications for this? It looks mostly straight-forwar

Re: Bits from the Lintian maintainers

Jeremiah Foster writes: > It would be really, really great if someone were to outline how to > add/remove tests from lintian's list of tests. If one could run 'pools' > of tests while using linitian's reporting infrastructure and in-depth > debian knowledge that would be a boon for all those who

Re: Bits from the Lintian maintainers

On Jan 2, 2010, at 18:59, Martin Ågren wrote: > Hi lintian maintainers! > > [I decided not to respect the Reply-To: d-d and instead contact you directly.] > > 2010/1/2 Russ Allbery : >> We're also looking for someone who would like to tackle converting the >> Lintian manual to Docbook instead o

Bug#563495: lintian: please add sparc64 to the list of known architectures

Package: lintian Version: 2.2.18 Severity: wishlist sparc64 is a new architecture that is currently being bootstrapped. It will be added to dpkg soon (see bug#560010, also for the rationale of this port). Could you please also make it known by lintian? -- System Information: Debian Release: squee

Re: Bits from the Lintian maintainers

Hi, (I am noty yet subscribed. Plese CC me) On Sat, Jan 02, 2010 at 11:34:53AM -0800, Russ Allbery wrote: > Wow, two volunteers within a day! That's excellent. I'm replying to this > message since it goes into detail on the conversion process and copying > Osamu Aoki on this message. I'm not