From: Maxime Devos <maximedevos@telenet.be>
To: "Denis 'GNUtoo' Carikli" <GNUtoo@cyberdimension.org>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: 55083@debbugs.gnu.org
Subject: [bug#55083] [PATCH 1/2] gnu: add python-librouteros
Date: Mon, 23 May 2022 18:37:50 +0200 [thread overview]
Message-ID: <eb7b8580688a3040620ba96abea021bfcd4ed992.camel@telenet.be> (raw)
In-Reply-To: <20220523180849.02eda788@primarylaptop.localdomain>
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
Denis 'GNUtoo' Carikli schreef op ma 23-05-2022 om 18:08 [+0200]:
> I could do that but we can only merge python-librouteros.
>
> python-librouteros doesn't want to change license
Upstream clarified it's GPLv2-only, but AFAICT hasn't explicitly
expressed any opinion on whether they would mind relicensing. I asked
for clarification [1]
[1]: <https://github.com/luqasz/librouteros/issues/129#issuecomment-1134892145>
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-05-23 16:39 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
2022-05-23 16:37 ` Maxime Devos [this message]
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=eb7b8580688a3040620ba96abea021bfcd4ed992.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55083@debbugs.gnu.org \
--cc=GNUtoo@cyberdimension.org \
--cc=ludo@gnu.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.
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).