Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35
retitle 486682 [checks/debhelper] warn if wildcards in .install could let a
SONAME bump go unnoticed
Bug#486682: [checks/shared-libs] warn if wildcards in .install could let a
The following commit has been merged in the master branch:
commit ebf65d68dcc7476279676eaed81cce371083cc8e
Author: Russ Allbery r...@debian.org
Date: Sun Jan 11 00:16:34 2009 -0800
Add pre_upstream hook to the test harness
* t/runtests:
+ [RA] Add pre_upstream hook to modify
The following commit has been merged in the master branch:
commit 1c483c8eec1b9bccbb71ca0a319d558df78b58dd
Author: Russ Allbery r...@debian.org
Date: Sun Jan 11 00:16:59 2009 -0800
Add tests for cruft in the upstream source
diff --git a/t/COVERAGE b/t/COVERAGE
index ddc8313..f0e654e 100644
Hi,
On Sonntag, 11. Januar 2009, Russ Allbery wrote:
I didn't see a reply to the above comment (although there was some other
further discussion about restructuring these patterns in Lintian). In the
absence of further information on this, I'm going to assume that Lintian's
current behavior
On Sat, Jan 10, 2009 at 08:27:05PM -0800, Russ Allbery wrote:
Russ Allbery r...@debian.org writes:
Julian Andres Klode j...@jak-linux.org writes:
If only internal debconf questions are used, lintian should not
complain about not using po-debconf. (as these questions are not meant
to be
Holger Levsen wrote:
If you have any more information about what these files are for and are
sure that they should be omitted, please feel free to reopen.
Sadly I don't know mercurial at all, so I cannot give you that information.
File Purpose Should
Package: lintian
Severity: wishlist
hi,
can you please generate an html-output for http://lintian.debian.org which
contains the indices grouped by the severity of the tag types?
cheers,
Chris
--
To UNSUBSCRIBE, email to debian-lint-maint-requ...@lists.debian.org
with a subject of
The following commit has been merged in the master branch:
commit 6a90db7da7c86b7fffd689c28f097d16fbd92653
Author: Russ Allbery r...@debian.org
Date: Sun Jan 11 10:46:17 2009 -0800
Check basic format of .changes files before continuing
* checks/lintian.desc:
+ [RA] Add tag
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35
# via tagpending
#
# lintian (2.1.6) UNRELEASED; urgency=low
#
# * frontend/lintian:
#+ [RA] Check that .changes files have at least a Format key. If not,
#
# Automatically generated email from bts, devscripts version 2.10.35
# via tagpending
#
# lintian (2.1.6) UNRELEASED; urgency=low
#
# * frontend/lintian:
#+ [RA] Check that .changes files have at least a Format key. If not,
# issue malformed-changes-file and skip them. This catches
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35
retitle 511496 [reporting] provide tag list grouped by severity
Bug#511496: Please provide taglists grouped by Severity
Changed Bug title to `[reporting] provide tag list
Processing commands for cont...@bugs.debian.org:
reopen 492626
Bug#492626: lintian: If only internal debconf questions are used, do not report
not-using-po-debconf errors
Bug reopened, originator not changed.
retitle 492626 [checks/po-debconf] don't require po-debconf if all debconf
reopen 492626
retitle 492626 [checks/po-debconf] don't require po-debconf if all debconf
questions are internal
tag 492626 moreinfo
thanks
Julian Andres Klode j...@debian.org writes:
On Sat, Jan 10, 2009 at 08:27:05PM -0800, Russ Allbery wrote:
Russ Allbery r...@debian.org writes:
This is
Processing commands for cont...@bugs.debian.org:
reopen 464837
Bug#464837: [checks/cruft] warn about Mercurial files in upstream source
Bug reopened, originator not changed.
retitle 464837 [checks/cruft] warn about Mercurial files
Bug#464837: [checks/cruft] warn about Mercurial files in
The following commit has been merged in the master branch:
commit e286baf6a895a08206057eee541e728adb4c700c
Author: Russ Allbery r...@debian.org
Date: Sun Jan 11 11:23:00 2009 -0800
Warn about .hgtags files in the diff and source
* checks/cruft{,.desc}:
+ [RA] Warn about
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35
# via tagpending
#
# lintian (2.1.6) UNRELEASED; urgency=low
#
# * checks/cruft{,.desc}:
#+ [RA] Error on CMakeCache.txt files added or modified in the diff.
#
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35
tags 464837 - moreinfo
Bug#464837: [checks/cruft] warn about Mercurial files
Tags were: pending moreinfo
Tags removed: moreinfo
End of message, stopping processing here.
The following commit has been merged in the master branch:
commit ca4afc31b9644b5a7bd1d92c3f12014e8ac31129
Author: Russ Allbery r...@debian.org
Date: Sun Jan 11 11:54:10 2009 -0800
Supress NMU warnings for local packages
* checks/nmu{,.desc}:
+ [RA] Suppress NMU warnings for
# Automatically generated email from bts, devscripts version 2.10.35
# via tagpending
#
# lintian (2.1.6) UNRELEASED; urgency=low
#
# * checks/nmu{,.desc}:
#+ [RA] Suppress NMU warnings for packages with local in the version
# number or local package in the first line of the changelog.
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35
# via tagpending
#
# lintian (2.1.6) UNRELEASED; urgency=low
#
# * checks/nmu{,.desc}:
#+ [RA] Suppress NMU warnings for packages with local in the version
#
Package: lintian
Version: 2.1.3
Severity: wishlist
Hello,
would be nice if Lintian could issue a warning in case someone is listed
in Maintainer: *and* Uploaders: headers. One of them is enough. (In
fact, being listed in both generates a little warning at dinstall time).
Thanks!
--
bye, Joerg
would be nice if Lintian could issue a warning in case someone is listed
in Maintainer: *and* Uploaders: headers. One of them is enough. (In
fact, being listed in both generates a little warning at dinstall time).
Appears that a double listing in maintainer: and uploaders: *is* already
a tag
The following commit has been merged in the master branch:
commit 1e76ebe385840b9bd169d31fc3c7fe89139d296a
Author: Adam D. Barratt a...@adam-barratt.org.uk
Date: Sun Jan 11 23:39:51 2009 +
Warn about duplicated uploaders
* checks/fields{,.desc}:
+ Warn about an individual
Processing commands for cont...@bugs.debian.org:
#lintian (2.1.6) UNRELEASED; urgency=low
#
# * checks/fields{,.desc}:
#+ [ADB] Warn about an individual uploader appearing multiple times
# in Uploaders. Thanks, Joerg Jaspert. (Closes: #511536)
#
package lintian
Ignoring bugs
Raphael Geissert atom...@gmail.com writes:
Although I agree that examples are just examples, I would like to see
this as a pedantic check; because it is nice when all you do is gunzip
and run it out of the box.
So, shall I reopen and assign it to me?
reopen 42936
owner 42936 Raphael
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35
retitle 511536 [checks/fields] detect repetition in the Uploaders field
Bug#511536: lintian: Double listed maintainer
Changed Bug title to `[checks/fields] detect repetition in
Processing commands for cont...@bugs.debian.org:
retitle 511536 [checks/fields] Warn about duplicated Uploaders
Bug#511536: [checks/fields] detect repetition in the Uploaders field
Changed Bug title to `[checks/fields] Warn about duplicated Uploaders' from
`[checks/fields] detect repetition in
Hi,
Attached is an mbox with the patches implementing the --pedantic
options/severity plus a few initial checks.
I'll later write a new method for lib/Tags.pm which should determine whether a
tag would be displayed or not, as to save time in not-to-be-used expensive
checks. More on this and a
Processing commands for cont...@bugs.debian.org:
reopen 42936
Bug#42936: lintian: does not detect incorrect bang paths in gziped files
Bug reopened, originator not changed.
owner 42936 Raphael Geissert atom...@gmail.com
Bug 42936 [lintian] lintian: does not detect incorrect bang paths in
The following commit has been merged in the master branch:
commit dbb0a6ce96f32b0479aed588ff9fb2fec502ece0
Author: Russ Allbery r...@debian.org
Date: Sun Jan 11 21:22:02 2009 -0800
Warn if the Debian diff is entirely empty
* checks/cruft{,.desc}:
+ [RA] Warn if the Debian
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35
# via tagpending
#
# lintian (2.1.6) UNRELEASED; urgency=low
#
# * checks/cruft{,.desc}:
#+ [RA] Error on CMakeCache.txt files added or modified in the diff.
#
# Automatically generated email from bts, devscripts version 2.10.35
# via tagpending
#
# lintian (2.1.6) UNRELEASED; urgency=low
#
# * checks/cruft{,.desc}:
#+ [RA] Error on CMakeCache.txt files added or modified in the diff.
# Thanks, Joerg Jaspert. (Closes: #510957)
#+ [RA] Warn
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35
tags 42936 - wontfix
Bug#42936: lintian: does not detect incorrect bang paths in gziped files
Tags were: wontfix
Tags removed: wontfix
retitle 42936 [checks/scripts] detect
33 matches
Mail list logo
