Hi,
Quoting Niels Thykier (2014-03-04 22:51:12)
Thanks for confirming my assertion. Sadly, I see I phrased myself poorly.
You implemented what I said, but not what I wanted. What I meant was to
remove the assignment to $d_restr completely. I.e.
my ($d_pkg, $d_march, $d_version,
* Johannes Schauer j.scha...@email.de, 2014-03-19, 11:43:
Before you apply the attached patch I have another question. Can
lintian also check debian/control in addition to DEBIAN/control?
Yes, it can. :)
In that case, can you give me an example of a tag that checks
debian/control?
Hi,
Quoting Jakub Wilk (2014-03-19 12:01:56)
In that case, can you give me an example of a tag that checks
debian/control?
binary-control-field-duplicates-source
thanks! That was very helpful :)
please find attached a new patch with one more added tag.
All three students forgot to add
Hi,
Quoting Niels Thykier (2014-03-03 22:05:31)
Thanks for looking into this.
and thanks for responding so quickly :)
+Tag: invalid-restriction-label-in-source-relation
+Severity: important
+Certainty: possible
+Info: The restriction list in the source relation includes a term with
+
On 2014-03-04 10:34, Johannes Schauer wrote:
Hi,
Quoting Niels Thykier (2014-03-03 22:05:31)
Thanks for looking into this.
and thanks for responding so quickly :)
If only I could keep it up :)
[...]
Usually, we don't bother doing conflict testing. At least, we skip it
for regular
Package: lintian
Version: 2.5.22
Severity: wishlist
Tags: patch
Hi,
I implemented a preliminary patch for lintian to understand and check
the restriction syntax described in this document:
https://wiki.debian.org/BuildProfileSpec
Please tell me what needs to be changed so that I can get this
On 2014-03-03 16:09, Johannes Schauer wrote:
Package: lintian
Version: 2.5.22
Severity: wishlist
Tags: patch
Hi,
I implemented a preliminary patch for lintian to understand and check
the restriction syntax described in this document:
https://wiki.debian.org/BuildProfileSpec
Hi,
7 matches
Mail list logo