From: Adam Borowski <kilobyte@angband.pl>
To: linux-btrfs@vger.kernel.org
Subject: Fwd: btrfs-progs: libbtrfsutil is under LGPL-3.0 and statically liked into btrfs
Date: Wed, 17 Mar 2021 12:53:00 +0100 [thread overview]
Message-ID: <YFHtnGvRH+QlwRN6@angband.pl> (raw)
This is https://bugs.debian.org/985400
----- Forwarded message from Claudius Heine <ch@denx.de> -----
Dear Maintainer,
I looked into the licenses of the btrfs-progs project and found that the
libbtrfsutils library is licensed under LGPL-3.0-or-later [1]
The `copyright` file does not show this this.
IANAL, but I think since `btrfs` (under GPL-2.0-only [2]) links to `libbtrfsutil`
statically this might cause a license conflict. See [3]. This would be the part
that might require upstream fixing.
regards,
Claudius
[1] https://github.com/kdave/btrfs-progs/blob/master/libbtrfsutil/btrfsutil.h
[2] https://github.com/kdave/btrfs-progs/blob/master/btrfs.c
[3] http://gplv3.fsf.org/dd3-faq#gpl-compat-matrix
next reply other threads:[~2021-03-17 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 11:53 Adam Borowski [this message]
2021-03-17 14:17 ` Fwd: btrfs-progs: libbtrfsutil is under LGPL-3.0 and statically liked into btrfs David Sterba
2021-03-17 20:06 ` Neal Gompa
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=YFHtnGvRH+QlwRN6@angband.pl \
--to=kilobyte@angband.pl \
--cc=linux-btrfs@vger.kernel.org \
/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