From: David Sterba <dsterba@suse.cz>
To: Adam Borowski <kilobyte@angband.pl>
Cc: linux-btrfs@vger.kernel.org, sbabic@denx.de, ngompa13@gmail.com,
Claudius Heine <ch@denx.de>,
osandov@osandov.com
Subject: Re: Fwd: btrfs-progs: libbtrfsutil is under LGPL-3.0 and statically liked into btrfs
Date: Wed, 17 Mar 2021 15:17:33 +0100 [thread overview]
Message-ID: <20210317141733.GR7604@twin.jikos.cz> (raw)
In-Reply-To: <YFHtnGvRH+QlwRN6@angband.pl>
On Wed, Mar 17, 2021 at 12:53:00PM +0100, Adam Borowski wrote:
> 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.
Thanks for bringing it up.
> [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
As explained in that link
"Use a library" means that you're not copying any source directly, but
instead interacting with it through linking, importing, or other
typical mechanisms that bind the sources together when you compile or
run the code.
the static link applies and the licenses do not allow that. So what are
the options:
- relicense libbtrfsutil to LGPL v2.1 or later
- relicense libbtrfsutil to LGPL v2.1 only
There was another request to relicense it
https://lore.kernel.org/linux-btrfs/b927ca28-e280-4d79-184f-b72867dbdaa8@denx.de/
I'm not aware of any objections to relicensing, it hasn't happend in
5.11 due to time reasons but I think 5.12 is feasible.
If there's anybody willing to drive the process please let me know. The
mpv project did relicensing as well and we can draw some inspiration
from there https://github.com/mpv-player/mpv/issues/2033 . It took them
like 5 years but the number of contributors we'd need to ask is small and
most of them are known so it should not take more than a month.
next prev parent reply other threads:[~2021-03-17 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 11:53 Fwd: btrfs-progs: libbtrfsutil is under LGPL-3.0 and statically liked into btrfs Adam Borowski
2021-03-17 14:17 ` David Sterba [this message]
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=20210317141733.GR7604@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=ch@denx.de \
--cc=kilobyte@angband.pl \
--cc=linux-btrfs@vger.kernel.org \
--cc=ngompa13@gmail.com \
--cc=osandov@osandov.com \
--cc=sbabic@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