From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/igraph/
Date: Thu, 9 May 2024 20:43:03 +0000 (UTC) [thread overview]
Message-ID: <1715287101.f699a76425d24e1ead794be9a8488dc26f8640ab.sam@gentoo> (raw)
commit: f699a76425d24e1ead794be9a8488dc26f8640ab
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu May 9 20:38:21 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu May 9 20:38:21 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f699a764
dev-libs/igraph: update LICENSE
Per the bug, it's GPL-2+ (see https://igraph.org/c/html/latest/igraph-Introduction.html#igraph-is-free-software).
Closes: https://bugs.gentoo.org/914971
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-libs/igraph/igraph-0.10.10.ebuild | 2 +-
dev-libs/igraph/igraph-0.10.11.ebuild | 2 +-
dev-libs/igraph/igraph-0.10.4-r1.ebuild | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/dev-libs/igraph/igraph-0.10.10.ebuild b/dev-libs/igraph/igraph-0.10.10.ebuild
index cb7c5a2e937c..7f5111f0726e 100644
--- a/dev-libs/igraph/igraph-0.10.10.ebuild
+++ b/dev-libs/igraph/igraph-0.10.10.ebuild
@@ -9,7 +9,7 @@ DESCRIPTION="Creating and manipulating undirected and directed graphs"
HOMEPAGE="https://igraph.org/"
SRC_URI="https://github.com/igraph/igraph/releases/download/${PV}/${P}.tar.gz"
-LICENSE="GPL-2"
+LICENSE="GPL-2+"
SLOT="0/0"
KEYWORDS="~amd64 ~x86"
diff --git a/dev-libs/igraph/igraph-0.10.11.ebuild b/dev-libs/igraph/igraph-0.10.11.ebuild
index 0553751b2bcf..30a8f524a0b5 100644
--- a/dev-libs/igraph/igraph-0.10.11.ebuild
+++ b/dev-libs/igraph/igraph-0.10.11.ebuild
@@ -9,7 +9,7 @@ DESCRIPTION="Creating and manipulating undirected and directed graphs"
HOMEPAGE="https://igraph.org/"
SRC_URI="https://github.com/igraph/igraph/releases/download/${PV}/${P}.tar.gz"
-LICENSE="GPL-2"
+LICENSE="GPL-2+"
SLOT="0/0"
KEYWORDS="~amd64 ~x86"
diff --git a/dev-libs/igraph/igraph-0.10.4-r1.ebuild b/dev-libs/igraph/igraph-0.10.4-r1.ebuild
index 9ccfb98c5cbb..a8d0b8c64efd 100644
--- a/dev-libs/igraph/igraph-0.10.4-r1.ebuild
+++ b/dev-libs/igraph/igraph-0.10.4-r1.ebuild
@@ -9,7 +9,7 @@ DESCRIPTION="Creating and manipulating undirected and directed graphs"
HOMEPAGE="https://igraph.org/"
SRC_URI="https://github.com/igraph/igraph/releases/download/${PV}/${P}.tar.gz"
-LICENSE="GPL-2"
+LICENSE="GPL-2+"
SLOT="0/0"
KEYWORDS="amd64 x86"
next reply other threads:[~2024-05-09 20:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 20:43 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-09 21:46 [gentoo-commits] repo/gentoo:master commit in: dev-libs/igraph/ Sam James
2024-05-09 21:46 Sam James
2024-05-09 20:43 Sam James
2024-05-09 20:43 Sam James
2024-04-07 14:02 David Seifert
2024-03-11 14:24 Sam James
2024-03-11 14:24 Sam James
2023-12-16 16:17 Arthur Zamarin
2023-05-22 20:12 Michael Orlitzky
2023-05-01 0:30 Sam James
2023-05-01 0:12 Sam James
2023-02-10 12:51 Andrew Ammerlaan
2022-12-20 19:27 Sam James
2022-12-20 19:26 Sam James
2022-12-20 19:26 Sam James
2021-06-17 17:49 David Seifert
2021-02-27 19:33 Sam James
2021-02-26 22:45 Sam James
2020-12-27 3:51 Sam James
2020-11-14 22:47 David Seifert
2020-08-23 17:01 David Seifert
2016-06-03 13:23 Michael Orlitzky
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=1715287101.f699a76425d24e1ead794be9a8488dc26f8640ab.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox