Bug#681616: lintian: False positive: unused-license-paragraph.. when two licenses are given and described in different places

2013-09-08 Thread Niels Thykier
Hi Martin, It seems I forgot to CC you on this. In short, I believe this is not a bug in Lintian, but rather a bug in the DEP-5 copyright file in question. See below for the rationale (or the bug log for #681616). ~Niels On 2013-09-05 13:39, Niels Thykier wrote: On 2013-09-05 12:24, Dominik

Bug#681616: lintian: False positive: unused-license-paragraph.. when two licenses are given and described in different places

2013-09-08 Thread Martin Erik Werner
On Sun, Sep 08, 2013 at 01:29:19PM +0200, Niels Thykier wrote: Hi Martin, It seems I forgot to CC you on this. In short, I believe this is not a bug in Lintian, but rather a bug in the DEP-5 copyright file in question. See below for the rationale (or the bug log for #681616). ~Niels

Bug#681616: lintian: False positive: unused-license-paragraph.. when two licenses are given and described in different places

2013-09-05 Thread Dominik George
Hi, It is my understanding that: Files: A Copyright: ... License: X or Y License: X $LICENSE_TEXT_FOR_X License: Y $LICENSE_TEXT_FOR_Y Works as intended. actually, it doesn't. I am not aware of a package in the distribution, but mirabilos (Cc) and I stumbled upon this

Bug#681616: lintian: False positive: unused-license-paragraph.. when two licenses are given and described in different places

2013-09-05 Thread Niels Thykier
On 2013-09-05 12:24, Dominik George wrote: Hi, It is my understanding that: Files: A Copyright: ... License: X or Y License: X $LICENSE_TEXT_FOR_X License: Y $LICENSE_TEXT_FOR_Y Works as intended. actually, it doesn't. Your sample copyright file does not follow the above

Bug#681616: lintian: False positive: unused-license-paragraph.. when two licenses are given and described in different places

2013-09-05 Thread Thorsten Glaser
Niels Thykier dixit: If there are no remaining lines, [...]. Otherwise, this field should either include the full text of the license(s) or include a pointer to the license file under /usr/share/common-licenses. [...] Ah so this is an either-or. license in /usr/share/common-licenses). The

Bug#681616: lintian: False positive: unused-license-paragraph.. when two licenses are given and described in different places

2013-09-04 Thread Niels Thykier
On 2013-08-30 00:18, Dominik George wrote: Package: lintian Version: 2.5.17 Followup-For: Bug #681616 The bug also exists for the construct License: Foo or Bar with two License paragraphs Foo and Bar. It appears that intian completely ignores the alternative names syntax described in

Bug#681616: lintian: False positive: unused-license-paragraph.. when two licenses are given and described in different places

2013-08-29 Thread Dominik George
Package: lintian Version: 2.5.17 Followup-For: Bug #681616 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The bug also exists for the construct License: Foo or Bar with two License paragraphs Foo and Bar. It appears that intian completely ignores the alternative names syntax described in DEP5.

Bug#681616: lintian: False positive: unused-license-paragraph.. when two licenses are given and described in different places

2012-07-14 Thread Martin Erik Werner
Package: lintian Version: 2.5.8 Severity: minor Dear Maintainer, A copyright file with this snippet: ### Files: * Copyright: Lor Em License: custom and Foo This is some custom license terms. . Mentions that Foo license also applies. License: Foo This is the standard Foo license. ###