public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Aaron Bauman" <bman@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-libs/libXft/
Date: Sat, 27 Apr 2019 04:29:32 +0000 (UTC)	[thread overview]
Message-ID: <1556338911.ba1f3bb13cfeeeb79b1eab2613c859ea70778801.bman@gentoo> (raw)

commit:     ba1f3bb13cfeeeb79b1eab2613c859ea70778801
Author:     Aaron Bauman <bman <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 27 04:21:51 2019 +0000
Commit:     Aaron Bauman <bman <AT> gentoo <DOT> org>
CommitDate: Sat Apr 27 04:21:51 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ba1f3bb1

x11-libs/libXft: amd64 stable wrt bug #682846

Signed-off-by: Aaron Bauman <bman <AT> gentoo.org>
Package-Manager: Portage-2.3.62, Repoman-2.3.11

 x11-libs/libXft/libXft-2.3.3.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/x11-libs/libXft/libXft-2.3.3.ebuild b/x11-libs/libXft/libXft-2.3.3.ebuild
index 60ab1b0389d..668a2532422 100644
--- a/x11-libs/libXft/libXft-2.3.3.ebuild
+++ b/x11-libs/libXft/libXft-2.3.3.ebuild
@@ -8,7 +8,7 @@ inherit xorg-3
 
 DESCRIPTION="X.Org Xft library"
 
-KEYWORDS="~alpha ~amd64 ~arm arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-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 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris ~x86-winnt"
 IUSE="doc"
 
 RDEPEND=">=media-libs/fontconfig-2.10.92[${MULTILIB_USEDEP}]


             reply	other threads:[~2019-04-27  4:29 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-27  4:29 Aaron Bauman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-05 15:40 [gentoo-commits] repo/gentoo:master commit in: x11-libs/libXft/ Matt Turner
2023-06-03 19:44 Arthur Zamarin
2023-06-01 20:04 Sam James
2023-06-01 17:04 Arthur Zamarin
2023-06-01 16:41 Arthur Zamarin
2023-06-01 16:41 Arthur Zamarin
2023-06-01 16:03 Arthur Zamarin
2023-04-17 19:36 Matt Turner
2022-11-16 18:23 Arthur Zamarin
2022-11-16  7:58 Arthur Zamarin
2022-11-12 15:55 Arthur Zamarin
2022-11-12 15:50 Arthur Zamarin
2022-09-10 15:31 Matt Turner
2022-09-06 13:44 Matt Turner
2022-01-02 13:25 James Le Cuirot
2021-11-18  7:48 Matt Turner
2021-11-17 22:55 Georgy Yakovlev
2021-11-17 16:51 Arthur Zamarin
2021-11-17  7:49 Sam James
2021-11-15  8:38 Jakov Smolić
2021-11-15  1:12 Sam James
2021-11-12 20:51 Sam James
2021-11-07 22:10 Jakov Smolić
2021-08-02  4:10 Matt Turner
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  3:15 Aaron Bauman
2019-04-26 18:06 Matt Turner
2019-04-24 16:57 Matt Turner
2019-03-16 20:01 Matt Turner
2018-06-28 14:37 Mikle Kolyada
2018-04-28  1:25 Matt Turner
2017-03-29 21:26 Michael Weber

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=1556338911.ba1f3bb13cfeeeb79b1eab2613c859ea70778801.bman@gentoo \
    --to=bman@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