From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-fonts/fontawesome/
Date: Mon, 12 Aug 2019 09:11:51 +0000 (UTC) [thread overview]
Message-ID: <1565601077.f5511d50006015b0fbc6fff341f975e5413b6aea.ago@gentoo> (raw)
commit: f5511d50006015b0fbc6fff341f975e5413b6aea
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Mon Aug 12 09:11:17 2019 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Mon Aug 12 09:11:17 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f5511d50
media-fonts/fontawesome: amd64 stable wrt bug #691918
Package-Manager: Portage-2.3.69, Repoman-2.3.16
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
media-fonts/fontawesome/fontawesome-4.7.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/media-fonts/fontawesome/fontawesome-4.7.0.ebuild b/media-fonts/fontawesome/fontawesome-4.7.0.ebuild
index 89ccde4834f..04e6bd276a8 100644
--- a/media-fonts/fontawesome/fontawesome-4.7.0.ebuild
+++ b/media-fonts/fontawesome/fontawesome-4.7.0.ebuild
@@ -13,7 +13,7 @@ SRC_URI="https://github.com/FortAwesome/${REPO_PN}/archive/v${PV}.tar.gz -> ${P}
LICENSE="CC-BY-3.0 OFL-1.1"
SLOT="0/4"
-KEYWORDS="~amd64 ~arm arm64 x86"
+KEYWORDS="amd64 ~arm arm64 x86"
IUSE="+otf +ttf"
REQUIRED_USE="|| ( otf ttf )"
next reply other threads:[~2019-08-12 9:11 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 9:11 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-24 20:25 [gentoo-commits] repo/gentoo:master commit in: media-fonts/fontawesome/ Andreas Sturmlechner
2024-09-24 20:25 Andreas Sturmlechner
2024-09-23 7:25 Arthur Zamarin
2024-01-13 13:09 Florian Schmaus
2024-01-13 13:09 Florian Schmaus
2024-01-13 13:09 Florian Schmaus
2024-01-13 13:09 Florian Schmaus
2023-12-20 15:19 Sam James
2022-05-25 8:29 WANG Xuerui
2022-05-25 8:29 WANG Xuerui
2022-04-17 9:34 Joonas Niilola
2021-12-05 4:45 Sam James
2021-05-04 13:38 Joonas Niilola
2021-01-22 4:15 Sam James
2020-12-29 9:47 Sam James
2020-10-12 9:06 Joonas Niilola
2020-10-12 9:06 Joonas Niilola
2020-09-30 22:59 Sam James
2020-07-21 1:48 Aaron Bauman
2020-06-20 20:31 Thomas Deutschmann
2020-05-22 19:35 Georgy Yakovlev
2020-05-22 19:35 Georgy Yakovlev
2020-04-28 7:44 Joonas Niilola
2019-09-25 7:08 Michał Górny
2019-09-25 7:08 Michał Górny
2019-09-19 6:02 Michał Górny
2019-09-19 6:02 Michał Górny
2019-09-13 17:39 Mikle Kolyada
2019-08-28 5:02 Joonas Niilola
2019-08-28 5:02 Joonas Niilola
2019-08-25 15:49 Joonas Niilola
2019-08-25 15:49 Joonas Niilola
2019-08-11 21:40 Aaron Bauman
2019-08-04 6:44 Joonas Niilola
2019-08-04 6:44 Joonas Niilola
2019-08-03 15:12 Joonas Niilola
2019-07-30 20:55 Georgy Yakovlev
2019-07-29 14:27 Mikle Kolyada
2019-07-22 21:36 Aaron Bauman
2019-06-21 11:07 Agostino Sarubbo
2019-06-21 8:03 Agostino Sarubbo
2018-07-17 13:10 Johannes Huber
2018-02-19 18:41 Andreas Sturmlechner
2018-02-19 18:41 Andreas Sturmlechner
2018-01-26 19:18 Patrice Clement
2018-01-26 19:18 Patrice Clement
2018-01-26 19:18 Patrice Clement
2017-11-25 14:39 Patrick Lauer
2016-10-25 18:32 David Seifert
2016-08-23 9:14 Patrice Clement
2016-05-27 14:01 Patrice Clement
2016-05-27 14:01 Patrice Clement
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=1565601077.f5511d50006015b0fbc6fff341f975e5413b6aea.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