From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 55083@debbugs.gnu.org
Subject: [bug#55083] [PATCH 2/2] gnu: Add bundlewrap
Date: Tue, 26 Apr 2022 17:32:41 +0200 [thread overview]
Message-ID: <20220426173241.2ba56ef7@primarylaptop.localdomain> (raw)
In-Reply-To: <82e750be4d7b9730b48f395fd96a1c5ee1a35188.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
On Sat, 23 Apr 2022 20:49:00 +0200
Maxime Devos <maximedevos@telenet.be> wrote:
> Denis 'GNUtoo' Carikli schreef op za 23-04-2022 om 18:54 [+0200]:
> > + (license license:gpl3)))
>
> Isn't this incompatible with librouteros' license?
Yes it is.
I've deduced both licenses from the setup.py file which as I understand
constitutes a statement of the project license (according to the GPL
FAQ you need statements to be sure of the license, not just a COPYING
file), but the issue is that they don't tell if it's GPLv2-only or
GPLv2-or-later (or GPLv3-only or GPLv3-or-later for bundlewrap's).
At first I've asked librouteros to clarify the situation[1] and
if that doesn't work I can still ask bundlewrap to add an exception for
linking against GPLv2-only code.
The later is also possible because there is some copyright assignment
process when sending patches to bundlewrap[2].
References:
-----------
[1]https://github.com/luqasz/librouteros/issues/129
[2]https://github.com/bundlewrap/bundlewrap/blob/main/CAA.md
Denis.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-04-26 15:32 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220426173241.2ba56ef7@primarylaptop.localdomain \
--to=gnutoo@cyberdimension.org \
--cc=55083@debbugs.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.