Skip to contentSkip to conversation

btrfs-progs: libbtrfsutil is under LGPL-3.0 and statically liked into btrfs

DISCUSSION Adam Borowski 3 participants 3 messages Mar 17, 2021 Btrfs file system

lore
Share & tools
lore
#0 lore raw

This is https://bugs.debian.org/985400

----- Forwarded message from Claudius Heine <[email protected]> -----

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

#1 lore raw
Quoted 6 lines · Adam Borowski

This is https://bugs.debian.org/985400

----- Forwarded message from Claudius Heine <[email protected]> -----

Dear Maintainer,

Quoted 8 lines

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.

Quoted 3 lines

[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/[email protected]/

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.

#2 lore raw
Quoted 39 lines · David Sterba
Quoted 6 lines · Adam Borowski

This is https://bugs.debian.org/985400

----- Forwarded message from Claudius Heine <[email protected]> -----

Dear Maintainer,

Quoted 8 lines

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.

Quoted 3 lines

[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/[email protected]/

Quoted 8 lines

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.

Relicensing request has been sent to the mailing list:
https://lore.kernel.org/linux-btrfs/[email protected]/T/

Signature · 1 line
真実はいつも一つ!/ Always, there's only one truth!