From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-video/cheese/
Date: Mon, 7 Sep 2015 19:58:13 +0000 (UTC) [thread overview]
Message-ID: <1441655706.39edd95a38c939545cb06ccddf66e626d3b736f1.zlogene@gentoo> (raw)
commit: 39edd95a38c939545cb06ccddf66e626d3b736f1
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Mon Sep 7 19:11:37 2015 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Mon Sep 7 19:55:06 2015 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=39edd95a
media-video/cheese: amd64 stable wrt bug #551826
Package-Manager: portage-2.2.20.1
RepoMan-Options: --ignore-arches
media-video/cheese/cheese-3.16.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/media-video/cheese/cheese-3.16.1.ebuild b/media-video/cheese/cheese-3.16.1.ebuild
index 3eff6f9..db4ed21 100644
--- a/media-video/cheese/cheese-3.16.1.ebuild
+++ b/media-video/cheese/cheese-3.16.1.ebuild
@@ -14,7 +14,7 @@ HOMEPAGE="https://wiki.gnome.org/Apps/Cheese"
LICENSE="GPL-2+"
SLOT="0/7" # subslot = libcheese soname version
IUSE="+introspection test"
-KEYWORDS="~amd64 ~arm ~ia64 ~ppc ~ppc64 ~x86"
+KEYWORDS="amd64 ~arm ~ia64 ~ppc ~ppc64 ~x86"
# using clutter-gst-2.0.0 results in GLSL errors; bug #478702
COMMON_DEPEND="
next reply other threads:[~2015-09-07 19:58 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 19:58 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-17 20:23 [gentoo-commits] repo/gentoo:master commit in: media-video/cheese/ Pacho Ramos
2015-11-17 20:23 Pacho Ramos
2015-11-17 20:23 Pacho Ramos
2015-11-24 20:02 Gilles Dartiguelongue
2016-03-06 18:03 Mikle Kolyada
2016-07-02 17:12 Pacho Ramos
2016-07-02 17:12 Pacho Ramos
2016-09-04 16:22 Gilles Dartiguelongue
2016-10-23 23:01 Gilles Dartiguelongue
2016-10-23 23:01 Gilles Dartiguelongue
2017-08-13 9:51 Gilles Dartiguelongue
2018-01-18 2:58 Mikle Kolyada
2018-01-19 7:34 Gilles Dartiguelongue
2018-01-27 0:41 Thomas Deutschmann
2018-02-03 23:00 Mart Raudsepp
2018-08-03 11:45 Mart Raudsepp
2018-12-02 10:12 Mikle Kolyada
2018-12-02 14:29 Mikle Kolyada
2018-12-02 17:27 Mart Raudsepp
2018-12-21 22:17 Gilles Dartiguelongue
2019-01-18 22:15 Mart Raudsepp
2019-01-18 22:15 Mart Raudsepp
2019-05-18 23:05 Mart Raudsepp
2019-08-03 19:04 Aaron Bauman
2019-10-13 0:18 Matt Turner
2019-10-13 12:14 Mart Raudsepp
2019-12-08 11:41 Mikle Kolyada
2019-12-08 11:52 Mikle Kolyada
2019-12-23 22:23 Mart Raudsepp
2020-03-01 16:18 Mart Raudsepp
2020-04-25 20:17 Mart Raudsepp
2020-05-03 20:22 Mart Raudsepp
2021-03-04 0:23 Sam James
2021-03-13 18:32 Matt Turner
2021-04-14 18:51 Mikle Kolyada
2021-04-15 1:33 Sam James
2021-04-15 5:25 Sam James
2021-04-24 9:20 Mart Raudsepp
2021-09-25 10:40 Mart Raudsepp
2021-10-04 1:24 Sam James
2021-10-04 1:25 Sam James
2021-11-06 4:09 Sam James
2021-12-19 2:00 Matt Turner
2021-12-26 22:32 Mart Raudsepp
2021-12-31 3:42 Yixun Lan
2023-02-17 8:23 Arthur Zamarin
2023-04-10 14:16 Matt Turner
2023-04-17 23:45 Matt Turner
2023-05-02 18:00 Arthur Zamarin
2023-05-05 9:13 Arthur Zamarin
2023-05-05 9:19 Arthur Zamarin
2023-05-17 21:55 Matt Turner
2023-07-18 22:39 Matt Turner
2023-08-30 7:57 Arthur Zamarin
2024-11-04 18:39 Andreas Sturmlechner
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=1441655706.39edd95a38c939545cb06ccddf66e626d3b736f1.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