From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-libs/libXau/
Date: Sat, 27 Apr 2019 11:47:51 +0000 (UTC) [thread overview]
Message-ID: <1556365598.581e3c47757c52bad0acd00b7435c69cfe53b6df.zlogene@gentoo> (raw)
commit: 581e3c47757c52bad0acd00b7435c69cfe53b6df
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 27 11:46:38 2019 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sat Apr 27 11:46:38 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=581e3c47
x11-libs/libXau: arm stable wrt bug #682846
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
Package-Manager: Portage-2.3.62, Repoman-2.3.11
RepoMan-Options: --include-arches="arm"
x11-libs/libXau/libXau-1.0.9.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/x11-libs/libXau/libXau-1.0.9.ebuild b/x11-libs/libXau/libXau-1.0.9.ebuild
index c91fd6c2c04..9c30eae8b91 100644
--- a/x11-libs/libXau/libXau-1.0.9.ebuild
+++ b/x11-libs/libXau/libXau-1.0.9.ebuild
@@ -8,7 +8,7 @@ inherit xorg-2
DESCRIPTION="X.Org X authorization library"
-KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~ppc-aix ~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 ~ppc-aix ~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=""
RDEPEND="x11-base/xorg-proto"
next reply other threads:[~2019-04-27 11:48 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 11:47 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-26 20:34 [gentoo-commits] repo/gentoo:master commit in: x11-libs/libXau/ Matt Turner
2025-01-24 3:55 Matt Turner
2025-01-18 7:11 Arthur Zamarin
2025-01-17 19:31 Arthur Zamarin
2025-01-17 19:29 Arthur Zamarin
2025-01-17 19:13 Arthur Zamarin
2024-12-14 2:19 Matt Turner
2023-01-26 17:47 Matt Turner
2023-01-24 18:27 Arthur Zamarin
2023-01-24 1:00 Sam James
2022-12-08 16:14 Matt Turner
2022-11-19 7:01 Arthur Zamarin
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-08-27 15:29 Matt Turner
2022-05-08 3:10 WANG Xuerui
2022-01-01 15:10 James Le Cuirot
2020-12-31 16:59 Matt Turner
2020-12-27 18:28 Fabian Groffen
2020-12-20 19:17 Thomas Deutschmann
2020-12-19 15:08 Sam James
2020-12-13 23:30 Sam James
2020-12-09 22:38 Sergei Trofimovich
2020-12-07 22:11 Matt Turner
2020-12-07 15:27 Sam James
2020-12-07 5:23 Sam James
2020-12-06 20:48 Sam James
2020-11-08 1:31 Matt Turner
2019-06-12 17:08 Michael Haubenwallner
2019-05-01 20:47 Matt Turner
2019-05-01 18:24 Matt Turner
2019-04-30 15:37 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 4:29 Aaron Bauman
2019-04-27 3:15 Aaron Bauman
2019-02-10 23:10 Matt Turner
2018-06-08 8:05 Mikle Kolyada
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=1556365598.581e3c47757c52bad0acd00b7435c69cfe53b6df.zlogene@gentoo \
--to=zlogene@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