public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Thomas Deutschmann" <whissi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gnome-base/gnome-core-libs/
Date: Sat, 29 Dec 2018 19:39:31 +0000 (UTC)	[thread overview]
Message-ID: <1546112364.914ad66702ee2b2e7e722608c587bf5a2b4975dd.whissi@gentoo> (raw)

commit:     914ad66702ee2b2e7e722608c587bf5a2b4975dd
Author:     Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
AuthorDate: Sat Dec 29 19:37:40 2018 +0000
Commit:     Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
CommitDate: Sat Dec 29 19:39:24 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=914ad667

gnome-base/gnome-core-libs: x86 keyworded (bug #673156)

Package-Manager: Portage-2.3.53, Repoman-2.3.12
Signed-off-by: Thomas Deutschmann <whissi <AT> gentoo.org>

 gnome-base/gnome-core-libs/gnome-core-libs-3.26.2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gnome-base/gnome-core-libs/gnome-core-libs-3.26.2.ebuild b/gnome-base/gnome-core-libs/gnome-core-libs-3.26.2.ebuild
index eb913408f5b..a0248826260 100644
--- a/gnome-base/gnome-core-libs/gnome-core-libs-3.26.2.ebuild
+++ b/gnome-base/gnome-core-libs/gnome-core-libs-3.26.2.ebuild
@@ -11,7 +11,7 @@ IUSE="cups python"
 
 # when unmasking for an arch
 # double check none of the deps are still masked !
-KEYWORDS="~alpha ~amd64 ~ia64 ~ppc ~ppc64 ~sparc"
+KEYWORDS="~alpha ~amd64 ~ia64 ~ppc ~ppc64 ~sparc ~x86"
 
 # Note to developers:
 # This is a wrapper for the core libraries used by GNOME 3


             reply	other threads:[~2018-12-29 19:39 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-29 19:39 Thomas Deutschmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-06  7:09 [gentoo-commits] repo/gentoo:master commit in: gnome-base/gnome-core-libs/ Mart Raudsepp
2024-04-22  8:20 Arthur Zamarin
2024-04-20  9:51 Michał Górny
2024-04-15  5:49 Arthur Zamarin
2023-12-21 19:44 Mart Raudsepp
2023-12-18 23:37 Mart Raudsepp
2023-12-18 23:37 Mart Raudsepp
2023-12-18 23:37 Mart Raudsepp
2023-07-27  8:29 WANG Xuerui
2022-03-12 23:41 Mart Raudsepp
2022-03-12 23:39 Mart Raudsepp
2021-12-15 22:29 Mart Raudsepp
2021-07-08 17:35 Matt Turner
2021-05-12 22:10 Matt Turner
2020-07-19 17:58 Mart Raudsepp
2020-03-16 22:20 Mart Raudsepp
2019-12-23 21:26 Mart Raudsepp
2019-09-19  7:15 Mart Raudsepp
2019-07-29  9:42 Aaron Bauman
2019-05-18 20:46 Mart Raudsepp
2019-03-30 21:56 Mart Raudsepp
2019-03-11 16:16 Mart Raudsepp
2019-03-02 23:12 Mart Raudsepp
2019-02-17 15:56 Mikle Kolyada
2018-12-19 22:27 Sergei Trofimovich
2018-12-16 11:40 Sergei Trofimovich
2018-12-14 22:55 Mart Raudsepp
2018-02-03 20:56 Mart Raudsepp
2018-01-18  3:15 Mikle Kolyada
2018-01-10  6:12 Mart Raudsepp
2017-08-15 22:44 Gilles Dartiguelongue
2017-04-02 13:03 Mart Raudsepp
2017-02-20 17:43 Mart Raudsepp
2017-02-20 17:43 Mart Raudsepp
2017-02-15 19:43 Mart Raudsepp
2016-11-12  0:37 Gilles Dartiguelongue
2016-11-12  0:37 Gilles Dartiguelongue
2016-10-12  7:28 Gilles Dartiguelongue
2016-09-05  7:18 Gilles Dartiguelongue
2016-03-06 17:23 Mikle Kolyada
2015-12-06 23:41 Gilles Dartiguelongue

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=1546112364.914ad66702ee2b2e7e722608c587bf5a2b4975dd.whissi@gentoo \
    --to=whissi@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