Author: rra
Date: 2007-12-04 09:05:42 +0100 (Tue, 04 Dec 2007)
New Revision: 1038
Modified:
trunk/checks/changelog-file
trunk/checks/changelog-file.desc
trunk/debian/changelog
trunk/testset/non-us/debian/changelog
trunk/testset/non-us/debian/control
Author: rra
Date: 2007-12-04 09:18:01 +0100 (Tue, 04 Dec 2007)
New Revision: 1040
Modified:
trunk/debian/changelog
trunk/man/lintian.1
Log:
+ [RA] Fix a slight spacing problem with the --color flag.
Modified: trunk/debian/changelog
Package: lintian
Severity: minor
Hi
yet another nice check, that should issue a warning:
If something has a dependency against libssl* *and* has GPL in its
copyright file, issue a warning, if you can not also find one of the two
words exception or exemption. That hits about 99% of those cases,
Author: rra
Date: 2007-12-04 09:34:41 +0100 (Tue, 04 Dec 2007)
New Revision: 1041
Modified:
trunk/checks/lintian.desc
trunk/debian/changelog
trunk/frontend/lintian
trunk/testset/manpages/debian/overrides
Log:
+ [RA] Diagnose malformed override entries; don't just ignore them.
+
Processing commands for [EMAIL PROTECTED]:
package lintian
Ignoring bugs not assigned to: lintian
# Fixed in r1038 by rra
tag 449257 + pending
Bug#449257: warn on non-increasing changelog version numbering
There were no tags set.
Tags added: pending
thanks
Stopping processing here.
Please
Micha Lenk [EMAIL PROTECTED] writes:
On Wed, Jun 29, 2005 at 10:23:48PM +0200, Bill Allombert wrote:
I would like to propose that Lintian emits a warning when a source
package (or change files) include circular dependencies between the
generated packages.
I would like to have this lintian
Package: lintian
Version: 1.23.36
Severity: minor
Tags: patch
Hi!
In my package mailman, I have converted two symlinks from relative to
absolute. The relative symlinks gave trouble for a number of different users
that had symlinked the targets themselves, and linking to relative links
gives
Author: rra
Date: 2007-12-04 10:18:03 +0100 (Tue, 04 Dec 2007)
New Revision: 1043
Modified:
trunk/debian/changelog
trunk/frontend/lintian
trunk/lib/Tags.pm
trunk/testset/runtests
trunk/testset/tags.libbaz
trunk/testset/tags.manpages
Log:
+ [RA] Display a summary of overridden
Processing commands for [EMAIL PROTECTED]:
package lintian
Ignoring bugs not assigned to: lintian
# Fixed in r1043 by rra
tag 452804 + pending
Bug#452804: Please add a summary of errors/warnings suppressed by overrides
There were no tags set.
Tags added: pending
thanks
Stopping processing
On 11223 March 1977, Thijs Kinkhorst wrote:
In general, symbolic links within a top-level directory should be relative,
and symbolic links pointing from one top-level directory into another
should be absolute. (A top-level directory is a sub-directory of the root
directory /.)
I read that as
Joerg Jaspert [EMAIL PROTECTED] writes:
On 11223 March 1977, Thijs Kinkhorst wrote:
I read that as it's ok if you have a good reason. Therefore, I think
a lintian warning would be more appropriate than an error. Attached
patch implements this change. Please consider applying it.
That seems
Processing commands for [EMAIL PROTECTED]:
package lintian
Ignoring bugs not assigned to: lintian
# Fixed in r1044 by rra
tag 454239 + pending
Bug#454239: symlink-should-be-relative: warning instead of error
Tags were: patch
Tags added: pending
thanks
Stopping processing here.
Please
Stefano Zacchiroli [EMAIL PROTECTED] writes:
On Tue, Dec 04, 2007 at 01:17:39AM -0800, Russ Allbery wrote:
Let's do this. Let's standardize on:
Ok, cool. Many thanks!
I'll implement the convention PTS side, let me know when the new scheme
is read on the lintian side.
I'll sneak this into
Author: rra
Date: 2007-12-04 22:03:32 +0100 (Tue, 04 Dec 2007)
New Revision: 1045
Modified:
trunk/debian/changelog
trunk/reporting/html_reports
Log:
* reporting/html_reports:
+ [RA] Change the layout of the per-maintainer lintian pages. Now,
each report will be in
Package: lintian
Version: 1.23.34
Severity: normal
Hi
a simple W: for a package ending in -dbg thats not priority extra,
please. Thanks.
Maybe another W: for packages containing /usr/lib/debug/ and do not end
in -dbg.
--
bye Joerg
Some NM:
main contains software that compiles with DFSG.
Author: rra
Date: 2007-12-05 01:35:25 +0100 (Wed, 05 Dec 2007)
New Revision: 1047
Modified:
trunk/checks/control-file.desc
trunk/checks/fields
trunk/debian/changelog
trunk/testset/tags.binary
trunk/testset/tags.cdbs-test
trunk/testset/tags.debconf
trunk/testset/tags.debug
Author: rra
Date: 2007-12-05 01:41:52 +0100 (Wed, 05 Dec 2007)
New Revision: 1048
Modified:
trunk/debian/changelog
trunk/debian/dirs
trunk/man/lintian.1
Log:
* debian/dirs:
+ [RA] Stop creating empty /usr/share/lintian/{overrides,info}
directories. The latter is no longer used and
Author: rra
Date: 2007-12-05 01:43:25 +0100 (Wed, 05 Dec 2007)
New Revision: 1049
Modified:
trunk/debian/changelog
Log:
Update timestamp to take a second shot at a 1.23.37 release.
Modified: trunk/debian/changelog
===
---
Author: rra
Date: 2007-12-05 02:43:37 +0100 (Wed, 05 Dec 2007)
New Revision: 1050
Added:
releases/1.23.37/
Log:
Tag 1.23.37 release.
Copied: releases/1.23.37 (from rev 1049, trunk)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
lintian_1.23.37_i386.changes uploaded successfully to localhost
along with the files:
lintian_1.23.37.dsc
lintian_1.23.37.tar.gz
lintian_1.23.37_all.deb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Accepted:
lintian_1.23.37.dsc
to pool/main/l/lintian/lintian_1.23.37.dsc
lintian_1.23.37.tar.gz
to pool/main/l/lintian/lintian_1.23.37.tar.gz
lintian_1.23.37_all.deb
to pool/main/l/lintian/lintian_1.23.37_all.deb
Override entries for your package:
lintian_1.23.37.dsc - source devel
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452804: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#453417: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#448677: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#454239: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#449257: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#357838: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#451668: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#453302: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#444642: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#447718: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#447718: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#441636: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452839: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#437959: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452336: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#448652: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#409109: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#409109: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#119097: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452316: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#451689: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 05 Dec 2007 01:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#448207: fixed in lintian 1.23.37
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
43 matches
Mail list logo
