From: "Aaron Bauman" <bman@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-libs/libXcursor/
Date: Sat, 27 Apr 2019 04:29:32 +0000 (UTC) [thread overview]
Message-ID: <1556338767.8e9e74ce81a4e6c8e96865479df5ae6a3cd6ba7a.bman@gentoo> (raw)
commit: 8e9e74ce81a4e6c8e96865479df5ae6a3cd6ba7a
Author: Aaron Bauman <bman <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 27 04:19:27 2019 +0000
Commit: Aaron Bauman <bman <AT> gentoo <DOT> org>
CommitDate: Sat Apr 27 04:19:27 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8e9e74ce
x11-libs/libXcursor: 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/libXcursor/libXcursor-1.2.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/x11-libs/libXcursor/libXcursor-1.2.0.ebuild b/x11-libs/libXcursor/libXcursor-1.2.0.ebuild
index 8c6e5a87cf1..cb8d0b1f9b8 100644
--- a/x11-libs/libXcursor/libXcursor-1.2.0.ebuild
+++ b/x11-libs/libXcursor/libXcursor-1.2.0.ebuild
@@ -8,7 +8,7 @@ inherit xorg-3
DESCRIPTION="X.Org Xcursor 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 ~x64-solaris ~x86-solaris"
+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 ~x64-solaris ~x86-solaris"
IUSE="doc"
RDEPEND=">=x11-libs/libXrender-0.9.8[${MULTILIB_USEDEP}]
next reply other threads:[~2019-04-27 4:29 UTC|newest]
Thread overview: 48+ 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 --
2024-11-06 18:42 [gentoo-commits] repo/gentoo:master commit in: x11-libs/libXcursor/ Matt Turner
2024-04-24 17:32 Matt Turner
2024-04-22 16:58 Arthur Zamarin
2024-04-19 6:39 Ionen Wolkens
2024-04-03 22:32 Sam James
2024-04-03 22:24 Sam James
2024-04-03 22:24 Sam James
2024-04-03 20:43 Arthur Zamarin
2024-04-03 20:43 Arthur Zamarin
2024-04-03 20:43 Arthur Zamarin
2024-03-04 17:07 Matt Turner
2024-03-03 4:24 Matt Turner
2022-05-29 15:23 Matt Turner
2022-05-28 1:35 Sam James
2022-05-25 18:00 Jakov Smolić
2022-05-25 17:57 Jakov Smolić
2022-05-17 7:56 WANG Xuerui
2022-05-10 16:19 Arthur Zamarin
2022-05-08 23:01 Sam James
2022-05-07 17:55 Jakov Smolić
2022-04-03 17:20 Matt Turner
2022-01-09 10:04 James Le Cuirot
2021-05-19 9:23 Yixun Lan
2021-05-02 15:24 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-11 6:10 Matt Turner
2018-12-30 21:38 Mikle Kolyada
2018-05-04 12:03 Mart Raudsepp
2018-01-05 18:50 Matt Turner
2017-12-13 21:12 Markus Meier
2017-12-01 7:32 Sergei Trofimovich
2017-11-30 20:19 Tobias Klausmann
2017-11-29 20:28 Sergei Trofimovich
2017-11-29 18:52 Thomas Deutschmann
2017-11-29 11:19 Agostino Sarubbo
2017-11-29 1:39 Matt Turner
2017-01-29 21:11 Fabian Groffen
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=1556338767.8e9e74ce81a4e6c8e96865479df5ae6a3cd6ba7a.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