I'm trying to get ramped back up with how Lintian works these days, at
least enough to be able to review and approve merge requests. When
looking at:
https://salsa.debian.org/lintian/lintian/-/merge_requests/400
I was a bit confused by the added tests, specifically that the valid
package seems
Hi,
The source format 3.0 is now the default in the Lintian test suite.
Most tests use a native format. That is not representative of the
archive, but it can be changed easily. Many tests will work with the
non-native format, but they haven't been converted for lack of need.
The native format may
Hi Chris,
I did not see this bug until now. Have you seen the error message since then?
Otherwise, I am inclined to close the bug. I have not had problems
with that part of the test suite in a while. It has been under rapid
development.
Kind regards
Felix Lechner
Chris Lamb pushed to branch master at lintian / lintian
Commits:
09965279 by Felix Lechner at 2019-01-25T08:20:21Z
Declare new lintian test suite tags; undefine all others.
In the future, all tests checking Lintians tag functionality belong to
suite
tags. Undefine the other suites for tests
Hi Niels,
Thank you for your thoughtful comments. Your input weighs heavily in
Debian QA. I will address your points one by one, but will mostly
disregard your comments regarding style. Some of it may be my lack of
experience. Perhaps it is my walk of life. I probably dislike the
passive language
Hi Felix,
Context for lint-maint: Felix Lechner sent me a proposed change for the
test suite and asked me for write an email with the feedback. I thought
it was useful to include lint-maint because it affects all contributors
of lintian (if implemented). The proposal is quoted below interleaved
Your message dated Wed, 23 Feb 2011 05:17:11 +
with message-id e1ps767-0005my...@franck.debian.org
and subject line Bug#593832: fixed in lintian 2.5.0~rc1
has caused the Debian Bug report #593832,
regarding lintian: Build-Depends for the lintian test suite
to be marked as done.
This means
On Wed, 2010-12-22 at 12:01 +0100, Niels Thykier wrote:
I had a look at the test suite and it is only a few hick-ups short of
being issue free (at least on a x86). I have attached the failures I saw.
This one:
-E: package-version-0 source: upstream-version-not-numeric unknown
was a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2010-12-24 14:22, Adam D. Barratt wrote:
On Wed, 2010-12-22 at 12:01 +0100, Niels Thykier wrote:
I had a look at the test suite and it is only a few hick-ups short of
being issue free (at least on a x86). I have attached the failures I saw.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi
I had a look at the test suite and it is only a few hick-ups short of
being issue free (at least on a x86). I have attached the failures I saw.
I heard that some of the legacy tests are known to fail on non-x86
architectures; but I do not have
On Wed, December 22, 2010 11:01, Niels Thykier wrote:
I had a look at the test suite and it is only a few hick-ups short of
being issue free (at least on a x86). I have attached the failures I saw.
Thanks for that.
This:
t/scripts/minimum-version.t ... 51/100
#
Adam D. Barratt wrote:
I heard that some of the legacy tests are known to fail on non-x86
architectures; but I do not have a non-x86 system, so I could not verify
this.
That would be libbaz (which I keep confusing with foo++ and referring to
as libfoo) which is the only test case we have
Niels Thykier ni...@thykier.net writes:
I have tried to figure out the test suite dependencies; Beyond lintian's
Build-Depends{,-Indep} I also installed lintian's dependencies and the
following packages.
libtext-template-perl
rsync
fakeroot
quilt (fields-quilt-debhelper)
python [1]
Package: lintian
Version: 2.4.3
Severity: wishlist
Hi
I have tried to figure out the test suite dependencies; Beyond lintian's
Build-Depends{,-Indep} I also installed lintian's dependencies and the
following packages.
libtext-template-perl
rsync
fakeroot
quilt (fields-quilt-debhelper)
python
Hi,
Russ Allbery wrote:
* The t/tests directory is getting quite large. One easy thing we could
do that would help this, and which I think would also make sense given
the rest of the layout, is to move the *.desc file for a test from
t/tests into the test directory (calling it desc
Raphael Geissert atomo64+deb...@gmail.com writes:
Russ Allbery wrote:
* The t/tests directory is getting quite large. One easy thing we could
do that would help this, and which I think would also make sense given
the rest of the layout, is to move the *.desc file for a test from
Russ Allbery wrote:
Raphael Geissert writes:
Russ Allbery wrote:
What about grouping together tests belonging to the same check?
E.g. move all the cruft tests to t/tests/cruft/
We could do that -- it trades off directory size with more nesting. I
guess I don't have a strong opinion,
I love the new test suite, and as you can probably see from the commit
notifications, I've been trying it out and adding a bunch of additional
test cases. After working with it for a while, I've developed a bit of a
wishlist. Here are my ideas; please send any comments (particularly
Frank, since
Your message dated Wed, 12 Mar 2008 00:57:19 -0700
with message-id [EMAIL PROTECTED]
and subject line Re: Bug#469926: lintian: test suite fails when invoked with
umask != 0022
has caused the Debian Bug report #469926,
regarding lintian: test suite fails when invoked with umask != 0022
Package: lintian
Version: 1.23.46
Severity: minor
Tags: patch
It seems that in many of the test packages in the test suite the
debian/rules script creates files without specifying the permissions
explicitly. If the test suite is run with a non-standard umask, this
causes Lintian to produce a lot
20 matches
Mail list logo
