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: gnome-extra/zenity/
Date: Mon, 27 Jan 2020 09:45:37 +0000 (UTC)	[thread overview]
Message-ID: <1580118326.c4f54f6cb7afd7e43ce7f0ab972d032a2f9fe496.zlogene@gentoo> (raw)

commit:     c4f54f6cb7afd7e43ce7f0ab972d032a2f9fe496
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Mon Jan 27 09:42:51 2020 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Mon Jan 27 09:45:26 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c4f54f6c

gnome-extra/zenity: amd64 stable wrt bug #706524

Package-Manager: Portage-2.3.84, Repoman-2.3.20
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>

 gnome-extra/zenity/zenity-3.32.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gnome-extra/zenity/zenity-3.32.0.ebuild b/gnome-extra/zenity/zenity-3.32.0.ebuild
index 4cf9410b6ca..915aa6749dd 100644
--- a/gnome-extra/zenity/zenity-3.32.0.ebuild
+++ b/gnome-extra/zenity/zenity-3.32.0.ebuild
@@ -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 ~amd64-linux ~x86-linux"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~ia64 ~ppc ~ppc64 ~sh ~sparc x86 ~amd64-linux ~x86-linux"
 IUSE="debug libnotify webkit"
 
 # TODO: X11 dependency is automagically enabled


             reply	other threads:[~2020-01-27  9:45 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-27  9:45 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-08 18:16 [gentoo-commits] repo/gentoo:master commit in: gnome-extra/zenity/ 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-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
2018-01-18  3:31 Mikle Kolyada
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=1580118326.c4f54f6cb7afd7e43ce7f0ab972d032a2f9fe496.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