From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libf2c/
Date: Mon, 9 Sep 2019 05:54:43 +0000 (UTC) [thread overview]
Message-ID: <1568008451.0dbb5be9e5bb3a6a8b8a5b4f5125d8fd6ce1255c.ago@gentoo> (raw)
commit: 0dbb5be9e5bb3a6a8b8a5b4f5125d8fd6ce1255c
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Mon Sep 9 05:54:11 2019 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Mon Sep 9 05:54:11 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0dbb5be9
dev-libs/libf2c: amd64 stable wrt bug #693672
Package-Manager: Portage-2.3.69, Repoman-2.3.16
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
dev-libs/libf2c/libf2c-20130927-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/libf2c/libf2c-20130927-r1.ebuild b/dev-libs/libf2c/libf2c-20130927-r1.ebuild
index 2969ed28be5..c91d0619c4f 100644
--- a/dev-libs/libf2c/libf2c-20130927-r1.ebuild
+++ b/dev-libs/libf2c/libf2c-20130927-r1.ebuild
@@ -11,7 +11,7 @@ SRC_URI="http://www.netlib.org/f2c/${PN}.zip -> ${P}.zip"
LICENSE="HPND"
SLOT="0"
-KEYWORDS="~amd64 ppc ppc64 x86 ~x86-fbsd ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 ppc ppc64 x86 ~x86-fbsd ~amd64-linux ~x86-linux"
IUSE="static-libs"
BDEPEND="app-arch/unzip"
next reply other threads:[~2019-09-09 5:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 5:54 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-05 17:54 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libf2c/ Sam James
2024-12-02 13:15 Jakov Smolić
2019-09-09 9:08 David Seifert
2019-09-08 18:30 Sergei Trofimovich
2019-09-08 18:26 Sergei Trofimovich
2015-08-23 13:35 Justin Lecher
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=1568008451.0dbb5be9e5bb3a6a8b8a5b4f5125d8fd6ce1255c.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