From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-plugins/gst-plugins-neon/
Date: Thu, 26 Oct 2017 07:30:00 +0000 (UTC) [thread overview]
Message-ID: <1509002983.b2e27be23cece9ea8634e7740671c538da55ab58.slyfox@gentoo> (raw)
commit: b2e27be23cece9ea8634e7740671c538da55ab58
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Thu Oct 26 06:47:30 2017 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Thu Oct 26 07:29:43 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b2e27be2
media-plugins/gst-plugins-neon: stable 1.10.5 for ppc/ppc64, bug #624180
Package-Manager: Portage-2.3.12, Repoman-2.3.4
RepoMan-Options: --include-arches="ppc ppc64"
media-plugins/gst-plugins-neon/gst-plugins-neon-1.10.5.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/media-plugins/gst-plugins-neon/gst-plugins-neon-1.10.5.ebuild b/media-plugins/gst-plugins-neon/gst-plugins-neon-1.10.5.ebuild
index fe2708d6d43..a973bf092ad 100644
--- a/media-plugins/gst-plugins-neon/gst-plugins-neon-1.10.5.ebuild
+++ b/media-plugins/gst-plugins-neon/gst-plugins-neon-1.10.5.ebuild
@@ -7,7 +7,7 @@ GST_ORG_MODULE=gst-plugins-bad
inherit gstreamer
DESCRIPTION="HTTP client source plugin for GStreamer"
-KEYWORDS="alpha amd64 ~ppc ~ppc64 x86"
+KEYWORDS="alpha amd64 ppc ppc64 x86"
IUSE=""
RDEPEND=">=net-libs/neon-0.30.0[${MULTILIB_USEDEP}]"
next reply other threads:[~2017-10-26 7:30 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 7:30 Sergei Trofimovich [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-neon/ Arthur Zamarin
2023-11-29 8:22 Arthur Zamarin
2023-10-15 11:40 Mart Raudsepp
2023-10-14 3:43 Sam James
2023-07-25 18:10 Arthur Zamarin
2023-07-23 19:32 Arthur Zamarin
2023-06-10 10:15 Arthur Zamarin
2023-06-10 9:45 Arthur Zamarin
2022-12-15 4:46 Arthur Zamarin
2022-12-13 20:09 Arthur Zamarin
2022-12-13 20:03 Arthur Zamarin
2022-10-20 17:01 Georgy Yakovlev
2022-09-17 10:46 Arthur Zamarin
2022-09-16 6:52 Agostino Sarubbo
2022-09-14 7:47 Agostino Sarubbo
2022-05-28 1:29 Sam James
2022-05-16 12:35 Jakov Smolić
2022-04-01 15:20 Jakov Smolić
2022-04-01 11:38 Arthur Zamarin
2022-04-01 7:14 Arthur Zamarin
2021-09-16 6:27 Sam James
2021-09-16 6:14 Sam James
2021-05-30 0:40 Sam James
2021-02-19 23:16 Mart Raudsepp
2021-02-15 4:03 Sam James
2021-02-14 2:09 Sam James
2021-02-13 21:54 Mart Raudsepp
2021-02-13 19:49 Mart Raudsepp
2020-09-07 5:42 Sam James
2020-09-07 5:11 Sam James
2019-12-28 15:42 Mikle Kolyada
2019-12-10 14:08 Agostino Sarubbo
2019-12-10 12:16 Agostino Sarubbo
2019-08-27 21:05 Mart Raudsepp
2019-01-25 2:38 Matt Turner
2019-01-09 6:40 Matt Turner
2018-09-21 5:23 Mart Raudsepp
2018-09-17 23:51 Mart Raudsepp
2018-09-17 22:54 Matt Turner
2018-07-21 16:57 Tobias Klausmann
2018-07-16 13:49 Mikle Kolyada
2018-06-21 10:40 Mart Raudsepp
2018-05-25 4:24 Matt Turner
2018-04-01 15:51 Tobias Klausmann
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-11 21:49 Thomas Deutschmann
2017-11-08 20:50 Tobias Klausmann
2017-11-01 19:56 Sergei Trofimovich
2017-11-01 9:35 Sergei Trofimovich
2017-09-16 19:46 Mart Raudsepp
2017-06-18 8:31 Mart Raudsepp
2017-04-05 14:07 Tobias Klausmann
2017-02-25 20:46 Mart Raudsepp
2017-02-24 13:51 Agostino Sarubbo
2017-02-11 14:52 Mart Raudsepp
2017-02-11 14:52 Mart Raudsepp
2016-09-26 10:10 Tobias Klausmann
2016-09-23 15:41 Tobias Klausmann
2016-07-09 15:09 Pacho Ramos
2016-06-11 11:30 Pacho Ramos
2016-04-07 10:17 Jeroen Roovers
2016-03-06 19:39 Mikle Kolyada
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=1509002983.b2e27be23cece9ea8634e7740671c538da55ab58.slyfox@gentoo \
--to=slyfox@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