public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/symengine/
Date: Sat, 25 Nov 2023 06:12:03 +0000 (UTC)	[thread overview]
Message-ID: <1700892694.2059beeafd7b6df9989a7945cef3efa543e93259.sam@gentoo> (raw)

commit:     2059beeafd7b6df9989a7945cef3efa543e93259
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 25 06:11:34 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Nov 25 06:11:34 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2059beea

sci-libs/symengine: Stabilize 0.10.1 arm64, #918179

Signed-off-by: Sam James <sam <AT> gentoo.org>

 sci-libs/symengine/symengine-0.10.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sci-libs/symengine/symengine-0.10.1.ebuild b/sci-libs/symengine/symengine-0.10.1.ebuild
index 5d4958377b95..eb06f3cc27bf 100644
--- a/sci-libs/symengine/symengine-0.10.1.ebuild
+++ b/sci-libs/symengine/symengine-0.10.1.ebuild
@@ -12,7 +12,7 @@ SRC_URI="https://github.com/symengine/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz
 
 LICENSE="MIT"
 SLOT="0/$(ver_cut 1-2)"
-KEYWORDS="amd64 ~arm ~arm64 ~loong ~ppc64 ~riscv ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 ~arm arm64 ~loong ~ppc64 ~riscv ~x86 ~amd64-linux ~x86-linux"
 # BUILD_FOR_DISTRIBUTION enables threads by default so do it here
 IUSE="arb benchmarks boost debug doc ecm +flint llvm +mpc +mpfr openmp test tcmalloc +threads"
 RESTRICT="!test? ( test )"


             reply	other threads:[~2023-11-25  6:12 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-25  6:12 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-15  1:39 [gentoo-commits] repo/gentoo:master commit in: sci-libs/symengine/ Sam James
2024-07-15  0:05 Sam James
2024-06-27 12:18 Michael Orlitzky
2023-11-29 18:38 Arthur Zamarin
2023-11-29 18:06 Michał Górny
2023-10-03 23:53 Sam James
2023-06-12  8:24 Arthur Zamarin
2023-04-16 12:11 WANG Xuerui
2023-03-24  2:57 Sam James
2023-03-22  9:20 Sam James
2022-11-18 17:29 Arthur Zamarin
2022-09-11 18:13 Sam James
2022-09-11 18:13 Sam James
2022-06-11  6:57 Matthias Maier
2022-06-11  6:50 Matthias Maier
2022-05-16  8:12 David Seifert
2022-03-29  8:49 Yixun Lan
2022-03-09  9:19 Agostino Sarubbo
2022-03-07 16:20 Agostino Sarubbo
2022-02-22  5:40 Yixun Lan
2022-02-21  3:17 Sam James
2022-02-21  2:49 Sam James
2021-12-30 19:10 Arthur Zamarin
2021-12-30 19:04 Arthur Zamarin
2021-12-14 19:52 Andrew Ammerlaan
2021-11-22  3:07 Yixun Lan
2021-05-04  7:03 Agostino Sarubbo
2021-04-30 15:23 Agostino Sarubbo
2020-10-27 19:58 Sam James
2020-10-27  5:11 Sam James
2020-08-31 14:15 Sam James
2020-08-31 13:49 Sam James
2020-08-30 23:18 Sam James
2020-05-02 20:15 Matthias Maier
2020-03-09 12:48 Agostino Sarubbo
2020-03-09 12:39 Agostino Sarubbo
2020-03-08 17:46 Andreas Sturmlechner
2020-03-08 17:46 Andreas Sturmlechner
2020-03-08 16:16 Andreas Sturmlechner
2020-03-08 16:02 Andreas Sturmlechner
2019-12-28 11:57 罗百科
2019-04-09  3:16 Matthias Maier
2017-08-16 18:12 Sebastien Fabbro
2017-08-03 17:33 Sebastien Fabbro
2017-07-26 20:07 Sebastien Fabbro

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=1700892694.2059beeafd7b6df9989a7945cef3efa543e93259.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