From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-misc/rygel/
Date: Mon, 7 Sep 2015 21:55:43 +0000 (UTC) [thread overview]
Message-ID: <1441662164.b736e14ac49647d5e8c8a2f22d9b4e0268132458.zlogene@gentoo> (raw)
commit: b736e14ac49647d5e8c8a2f22d9b4e0268132458
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Mon Sep 7 21:42:44 2015 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Mon Sep 7 21:42:44 2015 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b736e14a
net-misc/rygel: amd64 stable wrt bug #551826
Package-Manager: portage-2.2.20.1
RepoMan-Options: --ignore-arches
net-misc/rygel/rygel-0.26.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-misc/rygel/rygel-0.26.1.ebuild b/net-misc/rygel/rygel-0.26.1.ebuild
index 9ec428c..95a898d 100644
--- a/net-misc/rygel/rygel-0.26.1.ebuild
+++ b/net-misc/rygel/rygel-0.26.1.ebuild
@@ -13,7 +13,7 @@ HOMEPAGE="https://wiki.gnome.org/Projects/Rygel"
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 ~x86"
IUSE="X +introspection +sqlite tracker test transcode"
# The deps for tracker? and transcode? are just the earliest available
next reply other threads:[~2015-09-07 21:55 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 21:55 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-12 9:11 [gentoo-commits] repo/gentoo:master commit in: net-misc/rygel/ Agostino Sarubbo
2015-11-15 14:23 Pacho Ramos
2015-11-15 14:23 Pacho Ramos
2015-12-13 22:10 Gilles Dartiguelongue
2016-01-11 13:16 Pacho Ramos
2016-01-11 13:16 Pacho Ramos
2016-01-19 9:05 Patrick Lauer
2016-04-02 20:38 Pacho Ramos
2016-04-03 12:42 Pacho Ramos
2016-04-03 12:42 Pacho Ramos
2016-06-11 12:06 Pacho Ramos
2016-06-11 19:39 Pacho Ramos
2016-07-03 16:33 Pacho Ramos
2016-07-03 16:33 Pacho Ramos
2016-09-05 7:18 Gilles Dartiguelongue
2016-10-30 11:44 Gilles Dartiguelongue
2017-03-19 16:37 Mart Raudsepp
2017-03-20 15:54 Mart Raudsepp
2017-04-01 13:16 Agostino Sarubbo
2017-04-01 16:31 Agostino Sarubbo
2017-04-02 13:03 Mart Raudsepp
2017-08-13 17:03 Gilles Dartiguelongue
2018-01-18 2:53 Mikle Kolyada
2018-02-03 23:17 Mart Raudsepp
2019-01-22 16:41 Mart Raudsepp
2019-01-22 16:41 Mart Raudsepp
2019-04-08 2:18 Thomas Deutschmann
2019-04-09 21:09 Mikle Kolyada
2019-04-10 12:20 Mart Raudsepp
2020-02-20 8:51 Mart Raudsepp
2020-02-21 20:59 Mart Raudsepp
2020-02-21 20:59 Mart Raudsepp
2020-02-22 14:25 Mart Raudsepp
2020-04-20 17:03 Agostino Sarubbo
2020-04-20 18:16 Agostino Sarubbo
2020-04-25 20:17 Mart Raudsepp
2020-07-04 21:52 Mart Raudsepp
2020-08-30 15:17 Thomas Deutschmann
2020-08-30 18:09 Sam James
2020-11-07 15:23 Mart Raudsepp
2021-04-28 16:27 Matt Turner
2021-05-29 6:09 Sam James
2021-05-29 9:02 Sam James
2021-05-31 2:00 Matt Turner
2021-08-04 21:13 Pacho Ramos
2021-08-04 21:13 Pacho Ramos
2021-09-19 9:35 Pacho Ramos
2022-01-09 19:42 Matt Turner
2022-01-20 10:02 Jakov Smolić
2022-01-24 3:39 Sam James
2022-01-24 22:43 Matt Turner
2022-06-04 2:10 Matt Turner
2022-07-02 20:47 Sam James
2022-07-06 1:24 Sam James
2022-07-21 2:04 Matt Turner
2022-10-06 15:06 Matt Turner
2022-10-31 17:58 Matt Turner
2022-12-04 20:02 Matt Turner
2022-12-16 20:37 Arthur Zamarin
2023-01-01 14:48 David Seifert
2023-01-03 14:08 Matt Turner
2023-02-13 15:09 Matt Turner
2023-04-02 0:57 Matt Turner
2023-04-02 21:37 Matt Turner
2023-04-19 14:58 Pacho Ramos
2023-04-23 2:09 Matt Turner
2023-05-05 6:16 Arthur Zamarin
2023-05-05 6:16 Arthur Zamarin
2023-08-03 4:30 Matt Turner
2023-08-30 7:57 Arthur Zamarin
2023-09-05 20:28 Matt Turner
2023-11-04 23:03 Mart Raudsepp
2024-02-17 21:53 Mart Raudsepp
2024-04-17 22:01 Sam James
2024-04-22 17:42 Arthur Zamarin
2024-05-06 7:09 Mart Raudsepp
2024-06-01 12:01 Pacho Ramos
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=1441662164.b736e14ac49647d5e8c8a2f22d9b4e0268132458.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