From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/cppunit/
Date: Sat, 11 Nov 2017 09:55:06 +0000 (UTC) [thread overview]
Message-ID: <1510394096.b8a48e3c6198ebd093422d3a7405fe613539a8d5.slyfox@gentoo> (raw)
commit: b8a48e3c6198ebd093422d3a7405fe613539a8d5
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 11 09:54:56 2017 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Nov 11 09:54:56 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b8a48e3c
dev-util/cppunit: stable 1.14.0 for ppc/ppc64, bug #637042
Package-Manager: Portage-2.3.13, Repoman-2.3.4
RepoMan-Options: --include-arches="ppc ppc64"
dev-util/cppunit/cppunit-1.14.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-util/cppunit/cppunit-1.14.0.ebuild b/dev-util/cppunit/cppunit-1.14.0.ebuild
index 6df8af21bf9..c1f4e4d1ce5 100644
--- a/dev-util/cppunit/cppunit-1.14.0.ebuild
+++ b/dev-util/cppunit/cppunit-1.14.0.ebuild
@@ -15,7 +15,7 @@ LICENSE="LGPL-2.1"
SLOT="0"
# Don't move KEYWORDS on the previous line or ekeyword won't work # 399061
[[ ${PV} = 9999 ]] || \
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sparc ~x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ppc ppc64 ~s390 ~sparc ~x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos"
IUSE="doc examples static-libs"
RDEPEND=""
next reply other threads:[~2017-11-11 9:55 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-11 9:55 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-17 19:00 [gentoo-commits] repo/gentoo:master commit in: dev-util/cppunit/ Sam James
2021-12-06 15:23 Sam James
2021-12-06 15:20 Sam James
2021-12-05 20:36 Arthur Zamarin
2021-12-05 18:39 Sam James
2021-12-05 18:32 Sam James
2021-12-05 4:45 Sam James
2021-10-02 22:52 James Le Cuirot
2021-09-07 10:19 Joonas Niilola
2021-09-07 10:19 Joonas Niilola
2021-09-07 10:19 Joonas Niilola
2021-09-07 10:19 Joonas Niilola
2021-09-07 10:19 Joonas Niilola
2021-05-25 8:25 Yixun Lan
2021-03-26 12:01 Agostino Sarubbo
2021-02-27 17:08 Sam James
2021-02-25 18:58 Sam James
2021-02-25 13:54 Agostino Sarubbo
2021-02-25 7:32 Sam James
2021-02-24 16:23 Sam James
2021-02-24 16:23 Sam James
2021-02-24 16:22 Sam James
2021-01-21 14:11 Ben Kohler
2021-01-16 13:00 Lars Wendler
2021-01-16 13:00 Lars Wendler
2018-12-08 17:41 Mikle Kolyada
2018-03-05 14:29 Mart Raudsepp
2018-03-05 9:15 Tobias Klausmann
2018-01-17 18:01 Markus Meier
2017-11-23 23:17 Sergei Trofimovich
2017-11-13 15:12 Manuel Rüger
2017-11-11 18:00 Thomas Deutschmann
2017-11-11 11:24 Sergei Trofimovich
2017-11-11 11:19 Sergei Trofimovich
2017-08-17 17:06 Michał Górny
2017-05-22 5:54 Andreas Sturmlechner
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=1510394096.b8a48e3c6198ebd093422d3a7405fe613539a8d5.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