Hello,

I was not sure which list is appropriate for this question. Because of
that I try it here because I am quit familiar with this community.

To my understanding of the policy the license file of package should be installed into

/usr/share/doc/<package>/LICENSE

How to handle it if a project does have multiple license files?

According to the REUSE standard (itself related to SPDX standard) an
upstream repository should have a folder named LICENSES containing the licenses. See [1] as an example.

Would it be OK, just installing that folder in Debian GNU/Linux the same
way?

/usr/share/doc/<package>/LICENSES/*.txt

Regards,
Christian


[1] -- <https://github.com/bit-team/backintime/tree/dev/LICENSES>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

SGkgYy5idWh0eiAoMjAyNC4xMS4xOF8xMjozMTowMV8rMDAwMCkKPiBJIHdhcyBub3Qgc3VyZSB3 aGljaCBsaXN0IGlzIGFwcHJvcHJpYXRlIGZvciB0aGlzIHF1ZXN0aW9uLiBCZWNhdXNlIG9mIHRo YXQKPiBJIHRyeSBpdCBoZXJlIGJlY2F1c2UgSSBhbSBxdWl0IGZhbWlsaWFyIHdpdGggdGhpcyBj b21tdW5pdHkuCj4gCj4gVG8gbXkgdW5kZXJzdGFuZGluZyBvZiB0aGUgcG9saWN5IHRoZSBsaWNl bnNlIGZpbGUgb2YgcGFja2FnZSBzaG91bGQgYmUKPiBpbnN0YWxsZWQgaW50bwo+IAo+ICAgICAv dXNyL3NoYXJlL2RvYy88cGFja2FnZT4vTElDRU5TRQoKSXQncyBzcGVsbGVkOiAvdXNyL3NoYXJl L2RvYy88cGFja2FnZT4vY29weXJpZ2h0Cgo+IEhvdyB0byBoYW5kbGUgaXQgaWYgYSBwcm9qZWN0 IGRvZXMgaGF2ZSBtdWx0aXBsZSBsaWNlbnNlIGZpbGVzPwoKV2UgY29tYmluZSB0aGVtIGFsbCBp bnRvIGEgc2luZ2xlIGZpbGUuIFNlZToKaHR0cHM6Ly93d3cuZGViaWFuLm9yZy9kb2MvcGFja2Fn aW5nLW1hbnVhbHMvY29weXJpZ2h0LWZvcm1hdC8xLjAvCgo+IEFjY29yZGluZyB0byB0aGUgUkVV U0Ugc3RhbmRhcmQgKGl0c2VsZiByZWxhdGVkIHRvIFNQRFggc3RhbmRhcmQpIGFuCj4gdXBzdHJl YW0gcmVwb3NpdG9yeSBzaG91bGQgaGF2ZSBhIGZvbGRlciBuYW1lZCBMSUNFTlNFUyBjb250YWlu aW5nIHRoZQo+IGxpY2Vuc2VzLiBTZWUgWzFdIGFzIGFuIGV4YW1wbGUuCj4gCj4gV291bGQgaXQg YmUgT0ssIGp1c3QgaW5zdGFsbGluZyB0aGF0IGZvbGRlciBpbiBEZWJpYW4gR05VL0xpbnV4IHRo ZSBzYW1lCj4gd2F5Pwo+IAo+ICAgICAvdXNyL3NoYXJlL2RvYy88cGFja2FnZT4vTElDRU5TRVMv Ki50eHQKCkknbSBhZnJhaWQgbm90LCB0aGF0IHdvdWxkbid0IGNvbXBseSB3aXRoIHBvbGljeSwg wqcxMi41IGlzIGZhaXJseQpzcGVjaWZpYy4KCmh0dHBzOi8vd3d3LmRlYmlhbi5vcmcvZG9jL2Rl Ymlhbi1wb2xpY3kvY2gtZG9jcy5odG1sI3MtY29weXJpZ2h0ZmlsZQpodHRwczovL3d3dy5kZWJp YW4ub3JnL2RvYy9kZWJpYW4tcG9saWN5L2NoLXNvdXJjZS5odG1sI2NvcHlyaWdodC1kZWJpYW4t Y29weXJpZ2h0CgpOb3QgdGhhdCBwb2xpY3kgY2FuJ3QgYmUgY2hhbmdlZCwgYnV0IHRoZXJlJ2Qg bmVlZCB0byBiZSBhIGdvb2QgcmVhc29uLgpUaGlzIHNjaGVtZSBsb29rcyBsZXNzIGV4cHJlc3Np dmUgdGhhbiBEZWJpYW4ncyBtYWNoaW5lLXJlYWRhYmxlIGZvcm1hdC4KClN0ZWZhbm8KCi0tIApT dGVmYW5vIFJpdmVyYQogIGh0dHA6Ly90dW1ibGV3ZWVkLm9yZy56YS8KICArMSA0MTUgNjgzIDMy NzIK

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hello Stefano,

thank you for your reply.

Am 18.11.2024 13:55 schrieb Stefano Rivera:

To my understanding of the policy the license file of package should
be
installed into

/usr/share/doc/<package>/LICENSE

It's spelled: /usr/share/doc/<package>/copyright

To my understand the "copyright" file is something Debian specific.
This does not exist in my upstream project but is "generated" by my
Debian Package Maintainer.
There are several packages (e.g. "backintime-common" and
"backintime-qt") containing LICENSE
file and copyright file in that folder side by side.

Just assume that my DPM does handle the copyright file by himself in an appropriate way.

But what about LICNESE file and a LICENSES folder for multiple licenses
files?

This scheme looks less expressive than Debian's machine-readable
format.

SPDX is designed to be human- and machine readable. There is also a
linter "reuse lint".
I am also aware of Debian internal approaches to generate Debian policy
conform copyright
and license information based on SPDX meta data.

Regards,
Christian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, Nov 18, 2024 at 01:41:34PM +0000, c.buhtz@posteo.jp wrote:

To my understanding of the policy the license file of package should
be
installed into

/usr/share/doc/<package>/LICENSE

It's spelled: /usr/share/doc/<package>/copyright

To my understand the "copyright" file is something Debian specific.
This does not exist in my upstream project but is "generated" by my Debian Package Maintainer.

Correct. Which is what you were asking about.

There are several packages (e.g. "backintime-common" and "backintime-qt") containing LICENSE
file and copyright file in that folder side by side.

And lintian has an extra-license-file tag for such packages.

Just assume that my DPM does handle the copyright file by himself in an appropriate way.

But what about LICNESE file and a LICENSES folder for multiple licenses files?

What about them that wasn't answered in the email you quoted and in the
Policy?

--
WBR, wRAR

-----BEGIN PGP SIGNATURE-----

iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmc7TpwtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh mg8P/iUtAtQu9sgMluLbCv/XK2IhkuRiohSu26eH+dJVyIpzIHph53qShRU1UrCU NRZcep6uJG80aWegPq9mLYbqvGwm0BblIlQ/ifInKnWObNoIdinDO0e5Ei6Gc0dI Fb7M4mBva/caB7iDbtA8Qmut6YFnWK0BAhLwK68rz2fxpf1Pph4fPj/IVVe9KcOP yQPq8FvOnudXPB/q3Agj1dBr2axYtTWaG343cwlKqgfFayAD+Sl6DI1z8/SdGojc GZUAWdKOlfYztkZdJyXOg6OGBC8jLIbRlGGue4mTArTL21r2OOuBCso6ntahojas 17p27o14+rgqFEJuVP3ZZv3G7OK9s0zdd+ZEbW3RwmHgokNvnsId/ijGkfnEB04U goDjwMwGy8757BATC57W0TKu0JbHEsunh1U5bic/ssBMZB3OQzprsg+naCkPBSnQ oK9YguXuqcKNIpXlo0i09P3KyMsyV3GXbONyZX2KPkK8lwflLgUT7ly0l9Dc8xuW oU7gkALnPyG5I55YT2U/QHX4DzmTOMyFxNyWRQvavw6VQsiBwfWSL8XsUEriAnV5 +VyuEVL+u/YbnqItnjO5/n+HpHrQAaytLYIzWDpbf5aAFaKQlBAEVd5BbCQ8bjx3 pZAQDLjlVY9604VodxrF1p4CCEjafRjWGT0xf/2MxmUM63w9
=n8Kh
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hello Andrey,
Thank you for the reply.

Am 18.11.2024 15:26 schrieb Andrey Rakhmatullin:

On Mon, Nov 18, 2024 at 01:41:34PM +0000, c.buhtz@posteo.jp wrote:

To my understand the "copyright" file is something Debian specific.
This does not exist in my upstream project but is "generated" by my
Debian
Package Maintainer.

Correct. Which is what you were asking about.

IMHO not. But that seems to be because of our different perspectives.

And lintian has an extra-license-file tag for such packages.

https://udd.debian.org/lintian-tag/extra-license-file

Ah... Now, we come closer.

But what about LICNESE file and a LICENSES folder for multiple
licenses
files?

What about them that wasn't answered in the email you quoted and in the Policy?

To my understand that wasn't answered.

Regarding the lintian tag am I assuming correct that Debian GNU/Linux
does not care about a LICENSE file or LICENSES folder?
So there is no real problem to have a LICENSES folder?
The "copyright" file will exist (downstream) no matter if there is a
LICENSE file, a LICENSES folder or any of this.

Correct?

Regards,
Christian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Monday, November 18, 2024 8:57:49 AM MST c.buhtz@posteo.jp wrote:

Regarding the lintian tag am I assuming correct that Debian GNU/Linux
does not care about a LICENSE file or LICENSES folder?
So there is no real problem to have a LICENSES folder?
The "copyright" file will exist (downstream) no matter if there is a
LICENSE file, a LICENSES folder or any of this.

The debian/copyright file must contain all the copyright information AND all the license information. All the licenses from all the LICENSES files must be copied into debian/copyright (the full text of common licenses can be referenced against usr/share/common-licenses). Upstream LICENSES files should not be shipped in Debian.

--
Soren Stoutner
soren@debian.org
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmc7aUYACgkQwufLJ66w tgM9Ag/6AumBbG5NzaQIoItsiI7aLWME7SaCyTZ4F1xQ/s9KlLqe+N+MR8MkDqaM 3q5MTrikJg97zSuGvIdcKaXF20YAD2lkTIud3Hr6x+2fV7d3aSIDwCSe2r4u+bPz WoT/bvQTonGHhY6jVIUTZeagqUXg9Bhea28Hz33WSaILIfkYDHHPaITwMHCpv64E 24aPAkBKJJMmugjwsjevqUCdYcBc3w2MdxR3zwJYijEbkYODR+2LEwOxG6001WYf oFP6wtjaEZQIljC0mpea/iJbYuKC9abq8OXUEgx701/66dsBETxQOPMQwE4w2tzw 5MLyLUivNQQ5KsNwFkNFfnNBarymmc6U6KfcQxO9qSSgjO4QXaJBxVcuQyVmc8w2 IsfgqFyxqTgXtV4qUkiqxn35zSbh2CL7iIwKREVoee1qBzQDYEHB6Hz8kHVOPb1G F7GTxjwGRCjyIwzJ/97bIVMeGf7Cl+Ggw2Xu/zwJPBQvx4plwcY+W4JNuK8T87ou P7JSSw3j+sDwUgbC27G2Elmku6OOX0HcU+yFbRb3JWmloafG84MV48aq2ycCppZL BGRU7iAbjAldZsL4cS9c1j+KirwtP0Pc9dYueI/DjB+peUu4VrTYt+Dkx59LuICG odhPF3lzAI8XRfbF3wsFiRQxeZ0Nz1t5SxKC3YB8P5xbKfG0/qI=
=VjlT
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Monday, 18 November 2024 16:57:49 CET c.buhtz@posteo.jp wrote:

To my understand that wasn't answered.

Yes, the collection of licences is something distinct from the copyright information. In REUSE, the copyright information is maintained in a manifest that should be compatible with the DEP-5 format.

Regarding the lintian tag am I assuming correct that Debian GNU/Linux
does not care about a LICENSE file or LICENSES folder?
So there is no real problem to have a LICENSES folder?

I imagine that there will be a desire to prevent duplicate files being installed, since there is /usr/share/common-licenses which is meant to hold standard licence texts. Of course, custom licences would not feature among the common-licenses and this is where REUSE's own licences collection for each package could be useful, but some custom licences might preclude software from being available in Debian in the first place.

The "copyright" file will exist (downstream) no matter if there is a
LICENSE file, a LICENSES folder or any of this.

Indeed.

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, Nov 18, 2024 at 03:57:49PM +0000, c.buhtz@posteo.jp wrote:

To my understand the "copyright" file is something Debian specific.
This does not exist in my upstream project but is "generated" by my Debian
Package Maintainer.

Correct. Which is what you were asking about.

IMHO not. But that seems to be because of our different perspectives.

If you weren't actually asking about the requirements of the Policy then
you shouldn't have mentioned it...

And lintian has an extra-license-file tag for such packages.

https://udd.debian.org/lintian-tag/extra-license-file

Ah... Now, we come closer.

But what about LICNESE file and a LICENSES folder for multiple
licenses
files?

What about them that wasn't answered in the email you quoted and in the Policy?

To my understand that wasn't answered.

I asked what exactly wasn't answered...

Regarding the lintian tag am I assuming correct that Debian GNU/Linux does not care about a LICENSE file or LICENSES folder?

"Debian GNU/Linux" doesn't care if those files exist in the package.

So there is no real problem to have a LICENSES folder?

Yes, there is no real problem to ship the licenses twice. It's just not helpful.

The "copyright" file will exist (downstream) no matter if there is a LICENSE file, a LICENSES folder or any of this.

Of course, that's what the Policy mandates.

--
WBR, wRAR

-----BEGIN PGP SIGNATURE-----

iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmc7bkQtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh a80QAINtTho0H2BPNHg5Zpipuv7unvuP15PgHlhSdSBAJmiFvuEBdYHYFF7Eov1M Xm5MXUqfsRi3lW3oVzuLrHi6MG9i4Hg5LFm6YbDUBIiBiUHE0SC70wxB57yNJ2zj HPHvKXEywUKgOWovua+LRn1YefJgemsPoXxqNGjjZ4nJ0HOB88m7gPK24U1UrPPD 2PBKEJuRjRg7C7PuG/cCnZUksFSF3icoO9ul7G4svlE/BsAvOtra8xykWDv6tbIt WmRcnuYCfk5ydVDgxlROX9cLmW9Ao2yd8v0nNvO0tVamG9IYrbspV5aKSPoCrwGh L9tIhjZ+vOk14eS9mUyIRYU7YVn4aqdz3N5Bx98AgkXxCz7SiabCACbFhpzBBk6U 7QUf4TNrXd/+Hrm817HtUEJy8YSrlj5i+y1NdlsECYUBYe7AKTK3hBvgO8wW754/ eVOgFDlglHLnxqlHrOwEm7QzpZbw2Zsths1mM90TTyIHYpTPLNLdbj7FKuMzVVVG KbuQXwiA/vYWJMLIutsxXJsaIwIiQE2ktXfxzGXIjTXn1IQykjugBW/kvXTRBwmI NCnuQ+l2WY8li+8ozo0bPciqsvd5TL5Dvo6/xj4yp+G9yLPRePXvh3gWTQC7gf36 a+wqErCrQJRst3McawLT1lE5iObIg/4kpcrpOG1PgDEHctEc
=nNlK
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)