public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/atk/
Date: Thu, 18 Jan 2018 02:08:26 +0000 (UTC)	[thread overview]
Message-ID: <1516241297.25232d61740da9c0ccf768827ab1ae0d2e43c924.zlogene@gentoo> (raw)

commit:     25232d61740da9c0ccf768827ab1ae0d2e43c924
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 18 01:59:55 2018 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Thu Jan 18 02:08:17 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=25232d61

dev-libs/atk: amd64 stable wrt bug #631656

Package-Manager: Portage-2.3.19, Repoman-2.3.6

 dev-libs/atk/atk-2.24.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-libs/atk/atk-2.24.0.ebuild b/dev-libs/atk/atk-2.24.0.ebuild
index d35db91b40a..47e0f1ae659 100644
--- a/dev-libs/atk/atk-2.24.0.ebuild
+++ b/dev-libs/atk/atk-2.24.0.ebuild
@@ -9,7 +9,7 @@ HOMEPAGE="https://wiki.gnome.org/Accessibility"
 
 LICENSE="LGPL-2+"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh sparc ~x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~arm-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 ~arm-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris ~x86-winnt"
 IUSE="+introspection nls test"
 
 RDEPEND="


             reply	other threads:[~2018-01-18  2:08 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18  2:08 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-16 18:10 [gentoo-commits] repo/gentoo:master commit in: dev-libs/atk/ Arthur Zamarin
2022-10-29 23:21 Matt Turner
2022-05-17  7:56 WANG Xuerui
2022-03-25 18:25 Matt Turner
2021-05-19  9:23 Yixun Lan
2021-04-12 21:59 Matt Turner
2020-11-14  9:19 Mikle Kolyada
2020-11-06 15:19 Sam James
2020-11-05 16:16 Sam James
2020-09-11 16:57 Sergei Trofimovich
2020-08-31  2:52 Sam James
2020-06-07 21:28 Mart Raudsepp
2020-05-13 17:35 Sergei Trofimovich
2020-04-26  1:54 Matt Turner
2020-03-25  2:20 Matt Turner
2020-02-09 15:56 Mart Raudsepp
2020-01-11 19:40 Mart Raudsepp
2020-01-11 19:40 Mart Raudsepp
2020-01-01 15:25 Agostino Sarubbo
2019-12-24 17:03 Sergei Trofimovich
2019-12-09  9:14 Agostino Sarubbo
2019-12-09  9:11 Agostino Sarubbo
2019-12-08 11:59 Mikle Kolyada
2019-12-08 11:58 Mikle Kolyada
2019-12-08 11:55 Mikle Kolyada
2019-10-21 19:51 Matt Turner
2019-09-19  7:15 Mart Raudsepp
2019-06-17 19:40 Sergei Trofimovich
2019-05-10 17:33 Mikle Kolyada
2019-05-09 20:04 Aaron Bauman
2019-02-18 19:00 Mart Raudsepp
2018-12-29 20:43 Mart Raudsepp
2018-12-29 16:00 Sergei Trofimovich
2018-12-28  3:46 Matt Turner
2018-12-08 17:41 Mikle Kolyada
2018-12-05  7:34 Mikle Kolyada
2018-12-05  7:07 Mikle Kolyada
2018-12-04 16:27 Mikle Kolyada
2018-11-06 23:11 Sergei Trofimovich
2018-08-30 20:50 Mart Raudsepp
2018-03-14 21:41 Sergei Trofimovich
2018-03-06 21:37 Tobias Klausmann
2018-03-04 20:48 Sergei Trofimovich
2018-02-16 20:39 Sergei Trofimovich
2018-01-27  0:41 Thomas Deutschmann
2018-01-13 12:13 Sergei Trofimovich
2017-08-15 22:44 Gilles Dartiguelongue
2017-07-07 10:12 Agostino Sarubbo
2017-04-12 10:10 Jeroen Roovers
2017-03-29  7:45 Michael Weber
2017-03-28 15:09 Michael Weber
2017-03-28 14:59 Michael Weber
2017-01-29 16:07 Fabian Groffen
2016-12-06 20:18 Markus Meier
2016-11-01 23:58 Gilles Dartiguelongue
2016-05-03 19:26 Markus Meier
2015-11-16 21:56 Pacho Ramos
2015-11-16 21:56 Pacho Ramos
2015-10-03  8:09 Markus Meier

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=1516241297.25232d61740da9c0ccf768827ab1ae0d2e43c924.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