unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 55083@debbugs.gnu.org, Maxime Devos <maximedevos@telenet.be>
Subject: [bug#55083] [PATCH 1/2] gnu: add python-librouteros
Date: Mon, 23 May 2022 18:08:49 +0200	[thread overview]
Message-ID: <20220523180849.02eda788@primarylaptop.localdomain> (raw)
In-Reply-To: <87pmk475ez.fsf_-_@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1957 bytes --]

On Mon, 23 May 2022 15:19:16 +0200
Ludovic Courtès <ludo@gnu.org> wrote:

> Hi Denis,
Hi,

> Did you have a chance to address Maxime’s comments?
> 
> Seems like little is missing to get those patches applied.
I could do that but we can only merge python-librouteros.

python-librouteros doesn't want to change license so only bundlewrap
can fix that licensing issue.

I've reported the bug upstream[1], and as there is a CLA, a single
entity (here a company) owns all the copyright, and they don't want to
re-license as GPLv2 or GPLv2-or-later, so as I understand the only
options left are:
- to somehow remove the python-librouteros dependency completely
- to add an exception to link it to GPLv2 code

As for the later the project expressed some doubts on if it's really
possible or not:
> Hm. Are you sure it's possible for me to "allow" BundleWrap to be
> linked against GPLv2 libs? Wouldn't that require the permission of
> the lib, rather than BundleWrap?

And so far I found the following information on the topic but nothing
really conclusive yet:
- https://www.gnu.org/licenses/gpl-faq.html#v2v3Compatibility
- https://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs

And here the issue mentioned in the first link is the GPLv2 section 6
which has:
> [...]
> You may not impose any further restrictions on the recipients'
> exercise of the rights granted herein.
> [...]

So here I'm not sure anymore if there is a way to somehow satisfy
the GPLv2 of the library just with an exception in bundlewrap.

I'm also very interested in understanding that issue better as I've
written software (were I still own all the copyright) that has somewhat
similar requirements (I want to release it under GPLv2 or later (to
be able to be merged upstream) with an exception for linking against
Apache libraries).

References:
-----------
[1]https://github.com/bundlewrap/bundlewrap/issues/709

Denis.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-05-23 16:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-23 16:44 [bug#55083] [PATCH 1/2] gnu: add python-librouteros Denis 'GNUtoo' Carikli
2022-04-23 16:54 ` [bug#55083] [PATCH 2/2] gnu: Add bundlewrap Denis 'GNUtoo' Carikli
2022-04-23 18:49   ` Maxime Devos
2022-04-26 15:32     ` Denis 'GNUtoo' Carikli
2022-05-23 13:19       ` [bug#55083] [PATCH 1/2] gnu: add python-librouteros Ludovic Courtès
2022-05-23 16:08         ` Denis 'GNUtoo' Carikli [this message]
2022-05-23 16:37           ` Maxime Devos
2022-04-23 18:52   ` [bug#55083] [PATCH 2/2] gnu: Add bundlewrap Maxime Devos
2022-04-23 18:55   ` Maxime Devos
2022-04-23 19:00   ` Maxime Devos
2022-04-23 19:03   ` Maxime Devos
2022-04-23 18:45 ` [bug#55083] [PATCH 1/2] gnu: add python-librouteros Maxime Devos
2022-04-23 18:45 ` Maxime Devos
2022-04-23 18:48 ` Maxime Devos
2022-10-29 11:30 ` [bug#55083] " Denis 'GNUtoo' Carikli

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220523180849.02eda788@primarylaptop.localdomain \
    --to=gnutoo@cyberdimension.org \
    --cc=55083@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=maximedevos@telenet.be \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).