From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-libs/libfontenc/
Date: Wed, 2 Dec 2015 11:16:37 +0000 (UTC) [thread overview]
Message-ID: <1449054868.11cb8c45d594d3ddde0dda403fe58996f1e2c109.ago@gentoo> (raw)
commit: 11cb8c45d594d3ddde0dda403fe58996f1e2c109
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Wed Dec 2 11:14:28 2015 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Wed Dec 2 11:14:28 2015 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=11cb8c45
x11-libs/libfontenc: ppc stable wrt bug #559062
Package-Manager: portage-2.2.20.1
RepoMan-Options: --include-arches="ppc"
x11-libs/libfontenc/libfontenc-1.1.3.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/x11-libs/libfontenc/libfontenc-1.1.3.ebuild b/x11-libs/libfontenc/libfontenc-1.1.3.ebuild
index 9ffc78e..f58e5f5 100644
--- a/x11-libs/libfontenc/libfontenc-1.1.3.ebuild
+++ b/x11-libs/libfontenc/libfontenc-1.1.3.ebuild
@@ -7,7 +7,7 @@ inherit xorg-2
DESCRIPTION="X.Org fontenc library"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc x86 ~amd64-fbsd ~x86-fbsd ~x64-freebsd ~x86-freebsd ~x86-interix ~amd64-linux ~arm-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~x64-solaris ~x86-solaris ~x86-winnt"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ppc ~ppc64 ~s390 ~sh ~sparc x86 ~amd64-fbsd ~x86-fbsd ~x64-freebsd ~x86-freebsd ~x86-interix ~amd64-linux ~arm-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~x64-solaris ~x86-solaris ~x86-winnt"
IUSE=""
RDEPEND="sys-libs/zlib
next reply other threads:[~2015-12-02 11:16 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 11:16 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-21 21:09 [gentoo-commits] repo/gentoo:master commit in: x11-libs/libfontenc/ Matt Turner
2024-04-03 5:02 Sam James
2024-04-03 5:02 Sam James
2024-04-02 19:10 Arthur Zamarin
2024-04-02 17:15 Arthur Zamarin
2024-04-02 16:37 Arthur Zamarin
2024-04-02 16:37 Arthur Zamarin
2024-04-02 16:37 Arthur Zamarin
2024-03-03 4:24 Matt Turner
2023-01-26 17:47 Matt Turner
2023-01-25 19:21 Arthur Zamarin
2023-01-24 18:27 Arthur Zamarin
2023-01-24 1:00 Sam James
2022-12-08 16:14 Matt Turner
2022-12-03 6:05 Arthur Zamarin
2022-12-02 6:32 Arthur Zamarin
2022-11-19 7:01 Arthur Zamarin
2022-11-16 18:23 Arthur Zamarin
2022-11-12 15:55 Arthur Zamarin
2022-11-12 15:50 Arthur Zamarin
2022-08-31 14:48 Matt Turner
2022-08-27 15:29 Matt Turner
2022-01-02 14:43 James Le Cuirot
2019-05-01 20:47 Matt Turner
2019-05-01 18:24 Matt Turner
2019-04-28 20:59 Sergei Trofimovich
2019-04-28 9:35 Mikle Kolyada
2019-04-28 4:21 Matt Turner
2019-04-28 0:48 Matt Turner
2019-04-27 11:52 Mikle Kolyada
2019-04-27 11:47 Mikle Kolyada
2019-04-27 4:29 Aaron Bauman
2019-04-27 3:15 Aaron Bauman
2019-02-28 5:47 Matt Turner
2018-06-22 10:48 Mikle Kolyada
2018-05-22 1:19 Matt Turner
2018-04-28 1:25 Matt Turner
2018-03-21 22:40 Mart Raudsepp
2017-01-29 21:11 Fabian Groffen
2016-11-13 9:16 Agostino Sarubbo
2016-11-12 11:52 Agostino Sarubbo
2016-06-02 17:12 Tobias Klausmann
2016-01-09 14:35 Jeroen Roovers
2015-12-19 21:42 Markus Meier
2015-12-01 10:17 Agostino Sarubbo
2015-11-30 11:51 Agostino Sarubbo
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=1449054868.11cb8c45d594d3ddde0dda403fe58996f1e2c109.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