From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/superlu/
Date: Sat, 18 Aug 2018 22:36:59 +0000 (UTC) [thread overview]
Message-ID: <1534631723.ea71a4a8a5db6b48f571838caecaeb4109d981de.slyfox@gentoo> (raw)
commit: ea71a4a8a5db6b48f571838caecaeb4109d981de
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Aug 18 22:35:23 2018 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Aug 18 22:35:23 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ea71a4a8
sci-libs/superlu: stable 5.2.1-r1 for ppc64, bug #657244
Package-Manager: Portage-2.3.46, Repoman-2.3.10
RepoMan-Options: --include-arches="ppc64"
sci-libs/superlu/superlu-5.2.1-r1.ebuild | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/sci-libs/superlu/superlu-5.2.1-r1.ebuild b/sci-libs/superlu/superlu-5.2.1-r1.ebuild
index a0f4af49578..8a4ea865cdb 100644
--- a/sci-libs/superlu/superlu-5.2.1-r1.ebuild
+++ b/sci-libs/superlu/superlu-5.2.1-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2017 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -12,7 +12,7 @@ MY_PN=SuperLU
if [[ ${PV} != *9999* ]]; then
inherit versionator
SRC_URI="http://crd-legacy.lbl.gov/~xiaoye/SuperLU//${PN}_${PV}.tar.gz"
- KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux"
+ KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~ppc ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux"
SLOT="0/$(get_major_version)"
S="${WORKDIR}/SuperLU_${PV}"
else
@@ -20,7 +20,7 @@ else
GIT_ECLASS="git-r3"
EGIT_REPO_URI="https://github.com/xiaoyeli/${PN}"
SLOT="0/9999"
- KEYWORDS="~arm64 ~hppa ~ia64 ~sparc"
+ KEYWORDS="~arm64 ~hppa ~ia64 ppc64 ~sparc"
fi
DESCRIPTION="Sparse LU factorization library"
next reply other threads:[~2018-08-18 22:37 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-18 22:36 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-10 8:56 [gentoo-commits] repo/gentoo:master commit in: sci-libs/superlu/ Sam James
2023-06-03 11:15 Arthur Zamarin
2022-12-04 9:23 WANG Xuerui
2022-08-25 0:53 Sam James
2021-11-09 21:41 Jakov Smolić
2021-11-09 21:37 Sam James
2021-11-09 21:36 Sam James
2021-11-09 21:35 Sam James
2021-11-09 21:35 Sam James
2021-11-09 21:34 Sam James
2021-11-09 13:48 Jakov Smolić
2021-10-24 21:14 Sam James
2021-10-12 22:23 Marek Szuba
2021-10-04 19:33 Jakov Smolić
2021-10-04 19:33 Jakov Smolić
2021-10-02 23:17 Sam James
2021-07-14 16:15 Marek Szuba
2021-01-05 22:55 Sam James
2021-01-05 22:51 Sam James
2021-01-05 22:32 Sam James
2021-01-05 21:09 Sam James
2021-01-05 20:51 Sam James
2021-01-03 12:10 Sergei Trofimovich
2021-01-03 11:51 Sergei Trofimovich
2020-12-29 17:14 Sam James
2019-02-27 4:25 Aaron Bauman
2018-08-22 0:35 Mikle Kolyada
2017-11-27 19:46 Sergei Trofimovich
2017-10-16 3:34 David Seifert
2017-07-30 10:04 Michał Górny
2017-07-08 9:25 Alexis Ballier
2017-07-01 9:52 Sergei Trofimovich
2017-04-29 12:42 Jeroen Roovers
2016-12-22 15:40 Sebastien Fabbro
2016-12-19 23:51 Sebastien Fabbro
2016-06-07 16:47 Tobias Klausmann
2015-11-10 19:06 Markus Meier
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=1534631723.ea71a4a8a5db6b48f571838caecaeb4109d981de.slyfox@gentoo \
--to=slyfox@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