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/gnome-boxes/
Date: Tue,  9 Apr 2019 21:09:46 +0000 (UTC)	[thread overview]
Message-ID: <1554844125.b28ffb77c9dd5ea21b55937044b20343de97106a.zlogene@gentoo> (raw)

commit:     b28ffb77c9dd5ea21b55937044b20343de97106a
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Tue Apr  9 21:08:45 2019 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Tue Apr  9 21:08:45 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b28ffb77

gnome-extra/gnome-boxes: amd64 stable wrt bug #682116

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

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

diff --git a/gnome-extra/gnome-boxes/gnome-boxes-3.26.4.ebuild b/gnome-extra/gnome-boxes/gnome-boxes-3.26.4.ebuild
index 1ec866f6c6e..2f59f01a4b0 100644
--- a/gnome-extra/gnome-boxes/gnome-boxes-3.26.4.ebuild
+++ b/gnome-extra/gnome-boxes/gnome-boxes-3.26.4.ebuild
@@ -16,7 +16,7 @@ SLOT="0"
 # We force 'bindist' due to licenses from gnome-boxes-nonfree
 IUSE="" #bindist
 
-KEYWORDS="~amd64"
+KEYWORDS="amd64"
 
 # NOTE: sys-fs/* stuff is called via exec()
 # FIXME: ovirt is not available in tree


             reply	other threads:[~2019-04-09 21:09 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 21:09 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-16 11:28 [gentoo-commits] repo/gentoo:master commit in: gnome-extra/gnome-boxes/ Pacho Ramos
2024-07-16 11:28 Pacho Ramos
2024-03-02 22:41 Mart Raudsepp
2024-02-10 18:53 Arthur Zamarin
2023-09-22  2:33 Matt Turner
2023-09-18 17:03 Matt Turner
2023-09-12 14:53 Matt Turner
2023-07-15 11:43 Arthur Zamarin
2023-05-30 15:53 Matt Turner
2023-05-02 19:02 Arthur Zamarin
2023-04-04 18:42 Matt Turner
2023-03-18  0:11 Matt Turner
2023-02-20 17:32 Matt Turner
2023-02-15  4:10 Matt Turner
2023-01-01 14:48 David Seifert
2022-12-23  0:19 Matt Turner
2022-10-30 22:29 Matt Turner
2022-10-29  2:54 Matt Turner
2022-07-07 16:01 Matt Turner
2022-07-02 20:47 Sam James
2022-05-30 19:50 Matt Turner
2022-03-27  3:54 Matt Turner
2022-01-13 22:34 Matt Turner
2022-01-05 16:44 Mart Raudsepp
2022-01-05 16:22 Mart Raudsepp
2021-10-04  1:25 Sam James
2021-07-29 20:58 Matt Turner
2021-07-08 17:35 Matt Turner
2021-06-06 21:49 Matt Turner
2021-05-29  9:02 Sam James
2021-05-03 16:24 Matt Turner
2021-04-28 16:27 Matt Turner
2020-12-18  9:00 Michał Górny
2020-08-30 18:09 Sam James
2020-08-09 13:26 Mart Raudsepp
2020-07-26 11:46 Mart Raudsepp
2020-04-04 13:05 Mart Raudsepp
2020-02-23 12:43 Mart Raudsepp
2019-08-23 19:33 Mart Raudsepp
2019-08-22 18:11 Mart Raudsepp
2019-05-18 20:46 Mart Raudsepp
2019-04-10 12:20 Mart Raudsepp
2019-03-07 21:14 Mart Raudsepp
2019-02-15 13:42 Mart Raudsepp
2019-01-23 11:34 Mart Raudsepp
2019-01-23 11:34 Mart Raudsepp
2018-04-29  0:08 Mart Raudsepp
2018-04-26 22:32 Aaron Bauman
2018-04-15 11:00 Mart Raudsepp
2018-04-11 13:45 Mart Raudsepp
2018-02-03 22:00 Mart Raudsepp
2018-01-18  3:44 Mikle Kolyada
2017-08-11  7:18 Gilles Dartiguelongue
2017-04-02 14:05 Mart Raudsepp
2017-03-23  8:25 Mart Raudsepp
2016-11-23  8:13 Gilles Dartiguelongue
2016-11-13 11:39 Gilles Dartiguelongue
2016-11-09  8:28 Gilles Dartiguelongue
2016-10-20 22:31 Gilles Dartiguelongue
2016-10-20 22:31 Gilles Dartiguelongue
2016-06-25 16:53 Pacho Ramos
2016-06-25 16:53 Pacho Ramos
2016-03-06 18:58 Mikle Kolyada
2016-03-06 18:58 Mikle Kolyada
2015-11-14 19:46 Pacho Ramos
2015-11-14 19:46 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=1554844125.b28ffb77c9dd5ea21b55937044b20343de97106a.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