-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2011-01-07 04:38, Russ Allbery wrote:
Niels Thykier ni...@thykier.net writes:
[...]
My current effort in the infra-513663 branch has been to encapsulate
packages inside the lab and reduce the complexity of the PACKAGE: foreach.
I intend to
On Mon, January 10, 2011 09:51, Niels Thykier wrote:
Alright, I need a second pair of eyes here. In frontend/lintian there
is a piece of code[1]. This is about line 880ish in the infra-513663
branch.
I am almost certain there is something fishy going on within the if
body. With a bit of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2011-01-10 11:54, Adam D. Barratt wrote:
On Mon, January 10, 2011 09:51, Niels Thykier wrote:
Alright, I need a second pair of eyes here. In frontend/lintian there
is a piece of code[1]. This is about line 880ish in the infra-513663
branch.
Niels Thykier ni...@thykier.net writes:
Really? Judging from Lintian::Schedule I would say it is partly
enforcing this regardless of the output order of dpkg-genchanges
# for each package (the sort is to make sure that source packages are
# before the corresponding binary packages--this has
Niels Thykier wrote:
Speaking of unpacking; as I understand it we once had an unpack-level
2 which has now been removed in favour of collection. I am considering
to remove the unpack-level 1 as well and move everything to collection
as a part of this.
The frontend needs a couple of tweaks
Niels Thykier ni...@thykier.net writes:
Speaking of unpacking; as I understand it we once had an unpack-level
2 which has now been removed in favour of collection. I am considering
to remove the unpack-level 1 as well and move everything to collection
as a part of this.
I feel the unpack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2011-01-06 20:18, Russ Allbery wrote:
Niels Thykier ni...@thykier.net writes:
Speaking of unpacking; as I understand it we once had an unpack-level
2 which has now been removed in favour of collection. I am considering
to remove the
Niels Thykier ni...@thykier.net writes:
On 2011-01-06 20:18, Russ Allbery wrote:
As long as we have some way of marking some collections as transient
and some collections to be retained, and then provide some way of
overriding that, that sounds fine. I much prefer talking about
everything
Niels Thykier ni...@thykier.net writes:
I have had a look at this nearly 2 year old bug and I think it would be
great if we could find a solution for cross-package checks. To make it
even better I am interested in working on this. That being said I have
not work on Lintian for very long so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey
I have had a look at this nearly 2 year old bug and I think it would be
great if we could find a solution for cross-package checks. To make it
even better I am interested in working on this. That being said I have
not work on Lintian for very
Package: lintian
Version: 2.2.0
Severity: wishlist
Lintian currently checks source packages and binary packages in isolation,
except for a few fragile hacks. However, overwhelmingly Lintian is run in
one of two ways: on a *.changes file, from which the source package and all
binary packages
11 matches
Mail list logo
