public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-plugins/gst-plugins-mad/
Date: Sat, 16 Dec 2017 15:33:24 +0000 (UTC)	[thread overview]
Message-ID: <1513438384.d5c946479a25b15c2947ffaa659a5f7556eb74f6.leio@gentoo> (raw)

commit:     d5c946479a25b15c2947ffaa659a5f7556eb74f6
Author:     Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Sat Dec 16 15:25:49 2017 +0000
Commit:     Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Sat Dec 16 15:33:04 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d5c94647

media-plugins/gst-plugins-mad-1.10.5: hppa stable

1.10.3 was stable on hppa, while 1.10.5 series was skipped and
1.12.3 was the next stable, which doesn't have mad plugin anymore.
as there are no code changes in gst-plugins-mad between 1.10.3 and
1.10.5, stabilize blindly as maintainer for hppa to solve deptree
ater 1.10.3 set removal without having to still pull in
gst-plugins-ugly-1.10.3.tar.xz tarballs somewhere.

Package-Manager: Portage-2.3.16, Repoman-2.3.6

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

diff --git a/media-plugins/gst-plugins-mad/gst-plugins-mad-1.10.5.ebuild b/media-plugins/gst-plugins-mad/gst-plugins-mad-1.10.5.ebuild
index d88a2f09f33..1bd9bc89041 100644
--- a/media-plugins/gst-plugins-mad/gst-plugins-mad-1.10.5.ebuild
+++ b/media-plugins/gst-plugins-mad/gst-plugins-mad-1.10.5.ebuild
@@ -7,7 +7,7 @@ GST_ORG_MODULE=gst-plugins-ugly
 inherit gstreamer
 
 DESCRIPTION="MP3 decoder plugin for GStreamer"
-KEYWORDS="alpha amd64 arm ~arm64 ~hppa ia64 ~mips ppc ppc64 ~sh ~sparc x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux"
+KEYWORDS="alpha amd64 arm ~arm64 hppa ia64 ~mips ppc ppc64 ~sh ~sparc x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux"
 IUSE=""
 
 RDEPEND=">=media-libs/libmad-0.15.1b-r8[${MULTILIB_USEDEP}]"


             reply	other threads:[~2017-12-16 15:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-16 15:33 Mart Raudsepp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-12-16 14:13 [gentoo-commits] repo/gentoo:master commit in: media-plugins/gst-plugins-mad/ Mart Raudsepp
2017-07-20  4:40 Markus Meier
2017-07-08 16:08 Sergei Trofimovich
2017-06-28  9:35 Alexis Ballier
2017-06-10 20:14 Sergei Trofimovich
2017-04-05 14:07 Tobias Klausmann
2017-02-24 13:51 Agostino Sarubbo
2017-02-19 12:00 Jeroen Roovers
2017-02-15 17:46 Markus Meier
2017-01-22 18:03 Agostino Sarubbo
2017-01-22 17:45 Agostino Sarubbo
2016-12-06 21:36 Markus Meier
2016-10-03  6:12 Jeroen Roovers
2016-09-26 10:10 Tobias Klausmann
2016-09-23 15:41 Tobias Klausmann
2016-09-18 22:44 Gilles Dartiguelongue
2016-07-09 15:09 Pacho Ramos
2016-06-11 11:30 Pacho Ramos
2016-05-03 20:47 Markus Meier
2016-03-06 19:39 Mikle Kolyada
2016-01-31 15:54 Gilles Dartiguelongue
2015-12-26 18:21 Gilles Dartiguelongue
2015-12-26 17:15 Gilles Dartiguelongue
2015-11-08 19:27 Gilles Dartiguelongue
2015-10-25 23:01 Gilles Dartiguelongue
2015-10-03  8:50 Markus Meier

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=1513438384.d5c946479a25b15c2947ffaa659a5f7556eb74f6.leio@gentoo \
    --to=leio@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