On 2011-08-12 18:03, Russ Allbery wrote:
Niels Thykier ni...@thykier.net writes:
Other improvements
==
These days Lintian
^^^
(Fixed a typo, thanks to Jakub Wilk)
* processes related packages together
Since 2.5.0~rc3 Lintian has grouped related
Hi
See attached document; comments welcome :)
~Niels
Topics:
- Vendor profiles
- Configuration file changes
- Changes to Lintian options
- Other improvements
- Known bugs and issues
- Help us help you
Vendor Profiles
===
Starting with version 2.5.2, Lintian can now be
Niels Thykier ni...@thykier.net writes:
* processes related packages together
Since 2.5.0~rc3 Lintian has grouped related packages and processed
them together. With this Lintian can now do things like check if a
manpage is in a direct dependency.
...in a direct dependency
On Aug 12, 2011, at 18:03, Russ Allbery wrote:
Niels Thykier ni...@thykier.net writes:
This otherwise looks great to me.
And on a personal note, thank you *so* much for all the work that you've
been doing on Lintian. I've often had the experience with other open
source projects of
Jeremiah Foster jerem...@jeremiahfoster.com writes:
I've got a question regarding the various lintian modules. I'm a command
line person and often use tools like perldoc to read the documentation
that is in with code. Lintian does seem to use plain old documentation
very much which I think is
On Aug 12, 2011, at 21:36, Jeremiah Foster wrote:
I've got a question regarding the various lintian modules. I'm a command line
person and often use tools like perldoc to read the documentation that is in
with code. Lintian does seem to use
I meant doesn't of course. :}
plain old
Russ Allbery wrote:
debhelper and didn't have this dependency will now get a warning. We're
currently deciding whether to teach Lintian that ${misc:Depends} isn't
needed in this specific case or to just uniformly recommend the
${misc:Depends} dependency for all packages using debhelper.
The
Joey Hess jo...@debian.org writes:
Russ Allbery wrote:
debhelper and didn't have this dependency will now get a warning.
We're currently deciding whether to teach Lintian that ${misc:Depends}
isn't needed in this specific case or to just uniformly recommend the
${misc:Depends} dependency for
[ Any mistakes, or anything else I should mention? ]
New Team Member
===
The best news about Lintian is that Raphael Geissert has joined the team
as an additional Lintian maintainer. Raphael has been making suggestions
and contributing patches to Lintian since 2007 and has done a
Russ Allbery wrote:
[ Any mistakes, or anything else I should mention? ]
What about including the usual we welcome more contributors? :)
New Team Member
===
The best news about Lintian is that Raphael Geissert has joined the team
as an additional Lintian maintainer.
Heh,
On Fri, 2009-02-06 at 19:04 -0800, Russ Allbery wrote:
[ This is a draft of a post I'd like to send to debian-devel-announce.
Take a look and let me know if anything is wrong or missing. Thanks! ]
Thanks for that; I don't have think I have anything specific to add that
wasn't on Raphael's
Adam D. Barratt a...@adam-barratt.org.uk writes:
(fwiw, I've never really liked as good of a blah, but that could be an
en_US vs en_GB thing).
No, you're right, it's a sloppy construct. I reworded it.
We're also looking for someone who would like to tackle converting the
Lintian manual in
Russ Allbery wrote:
[ This is a draft of a post I'd like to send to debian-devel-announce.
Take a look and let me know if anything is wrong or missing. Thanks! ]
Current Status
==
[...]
Maybe it should be mentioned how many checks there were in etch's lintian,
how many in
[ This is a draft of a post I'd like to send to debian-devel-announce.
Take a look and let me know if anything is wrong or missing. Thanks! ]
Current Status
==
Since the lenny freeze began, we've been working on incorporating major
changes in preparation for squeeze, including (as
Marc 'HE' Brockschmidt [EMAIL PROTECTED] writes:
FWIW, two years ago (?) Jeroen, djpig and I had a discussion about
this. The basic idea back then was the same as you describe now: Move
away from E, W and I and use two letters to indicate the two
different measurements are represented:
(i)
Russ Allbery [EMAIL PROTECTED] writes:
* Provide a way to more clearly indicate Lintian's certainty, the severity
of the problem, and the source of the rule that Lintian is checking,
rather than always collapsing that information into a simple three-level
error/warning/info hierarchy.
16 matches
Mail list logo
