From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-plugins/gst-plugins-mplex/
Date: Sun, 6 Mar 2016 19:39:26 +0000 (UTC) [thread overview]
Message-ID: <1457292973.576b6fc5459aace1efcaf89c2319c5283c388f7b.zlogene@gentoo> (raw)
commit: 576b6fc5459aace1efcaf89c2319c5283c388f7b
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 6 19:33:36 2016 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sun Mar 6 19:36:13 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=576b6fc5
media-plugins/gst-plugins-mplex: x86 stable wrt bug #566378
Package-Manager: portage-2.2.26
media-plugins/gst-plugins-mplex/gst-plugins-mplex-1.6.3.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/media-plugins/gst-plugins-mplex/gst-plugins-mplex-1.6.3.ebuild b/media-plugins/gst-plugins-mplex/gst-plugins-mplex-1.6.3.ebuild
index cd0f2dd..bdba1ba 100644
--- a/media-plugins/gst-plugins-mplex/gst-plugins-mplex-1.6.3.ebuild
+++ b/media-plugins/gst-plugins-mplex/gst-plugins-mplex-1.6.3.ebuild
@@ -8,7 +8,7 @@ GST_ORG_MODULE=gst-plugins-bad
inherit gstreamer
DESCRIPTION="GStreamer plugin for MPEG/DVD/SVCD/VCD video/audio multiplexing"
-KEYWORDS="~alpha amd64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86 ~amd64-fbsd"
+KEYWORDS="~alpha amd64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc x86 ~amd64-fbsd"
IUSE=""
RDEPEND=">=media-video/mjpegtools-2.1.0-r1[${MULTILIB_USEDEP}]"
next reply other threads:[~2016-03-06 19:39 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 19:39 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-19 14:23 [gentoo-commits] repo/gentoo:master commit in: media-plugins/gst-plugins-mplex/ Arthur Zamarin
2022-12-15 4:46 Arthur Zamarin
2022-12-13 20:03 Arthur Zamarin
2022-11-24 12:11 WANG Xuerui
2022-11-02 5:50 WANG Xuerui
2022-10-10 2:34 Matt Turner
2022-09-16 6:52 Agostino Sarubbo
2022-09-14 7:47 Agostino Sarubbo
2022-05-16 12:35 Jakov Smolić
2022-04-01 15:20 Jakov Smolić
2022-04-01 7:14 Arthur Zamarin
2021-09-16 6:27 Sam James
2021-08-13 23:29 Sam James
2021-08-10 14:18 Marek Szuba
2021-05-30 0:40 Sam James
2021-02-19 23:16 Mart Raudsepp
2021-02-13 19:49 Mart Raudsepp
2019-12-28 15:42 Mikle Kolyada
2019-08-27 21:05 Mart Raudsepp
2019-01-25 2:38 Matt Turner
2018-07-21 16:57 Tobias Klausmann
2018-07-16 13:49 Mikle Kolyada
2018-07-15 22:52 Mart Raudsepp
2018-05-20 19:10 Andreas Sturmlechner
2018-04-01 15:51 Tobias Klausmann
2018-03-28 22:41 Matt Turner
2018-03-17 17:50 Mikle Kolyada
2018-02-14 22:06 Mart Raudsepp
2018-01-03 0:05 Mart Raudsepp
2017-12-12 16:55 Mart Raudsepp
2017-11-08 20:50 Tobias Klausmann
2017-11-07 8:06 Sergei Trofimovich
2017-09-16 19:46 Mart Raudsepp
2017-06-30 4:58 Alexis Ballier
2017-06-18 8:31 Mart Raudsepp
2017-04-05 14:07 Tobias Klausmann
2017-02-25 20:46 Mart Raudsepp
2017-02-19 12:00 Jeroen Roovers
2017-02-11 14:52 Mart Raudsepp
2017-01-26 4:36 Mart Raudsepp
2016-10-03 6:12 Jeroen Roovers
2016-09-26 10:10 Tobias Klausmann
2016-09-23 15:41 Tobias Klausmann
2016-06-11 11:30 Pacho Ramos
2016-01-31 14:45 Gilles Dartiguelongue
2015-12-26 17:15 Gilles Dartiguelongue
2015-10-25 17:32 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=1457292973.576b6fc5459aace1efcaf89c2319c5283c388f7b.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