From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gnome-extra/zenity/
Date: Thu, 18 Jan 2018 03:31:02 +0000 (UTC) [thread overview]
Message-ID: <1516246132.1da6ee62516179032d2b7c33f5b8234974f4ce1a.zlogene@gentoo> (raw)
commit: 1da6ee62516179032d2b7c33f5b8234974f4ce1a
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 18 03:28:52 2018 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Thu Jan 18 03:28:52 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1da6ee62
gnome-extra/zenity: amd64 stable wrt bug #631656
Package-Manager: Portage-2.3.19, Repoman-2.3.6
| 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--git a/gnome-extra/zenity/zenity-3.24.0.ebuild b/gnome-extra/zenity/zenity-3.24.0.ebuild
index 0b4b1611511..be81f8d843b 100644
--- a/gnome-extra/zenity/zenity-3.24.0.ebuild
+++ b/gnome-extra/zenity/zenity-3.24.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2017 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -9,7 +9,7 @@ HOMEPAGE="https://wiki.gnome.org/Projects/Zenity"
LICENSE="LGPL-2+"
SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~ia64 ~ppc ~ppc64 ~sh ~sparc ~x86 ~x86-fbsd ~amd64-linux ~x86-linux"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~ia64 ~ppc ~ppc64 ~sh ~sparc ~x86 ~x86-fbsd ~amd64-linux ~x86-linux"
IUSE="debug libnotify webkit"
# TODO: X11 dependency is automagically enabled
next reply other threads:[~2018-01-18 3:31 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 3:31 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-01 15:31 [gentoo-commits] repo/gentoo:master commit in: gnome-extra/zenity/ Pacho Ramos
2025-06-25 23:56 Sam James
2025-06-25 18:40 Arthur Zamarin
2025-06-16 6:20 Sam James
2024-11-08 18:16 Pacho Ramos
2024-07-15 19:22 Pacho Ramos
2024-07-15 19:22 Pacho Ramos
2024-04-07 8:38 Arthur Zamarin
2024-04-06 21:07 Arthur Zamarin
2024-01-28 11:45 Pacho Ramos
2024-01-28 11:45 Pacho Ramos
2023-12-18 10:19 Pacho Ramos
2023-12-05 10:32 Sam James
2023-11-24 13:54 Pacho Ramos
2023-11-24 13:54 Pacho Ramos
2023-11-17 7:47 Sam James
2023-10-08 11:51 Pacho Ramos
2023-10-08 11:51 Pacho Ramos
2023-09-22 3:52 Matt Turner
2023-09-22 3:52 Matt Turner
2023-08-30 7:57 Arthur Zamarin
2023-08-26 15:21 Matt Turner
2023-08-16 22:32 Matt Turner
2023-08-10 16:46 Matt Turner
2023-08-10 15:13 Matt Turner
2023-07-07 22:03 Matt Turner
2023-06-08 23:39 Matt Turner
2023-01-25 13:03 Matt Turner
2022-10-30 23:21 Matt Turner
2022-04-28 15:31 Matt Turner
2022-04-03 0:07 Matt Turner
2021-12-19 17:12 Matt Turner
2021-08-27 15:19 Yixun Lan
2021-01-18 21:10 Matt Turner
2020-01-28 9:39 Mart Raudsepp
2020-01-27 9:45 Mikle Kolyada
2020-01-26 22:39 Thomas Deutschmann
2019-12-30 22:36 Mart Raudsepp
2019-05-18 22:08 Mart Raudsepp
2019-03-15 13:16 Mart Raudsepp
2018-12-02 17:27 Mart Raudsepp
2018-08-02 20:32 Mart Raudsepp
2018-02-03 22:35 Mart Raudsepp
2017-08-12 23:15 Gilles Dartiguelongue
2016-10-24 7:22 Gilles Dartiguelongue
2016-10-24 7:22 Gilles Dartiguelongue
2016-03-06 18:58 Mikle Kolyada
2015-11-15 10:30 Pacho Ramos
2015-11-15 10:30 Pacho Ramos
2015-09-07 21:11 Mikle Kolyada
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=1516246132.1da6ee62516179032d2b7c33f5b8234974f4ce1a.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