From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-fonts/unifont/
Date: Sun, 24 Dec 2017 11:11:31 +0000 (UTC) [thread overview]
Message-ID: <1514113885.5c140f14aefa3ed54db0a5a91dff2ba29d5c68d9.slyfox@gentoo> (raw)
commit: 5c140f14aefa3ed54db0a5a91dff2ba29d5c68d9
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sun Dec 24 11:09:14 2017 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sun Dec 24 11:11:25 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5c140f14
media-fonts/unifont: stable 10.0.06 for ppc/ppc64, bug #641316
Package-Manager: Portage-2.3.19, Repoman-2.3.6
RepoMan-Options: --include-arches="ppc ppc64"
media-fonts/unifont/unifont-10.0.06.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/media-fonts/unifont/unifont-10.0.06.ebuild b/media-fonts/unifont/unifont-10.0.06.ebuild
index a7bed22ec21..87b7a0814c7 100644
--- a/media-fonts/unifont/unifont-10.0.06.ebuild
+++ b/media-fonts/unifont/unifont-10.0.06.ebuild
@@ -11,7 +11,7 @@ SRC_URI="mirror://gnu/${PN}/${P}/${P}.tar.gz"
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ia64 ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~x86-fbsd"
+KEYWORDS="~alpha amd64 ~arm ia64 ppc ppc64 ~s390 ~sh ~sparc ~x86 ~x86-fbsd"
IUSE="fontforge utils"
DEPEND="
next reply other threads:[~2017-12-25 1:19 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-24 11:11 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-07 4:27 [gentoo-commits] repo/gentoo:master commit in: media-fonts/unifont/ WANG Xuerui
2022-08-02 18:47 Arthur Zamarin
2022-07-30 16:16 Arthur Zamarin
2022-07-30 8:59 Agostino Sarubbo
2022-07-29 17:09 Arthur Zamarin
2022-07-29 17:09 Arthur Zamarin
2022-07-29 17:09 Arthur Zamarin
2022-05-31 4:46 Sam James
2022-05-25 8:29 WANG Xuerui
2022-05-08 19:45 Matt Turner
2022-03-22 18:43 Jakov Smolić
2021-06-03 19:13 Andreas K. Hüttel
2021-01-24 18:48 Mike Gilbert
2020-05-28 15:45 Agostino Sarubbo
2020-05-28 15:43 Agostino Sarubbo
2020-05-28 15:42 Agostino Sarubbo
2020-05-28 15:40 Agostino Sarubbo
2020-05-28 15:39 Agostino Sarubbo
2020-05-28 15:37 Agostino Sarubbo
2020-03-29 2:11 Mike Gilbert
2020-03-29 2:11 Mike Gilbert
2020-03-29 2:11 Mike Gilbert
2020-03-29 2:11 Mike Gilbert
2018-03-17 13:27 Mikle Kolyada
2018-02-06 18:36 Thomas Deutschmann
2018-01-29 8:22 Tobias Klausmann
2018-01-04 22:11 Sergei Trofimovich
2017-12-21 11:05 Sergei Trofimovich
2017-12-18 16:18 Jason Zaman
2017-08-28 15:20 Mike Gilbert
2017-08-04 16:19 Mike Gilbert
2017-07-08 18:18 Mike Gilbert
2017-07-08 18:18 Mike Gilbert
2017-07-08 18:18 Mike Gilbert
2017-06-15 16:05 Markus Meier
2017-06-10 15:10 Agostino Sarubbo
2017-06-04 19:20 Tobias Klausmann
2017-05-31 13:06 Agostino Sarubbo
2016-12-23 19:35 Mike Gilbert
2016-10-30 3:22 Mike Gilbert
2016-09-02 15:43 Mike Gilbert
2016-07-03 19:09 Mike Gilbert
2016-07-03 19:09 Mike Gilbert
2016-05-26 13:43 Tobias Klausmann
2016-03-25 9:44 Markus Meier
2016-03-20 11:53 Agostino Sarubbo
2016-03-19 11:35 Agostino Sarubbo
2016-03-17 10:50 Agostino Sarubbo
2016-03-16 11:51 Agostino Sarubbo
2016-03-15 15:27 Agostino Sarubbo
2016-03-06 12:58 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=1514113885.5c140f14aefa3ed54db0a5a91dff2ba29d5c68d9.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