From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-mathematics/polymake/
Date: Sun, 27 Oct 2024 03:07:01 +0000 (UTC) [thread overview]
Message-ID: <1729998387.87bedcbb09f84a5c2a23e2fb35f66bd686bc3a36.mjo@gentoo> (raw)
commit: 87bedcbb09f84a5c2a23e2fb35f66bd686bc3a36
Author: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 27 03:02:00 2024 +0000
Commit: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Sun Oct 27 03:06:27 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=87bedcbb
sci-mathematics/polymake: un-keyword for x86
Despite the fact that USE=lrs is masked for x86, pkgcheck is throwing a
fit about the fact that I've un-keyworded sci-libs/lrslib for x86 (it
doesn't even build on x86), and is turning the CI red. So to fix that,
I'm un-keywording polymake too.
I'll file a bug for x86@, but this is a pretty niche application and
probably nobody cares.
Signed-off-by: Michael Orlitzky <mjo <AT> gentoo.org>
sci-mathematics/polymake/polymake-4.11.ebuild | 2 +-
sci-mathematics/polymake/polymake-4.12.ebuild | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/sci-mathematics/polymake/polymake-4.11.ebuild b/sci-mathematics/polymake/polymake-4.11.ebuild
index 8c6be02dd591..afcd2acf56a5 100644
--- a/sci-mathematics/polymake/polymake-4.11.ebuild
+++ b/sci-mathematics/polymake/polymake-4.11.ebuild
@@ -18,7 +18,7 @@ HOMEPAGE="https://polymake.org/"
# closer look at how (or even if) the corresponding code is being used.
LICENSE="BSD GPL-2 GPL-2+ MIT WTFPL-2"
SLOT="0"
-KEYWORDS="amd64 ~riscv ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 ~riscv ~amd64-linux"
IUSE="bliss +cdd +flint +normaliz libpolymake lrs nauty ppl singular"
REQUIRED_USE="^^ ( bliss nauty )"
diff --git a/sci-mathematics/polymake/polymake-4.12.ebuild b/sci-mathematics/polymake/polymake-4.12.ebuild
index a4232f80fa1b..1022ff12e0cc 100644
--- a/sci-mathematics/polymake/polymake-4.12.ebuild
+++ b/sci-mathematics/polymake/polymake-4.12.ebuild
@@ -18,7 +18,7 @@ SRC_URI="https://polymake.org/lib/exe/fetch.php/download/${P}-minimal.tar.bz2"
# closer look at how (or even if) the corresponding code is being used.
LICENSE="BSD GPL-2 GPL-2+ MIT WTFPL-2"
SLOT="0"
-KEYWORDS="~amd64 ~riscv ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~amd64 ~riscv ~amd64-linux"
IUSE="bliss +cdd +flint +normaliz libpolymake lrs nauty ppl singular"
REQUIRED_USE="^^ ( bliss nauty )"
next reply other threads:[~2024-10-27 3:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 3:07 Michael Orlitzky [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-10 6:58 [gentoo-commits] repo/gentoo:master commit in: sci-mathematics/polymake/ Ionen Wolkens
2023-07-04 22:03 Sam James
2023-05-22 1:40 Michael Orlitzky
2022-12-23 20:49 Arthur Zamarin
2022-12-21 11:45 Michael Orlitzky
2022-12-21 11:45 Michael Orlitzky
2022-12-11 11:46 Andreas K. Hüttel
2022-09-09 19:09 Michael Orlitzky
2022-02-07 10:26 Jakov Smolić
2022-01-30 22:54 Michael Orlitzky
2021-12-29 13:46 Yixun Lan
2021-10-23 0:17 Michael Orlitzky
2020-06-27 20:45 Andreas K. Hüttel
2017-05-14 22:53 Patrice Clement
2017-02-18 22:41 Andreas Hüttel
2016-09-30 11:46 Thomas Kahle
2016-05-14 23:32 David Seifert
2016-05-14 23:32 David Seifert
2016-05-14 23:32 David Seifert
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=1729998387.87bedcbb09f84a5c2a23e2fb35f66bd686bc3a36.mjo@gentoo \
--to=mjo@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