[1] https://github.com/glaubitz/fs-uae-arcade-debian
[2] https://github.com/glaubitz/fs-uae-launcher-debian
[3] https://salsa.debian.org/fonts-team/fonts-roboto/-/blob/master/debian/copyright
(Please CC me, I'm not subscribed to debian-devel)
Hi!
I'm currently updating the debian/copyright of my two packages
fs-uae-arcade [1] and fs-uae-launcher [2] as both packages got
rejected by the FTP team due to an incomplete debian/copyright.
Since the packages contain a lot of different licenses, the
debian/copyright would be very long when copying the different license
texts verbatim.
However, I stumbled over the fonts-roboto package which resolves this
issue by using just references to the full license texts which are
present on any Debian system anyway [3].
I have updated debian/copyright of both fs-uae-* packages to use the "License-Reference" keyword, however lintian now complains about the
missing license texts so I'm wondering whether this approach - which I
like - is actually compliant with the Debian Policy?
Quoting John Paul Adrian Glaubitz (2022-01-16 19:38:25)[...]
I have updated debian/copyright of both fs-uae-* packages to use the "License-Reference" keyword, however lintian now complains about the missing license texts so I'm wondering whether this approach - which
I like - is actually compliant with the Debian Policy?
I firmly believe that it is Policy-compliant to reference files
included with package base-files and installed below /usr/share/common-licenses. All other license texts must be included verbatim in the debian/copyright file
Quoting Jonas Smedegaard (2022-01-16 19:53:48)
Quoting John Paul Adrian Glaubitz (2022-01-16 19:38:25)[...]
I have updated debian/copyright of both fs-uae-* packages to use the
"License-Reference" keyword, however lintian now complains about the
missing license texts so I'm wondering whether this approach - which
I like - is actually compliant with the Debian Policy?
I firmly believe that it is Policy-compliant to reference files
included with package base-files and installed below
/usr/share/common-licenses. All other license texts must be included
verbatim in the debian/copyright file
Maybe more interesting than what I personally believe might be, that I
use that writing style generally for the about 600 packages that I am involved in maintaining, and evidently ftpmasters agree with me.
For anyone considering to adopt this pattern, it is quite some time ago
that I helped Vasudev package Roboto fonts, and I have simplified and extended my writing style to use the shorter field "Reference" and also
use it to reference sources of copyright holders and license grants when
not contained in licensed file itself (with a little special twist of self-referencing canonical statements in debian/copyright).
I use the package ghostscript as my sort-of reference package. Look at
that for my newest inventions on copyright file writing and checking.
See also https://wiki.debian.org/CopyrightReviewTools
On 1/16/22 20:06, Jonas Smedegaard wrote:
For anyone considering to adopt this pattern, it is quite some time
ago that I helped Vasudev package Roboto fonts, and I have
simplified and extended my writing style to use the shorter field "Reference" and also use it to reference sources of copyright
holders and license grants when not contained in licensed file
itself (with a little special twist of self-referencing canonical statements in debian/copyright).
I agree it's a great idea as it saves a lot of time. Writing an
acceptable debian/copyright file can be quite frustrating so this is a
very welcome improvement.
I use the package ghostscript as my sort-of reference package. Look
at that for my newest inventions on copyright file writing and
checking.
See also https://wiki.debian.org/CopyrightReviewTools
Thanks, I'll have a look!
Thanks a lot for the quick and detailed response!
"Jonas" == Jonas Smedegaard <jonas@jones.dk> writes:
"Jonas" == Jonas Smedegaard <jonas@jones.dk> writes:
Jonas> Please note, however, that license _grants_ (i.e. the various
Jonas> ways a copyright holder can state that they grant some
Jonas> _referenced-by-them_ license) need not be included verbatim.
I suspect we're in agreement. But for completeness. If a copyright
grant simply grants the terms of a referenced license, I don't think
we need to include it verbatim. However, if the grant includes
licensing itself--for example additional permissions or even more interestingly restrictions), it's easy for the grant to become more of
a license and to be a license that needs to binclude in its own right.
(I'm aware that many circumstances where a license grant includes a restriction would be problematic especially say when combined with the GPL-3. I can think of licenses/situations when such a result would
still be DFSG free though, and in such situations it seems like it
would be important to clearly document in debian/copyright).
I don't think anything I write above is a disagreement with the common
case you're covering. I suspect you already would be, but my advice
to others is to be careful of license grants that include unsual text
and to err on the side of including them in debian/copyright.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 58:15:43 |
Calls: | 6,652 |
Calls today: | 4 |
Files: | 12,200 |
Messages: | 5,331,136 |