all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: 55083@debbugs.gnu.org
Subject: [bug#55083] gnu: add python-librouteros
Date: Sat, 29 Oct 2022 13:30:29 +0200	[thread overview]
Message-ID: <20221029133029.7108fa0e@primary_laptop> (raw)
In-Reply-To: <20220423164428.28465-1-GNUtoo@cyberdimension.org>

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

Hi,

In the bug report about licensing it was unclear if
python-librouteros was GPLv2 only[1] or GPLv2 or later[2].

The comments were by the same person (the project owner in github) and
the one stating that it is GPLv2 or later came after the one stating
that it is GPLv2 only.

Bundlewrap considered it as GPLv2 of that later comment[3].

So to get a definitive clarification I send a patch to librouteros
for the license clarification[4] and it was accepted.

So I can now cleanup the code, update the packages to the latest
versions if necessary and get all that merged.

Do I need to use the exact commit with the license clarification or can
I use the latest release? Or do I backport that commit?

Since it's a license clarification and not a license change, I guess
that it works retrospectively too.

References:
-----------
[1]https://github.com/luqasz/librouteros/issues/129#issuecomment-1111537090
[2]https://github.com/luqasz/librouteros/issues/129#issuecomment-1136123888
[3]https://github.com/bundlewrap/bundlewrap/issues/709#issuecomment-1249674037
[4]https://github.com/luqasz/librouteros/commit/bbf0e580ac03b818190d2a3839046dc7e1a06a90

Denis.

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

      parent reply	other threads:[~2022-10-29 11:31 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
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 ` Denis 'GNUtoo' Carikli [this message]

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=20221029133029.7108fa0e@primary_laptop \
    --to=gnutoo@cyberdimension.org \
    --cc=55083@debbugs.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 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.