On Sat, Jun 04, 2011 at 10:57:20PM +0200, Niels Thykier wrote:
> Personally I feel that running setup.py code inside the package is a
> "no-go" for Lintian; perhaps there is another way we can "trivially"
> extract it from setup.py?
Not running code is a very good point. Unfortunately, there is n
Package: lintian
Severity: wishlist
Some of us are not so good at remembering to set the upload target
(unstable/experimental/stable/whatever) correctly. It would be handy if
lintian could warn about this. For example (names changed):
liw: we have bar 3.0.x series in unstable and 3.2.x in
experi
la, 2008-05-31 kello 11:08 -0700, Russ Allbery kirjoitti:
> You'd need some way to request only that specific check, I think, since
> even people who normally want lintian to be as verbose as possible aren't
> going to want that.
Yeah, thus the debian/lintian-me-harder suggestion: only do the chec
la, 2008-05-31 kello 16:47 -0500, Raphael Geissert kirjoitti:
> Wouldn't this be more suitable in dput/dupload?
> Those already have similar options, some of which are disabled by default,
> but available anyway.
It seems to me that it's the kind of static checking that belongs to
lintian, so I'd
Package: lintian
Severity: wishlist
Policy 9.3.3.2 (Running initscripts) says that packages are strongly
recommended to use invoke-rc.d instead of calling the init.d script
directly. This will in the future become mandatory (or so the footnote
says and I fervently hope).
It would be nice if linti
> It would be nice if lintian would warn if maintainer scripts use the
> init.d script directly and not via invoke-rc.d. Checking that the string
> "/etc/init.d/" exists but "invoke-rc.d" does not might be a good enough
> approximation to catch most such problems.
I did a quick check using the at
Are the scripts that operate http://lintian.debian.org/ (run lintian,
build web pages) available?
I'm going to look at doing the same for Ubuntu packages, and would be
glad to share scripts (and co-operate in maintaining them, if
necessary).
--
That which does not kill us makes us stranger
--
to, 2007-10-04 kello 16:09 -0700, Russ Allbery kirjoitti:
> Lars Wirzenius <[EMAIL PROTECTED]> writes:
>
> > Are the scripts that operate http://lintian.debian.org/ (run lintian,
> > build web pages) available?
>
> Yes, they're part of the lintian
pe, 2007-10-05 kello 11:12 -0700, Russ Allbery kirjoitti:
> I don't know what the other lintian maintainers feel about this, but I
> personally am comfortable enough with Python that I would have no
> objections if you'd like to rewrite the reporting harness and HTML
> generation in Python instead
Package: lintian
http://lintian.debian.org/reports/Tdeb-data-member-wrongly-compressed.html
deb-data-member-wrongly-compressed
The binary package contains a data member not compressed with
gzip. From dpkg-dev 1.11 on, you can configure the way the data
tarball is compresse
Am I crazy or is the reporting/config file in the lintian source tree
using an entirely wrong syntax? I have not yet had time to learn Perl,
but it seems to me that the code in frontend/lintian that reads the
configuration file (starting around line 350) does not want the Perl
syntax in the example
On ma, 2007-11-19 at 12:18 -0800, Russ Allbery wrote:
> Lars Wirzenius <[EMAIL PROTECTED]> writes:
>
> > Am I crazy or is the reporting/config file in the lintian source tree
> > using an entirely wrong syntax? I have not yet had time to learn Perl,
> > but i
I have now successfully used the harness to run lintian on a subset of
Ubuntu (specifically the "restricted" section), and would like to expand
to include "main", but it does not seem to be possible to run lintian
automatically against all sections on a mirror. Is that correct, or am I
being dense
On ma, 2007-11-19 at 13:07 -0800, Russ Allbery wrote:
> Lars Wirzenius <[EMAIL PROTECTED]> writes:
>
> > I knew about harness. I used (or tried to) use harness earlier, even,
> > but now I completely forgot about it, and started re-writing one from
> > scratch. No
On ma, 2007-11-19 at 13:22 -0800, Russ Allbery wrote:
> Lars Wirzenius <[EMAIL PROTECTED]> writes:
>
> > I have now successfully used the harness to run lintian on a subset of
> > Ubuntu (specifically the "restricted" section), and would like to expand
> >
On to, 2008-01-03 at 08:48 +0100, Thijs Kinkhorst wrote:
> I was thinking that this could be better implemented by generating one page
> per maintainer with all tags, and that I and O are hidden elements by
> default. A link on the page would then just toggle the visibility of that CSS
> class (
On su, 2008-03-02 at 19:33 +0100, Amaya wrote:
> Hey There,
>
> As an effort to try to finish the invoke-rc.d transition for lenny, I
> feel I must prod you guys here. Any improvements so far?
> Lars, could you maybe look into providing a patch?
Unfortunately, I'm able to provide patch perl code
On su, 2008-03-02 at 19:59 +0100, Amaya wrote:
> > Unfortunately, I'm able to provide patch perl code at the time being.
>
> This does not parse. If you are unable to provide a patch atm, is it
> because of perl?
I don't know Perl and so I'm unable to write a patch that will add a
lintian warning
18 matches
Mail list logo
