From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gnome-base/gnome-settings-daemon/
Date: Thu, 18 Jan 2018 02:35:40 +0000 (UTC) [thread overview]
Message-ID: <1516242868.d2d1d029e0e0733af3f2856c3fd9bc76672dc4d3.zlogene@gentoo> (raw)
commit: d2d1d029e0e0733af3f2856c3fd9bc76672dc4d3
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 18 02:34:28 2018 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Thu Jan 18 02:34:28 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d2d1d029
gnome-base/gnome-settings-daemon: amd64 stable wrt bug #631656
Package-Manager: Portage-2.3.19, Repoman-2.3.6
gnome-base/gnome-settings-daemon/gnome-settings-daemon-3.24.3.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gnome-base/gnome-settings-daemon/gnome-settings-daemon-3.24.3.ebuild b/gnome-base/gnome-settings-daemon/gnome-settings-daemon-3.24.3.ebuild
index 1b5f1cb13c9..08ef2d56a27 100644
--- a/gnome-base/gnome-settings-daemon/gnome-settings-daemon-3.24.3.ebuild
+++ b/gnome-base/gnome-settings-daemon/gnome-settings-daemon-3.24.3.ebuild
@@ -20,7 +20,7 @@ REQUIRED_USE="
smartcard? ( udev )
wayland? ( udev )
"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~ia64 ~ppc ~ppc64 ~sparc ~x86 ~x86-fbsd ~amd64-linux ~x86-linux ~x86-solaris"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~ia64 ~ppc ~ppc64 ~sparc ~x86 ~x86-fbsd ~amd64-linux ~x86-linux ~x86-solaris"
COMMON_DEPEND="
>=dev-libs/glib-2.44.0:2[dbus]
next reply other threads:[~2018-01-18 2:35 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 2:35 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-07 10:50 [gentoo-commits] repo/gentoo:master commit in: gnome-base/gnome-settings-daemon/ Pacho Ramos
2024-08-03 14:11 Pacho Ramos
2024-04-20 11:42 Mart Raudsepp
2024-04-17 6:54 Sam James
2024-04-07 6:23 Arthur Zamarin
2024-04-07 5:55 Arthur Zamarin
2024-03-09 15:35 Mart Raudsepp
2024-02-11 14:21 Mart Raudsepp
2024-02-11 8:09 Arthur Zamarin
2023-09-24 9:02 WANG Xuerui
2023-09-16 18:48 Matt Turner
2023-09-10 14:24 Matt Turner
2023-08-12 23:42 Matt Turner
2023-07-27 5:11 WANG Xuerui
2023-05-02 19:19 Arthur Zamarin
2023-05-02 18:52 Arthur Zamarin
2023-05-02 18:14 Arthur Zamarin
2023-04-18 16:02 Matt Turner
2023-03-21 19:08 Matt Turner
2023-03-12 2:01 Matt Turner
2022-10-30 16:34 Matt Turner
2022-10-08 16:52 Arthur Zamarin
2022-10-01 17:16 Matt Turner
2022-09-30 16:52 Matt Turner
2022-09-27 23:55 Matt Turner
2022-08-02 17:52 Pacho Ramos
2022-07-29 2:59 Sam James
2022-07-19 3:20 Matt Turner
2022-07-18 23:41 Sam James
2022-06-01 13:56 Matt Turner
2022-01-22 18:50 Mike Gilbert
2022-01-13 14:22 Mart Raudsepp
2021-12-19 18:15 Mart Raudsepp
2021-12-19 4:53 Matt Turner
2021-11-14 16:38 Mike Gilbert
2021-04-20 14:48 Matt Turner
2021-04-12 23:11 Sam James
2020-12-02 19:59 Mart Raudsepp
2020-12-02 19:59 Mart Raudsepp
2020-07-12 21:32 Mart Raudsepp
2020-03-15 17:38 Mart Raudsepp
2020-02-16 17:28 Mart Raudsepp
2019-12-23 21:26 Mart Raudsepp
2019-09-08 16:51 Mart Raudsepp
2019-03-14 10:26 Mart Raudsepp
2019-03-14 9:35 Mart Raudsepp
2019-03-04 10:56 Mart Raudsepp
2019-03-02 14:28 Mart Raudsepp
2018-09-28 13:51 Mart Raudsepp
2018-04-26 22:32 Aaron Bauman
2018-04-21 8:59 Mart Raudsepp
2017-09-23 21:13 Thomas Deutschmann
2017-08-18 7:50 Gilles Dartiguelongue
2017-07-25 13:36 Alexis Ballier
2017-07-25 12:27 Alexis Ballier
2017-07-15 11:04 Tobias Klausmann
2017-05-28 15:35 Mike Gilbert
2017-05-28 15:25 Mart Raudsepp
2017-05-28 15:25 Mart Raudsepp
2017-03-21 0:23 Mart Raudsepp
2017-03-09 8:15 Mart Raudsepp
2017-02-15 19:43 Mart Raudsepp
2016-10-29 23:15 Mike Gilbert
2016-10-12 7:28 Gilles Dartiguelongue
2016-03-06 17:23 Mikle Kolyada
2015-11-14 13:48 Pacho Ramos
2015-11-14 13:48 Pacho Ramos
2015-08-23 16:01 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=1516242868.d2d1d029e0e0733af3f2856c3fd9bc76672dc4d3.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