Processed: Re: Bug#872611: lintian: Please warn on package using sensible-utils w/o relationship

Processing control commands: > reopen -1 Bug #872611 {Done: Chris Lamb } [lintian] lintian: Please warn on package using sensible-utils w/o relationship 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need

Bug#872611: lintian: Please warn on package using sensible-utils w/o relationship

Control: reopen -1 Hi! On Tue, 2017-08-22 at 12:30:49 -0700, Chris Lamb wrote: > > Patch is for me incompletewe must use cruft... So partial fix Right, thanks for the partial fix though. :) > Sorry, I don't understand. :) I'm guess because the fix only covers scripts and not compiled

Bug#877802: include file name and line number in output

Package: lintian Version: 2.5.54 Severity: wishlist It would be great if lintian could include the relevant file name and line number in each line of output. That way, users could easily jump to the issue at hand by using their editor’s “compilation mode” (Emacs), quickfix (Vim) or similar

lintian_2.5.54~bpo9+1_amd64.changes ACCEPTED into stretch-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 01 Oct 2017 15:43:44 +0200 Source: lintian Binary: lintian Architecture: source all Version: 2.5.54~bpo9+1 Distribution: stretch-backports Urgency: medium Maintainer: Debian Lintian Maintainers

Bug#877766: lintian: more false positives in copyright-year-in-future

Package: lintian Version: 2.5.54 Severity: normal Hi! The new copyright-year-in-future check is very prone to false-positives. And I doesn't feel like white-listing context is the best way to go around this. :/ ISTM that this check should only be performed on the Copyright field for