From: Vagrant Cascadian <vagrant@debian.org>
To: u-boot@lists.denx.de
Subject: Licensing discrepancies or ambiguities
Date: Tue, 21 Nov 2023 11:10:57 -0800 [thread overview]
Message-ID: <8734wyudku.fsf@contorta> (raw)
[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]
I've been reviewing the copyright and license information for Das U-Boot
in preparation for uploading to Debian, and found a few surprises.
tools/libfdt/fdt_rw.c: /* SPDX-License-Identifier: GPL-2.0+ BSD-2-Clause */
I *think* according to the SPDX spec this needs an OR or an AND. I also
see no copyright declaration, although maybe there is a standard
interpretation for this.
Similar issue with (though thankfully they include copyright
declarations):
include/bloblist.h:/* SPDX-License-Identifier: GPL-2.0+ BSD-3-Clause */
common/bloblist.c:// SPDX-License-Identifier: GPL-2.0+ BSD-3-Clause
doc/README.ubispl:# SPDX-License-Identifier: GPL 2.0+ BSD-3-Clause
This one has a non-existent license:
test/lib/strlcat.c: // SPDX-License-Identifier: GPL-2.1+
No such license exists, though thankfully it references the exact file
in the original glibc sources it came from, which is listed as
LGPL-2.1+.
There are certainly more ambiguous issues, but figured I would start
with those!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2023-11-21 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 19:10 Vagrant Cascadian [this message]
2023-11-21 19:37 ` Licensing discrepancies or ambiguities Tom Rini
2023-11-25 22:39 ` Vagrant Cascadian
2023-11-27 14:27 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8734wyudku.fsf@contorta \
--to=vagrant@debian.org \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox