From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/metis/
Date: Sun, 21 Jun 2020 17:03:55 +0000 (UTC) [thread overview]
Message-ID: <1592759027.2362a0e2d86a7bf6df0d912f92428d79e287817d.ago@gentoo> (raw)
commit: 2362a0e2d86a7bf6df0d912f92428d79e287817d
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 21 17:02:51 2020 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Sun Jun 21 17:03:47 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2362a0e2
sci-libs/metis: ppc stable wrt bug #716960
Package-Manager: Portage-2.3.99, Repoman-2.3.22
RepoMan-Options: --include-arches="ppc"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
sci-libs/metis/metis-5.1.0-r4.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sci-libs/metis/metis-5.1.0-r4.ebuild b/sci-libs/metis/metis-5.1.0-r4.ebuild
index 5f62daa4aff..ca20576419f 100644
--- a/sci-libs/metis/metis-5.1.0-r4.ebuild
+++ b/sci-libs/metis/metis-5.1.0-r4.ebuild
@@ -11,7 +11,7 @@ SRC_URI="http://glaros.dtc.umn.edu/gkhome/fetch/sw/${PN}/${P}.tar.gz"
LICENSE="Apache-2.0"
SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ia64 ppc ~ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux"
IUSE="doc openmp"
RDEPEND="!sci-libs/parmetis"
next reply other threads:[~2020-06-21 17:04 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 17:03 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-10 13:19 [gentoo-commits] repo/gentoo:master commit in: sci-libs/metis/ Sam James
2024-03-10 13:07 Arthur Zamarin
2024-03-10 12:13 Arthur Zamarin
2024-03-10 12:13 Arthur Zamarin
2024-03-10 12:13 Arthur Zamarin
2023-12-06 17:57 Ionen Wolkens
2023-12-01 3:30 Sam James
2023-08-05 11:40 Arthur Zamarin
2023-07-29 20:39 Arthur Zamarin
2023-07-17 6:12 Sam James
2023-07-17 6:12 Sam James
2023-07-14 18:02 Arthur Zamarin
2023-06-12 6:01 Arthur Zamarin
2023-06-03 9:50 WANG Xuerui
2023-05-03 10:55 Jakov Smolić
2023-05-03 8:49 Andrew Ammerlaan
2023-05-02 17:36 Arthur Zamarin
2022-12-01 3:21 WANG Xuerui
2022-10-09 16:10 Sam James
2022-09-19 6:42 Michał Górny
2021-10-06 6:22 Jakov Smolić
2021-10-06 6:06 Agostino Sarubbo
2021-10-05 6:48 Agostino Sarubbo
2021-10-04 19:19 Sam James
2021-10-04 19:19 Sam James
2021-10-04 19:17 Sam James
2021-10-04 19:16 Sam James
2021-10-04 17:44 Sam James
2021-07-20 7:41 Andrew Ammerlaan
2021-07-16 11:43 Marek Szuba
2021-07-16 11:43 Marek Szuba
2021-07-16 11:43 Marek Szuba
2021-07-14 16:14 Marek Szuba
2020-11-07 17:57 Sam James
2020-07-21 10:03 Andreas Sturmlechner
2020-07-21 10:03 Andreas Sturmlechner
2020-07-19 16:03 Sam James
2020-07-07 6:58 Sergei Trofimovich
2020-06-22 6:57 Agostino Sarubbo
2020-06-21 17:08 Agostino Sarubbo
2020-01-11 16:33 Ulrich Müller
2019-05-21 20:30 Aaron Bauman
2017-07-12 18:40 Alexis Ballier
2017-07-11 8:41 Alexis Ballier
2017-07-01 9:52 Sergei Trofimovich
2017-07-01 9:52 Sergei Trofimovich
2017-07-01 9:52 Sergei Trofimovich
2017-04-22 16:03 Justin Lecher
2017-04-22 16:03 Justin Lecher
2017-03-24 12:05 Nicolas Bock
2016-08-11 17:18 David Seifert
2016-06-07 16:47 Tobias Klausmann
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=1592759027.2362a0e2d86a7bf6df0d912f92428d79e287817d.ago@gentoo \
--to=ago@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