public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-plugins/gst-plugins-libpng/
Date: Fri, 24 Feb 2017 13:51:09 +0000 (UTC)	[thread overview]
Message-ID: <1487944161.99e0d55259843a070c6d6b856b3fe4c74afc3a6f.ago@gentoo> (raw)

commit:     99e0d55259843a070c6d6b856b3fe4c74afc3a6f
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Fri Feb 24 13:49:21 2017 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Fri Feb 24 13:49:21 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=99e0d552

media-plugins/gst-plugins-libpng: ppc64 stable wrt bug #601354

Package-Manager: portage-2.3.3
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

 media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.10.3.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.10.3.ebuild b/media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.10.3.ebuild
index 021657fd13..13d02d39e0 100644
--- a/media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.10.3.ebuild
+++ b/media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.10.3.ebuild
@@ -8,7 +8,7 @@ GST_ORG_MODULE=gst-plugins-good
 inherit gstreamer
 
 DESCRIPTION="PNG image encoder/decoder plugin for GStreamer"
-KEYWORDS="~alpha amd64 ~arm ~ppc ~ppc64 ~sparc x86"
+KEYWORDS="~alpha amd64 ~arm ~ppc ppc64 ~sparc x86"
 IUSE=""
 
 RDEPEND=">=media-libs/libpng-1.6.10:0=[${MULTILIB_USEDEP}]"


             reply	other threads:[~2017-02-24 13:51 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-24 13:51 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-15  5:01 [gentoo-commits] repo/gentoo:master commit in: media-plugins/gst-plugins-libpng/ Arthur Zamarin
2023-11-29  8:22 Arthur Zamarin
2023-10-14  3:43 Sam James
2023-08-21  6:31 Arthur Zamarin
2023-07-29 20:35 Arthur Zamarin
2023-07-29 20:35 Arthur Zamarin
2023-07-29 20:35 Arthur Zamarin
2022-12-13 18:26 Arthur Zamarin
2022-09-17 10:46 Arthur Zamarin
2022-09-16  8:53 Arthur Zamarin
2022-04-01 11:38 Arthur Zamarin
2021-09-27 14:14 Yixun Lan
2021-09-16 18:55 Sam James
2021-09-16  6:14 Sam James
2021-06-29 16:35 Sam James
2021-02-20  9:36 Mart Raudsepp
2021-02-17 13:53 Sam James
2021-02-15  4:03 Sam James
2021-02-14  2:09 Sam James
2021-02-13 17:43 Mart Raudsepp
2020-09-07  5:42 Sam James
2020-09-07  5:11 Sam James
2020-06-21 21:59 Mart Raudsepp
2020-05-03 19:12 Mart Raudsepp
2020-01-01 15:08 Mart Raudsepp
2019-12-28 15:42 Mikle Kolyada
2019-12-10 18:10 Aaron Bauman
2019-12-10 14:08 Agostino Sarubbo
2019-12-10 12:16 Agostino Sarubbo
2019-08-26  9:36 Mart Raudsepp
2019-07-29 20:02 Aaron Bauman
2019-03-02 23:28 Andreas Sturmlechner
2019-02-05 23:33 Mart Raudsepp
2019-01-25  2:38 Matt Turner
2019-01-15 23:29 Mart Raudsepp
2019-01-09  6:40 Matt Turner
2018-10-03 23:56 Mart Raudsepp
2018-09-30 20:59 Mart Raudsepp
2018-09-17 22:54 Matt Turner
2018-09-17 21:49 Mart Raudsepp
2018-07-30 22:59 Mart Raudsepp
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:44 Mikle Kolyada
2018-01-28 19:13 Mart Raudsepp
2018-01-05 13:29 Mart Raudsepp
2017-12-16 15:33 Mart Raudsepp
2017-11-08 20:50 Tobias Klausmann
2017-09-18 20:34 Mart Raudsepp
2017-02-25  1:28 Mart Raudsepp
2017-01-22 17:45 Agostino Sarubbo
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 13:51 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=1487944161.99e0d55259843a070c6d6b856b3fe4c74afc3a6f.ago@gentoo \
    --to=ago@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