From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-sound/beets/
Date: Wed, 5 Sep 2018 21:08:03 +0000 (UTC) [thread overview]
Message-ID: <1536181602.9d8706f11b83454bf7c9ed4c27c8707c77446513.asturm@gentoo> (raw)
commit: 9d8706f11b83454bf7c9ed4c27c8707c77446513
Author: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
AuthorDate: Wed Sep 5 21:04:23 2018 +0000
Commit: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Wed Sep 5 21:06:42 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9d8706f1
media-sound/beets: +replaygain,+gstreamer needs gst-plugins-meta[ffmpeg]
Reported-by: <apaterson <AT> protonmail.com>
Closes: https://bugs.gentoo.org/663398
Package-Manager: Portage-2.3.49, Repoman-2.3.10
media-sound/beets/beets-1.4.7.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/media-sound/beets/beets-1.4.7.ebuild b/media-sound/beets/beets-1.4.7.ebuild
index b0ea1935a00..580bf88dca8 100644
--- a/media-sound/beets/beets-1.4.7.ebuild
+++ b/media-sound/beets/beets-1.4.7.ebuild
@@ -51,7 +51,7 @@ RDEPEND="
gstreamer? (
dev-python/pygobject:3[${PYTHON_USEDEP}]
media-libs/gst-plugins-good:1.0
- media-plugins/gst-plugins-meta:1.0
+ media-plugins/gst-plugins-meta:1.0[ffmpeg]
)
!gstreamer? ( media-sound/mp3gain )
)
next reply other threads:[~2018-09-05 21:08 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 21:08 Andreas Sturmlechner [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-11 9:04 [gentoo-commits] repo/gentoo:master commit in: media-sound/beets/ Ionen Wolkens
2024-12-19 7:54 Arsen Arsenović
2024-12-19 7:54 Arsen Arsenović
2024-06-13 9:26 Matt Jolly
2024-06-03 5:06 Matt Jolly
2024-06-03 5:06 Matt Jolly
2024-05-28 22:01 Sam James
2024-05-23 7:51 Matt Jolly
2024-05-22 13:19 Matt Jolly
2024-05-08 21:33 Sam James
2023-07-14 12:09 Sam James
2023-05-20 6:22 Michał Górny
2023-05-01 0:34 Sam James
2023-05-01 0:19 Sam James
2023-02-22 16:02 Sam James
2023-02-22 16:02 Sam James
2023-02-22 16:00 Sam James
2023-02-22 16:00 Sam James
2022-06-22 13:22 Agostino Sarubbo
2022-06-21 6:40 Sam James
2022-06-21 5:35 Sam James
2022-06-07 21:09 Sam James
2022-02-13 22:59 Jakov Smolić
2021-10-31 18:29 Sam James
2021-10-31 8:46 Sam James
2021-10-31 2:58 Sam James
2021-06-01 0:28 Sam James
2021-05-14 11:21 Sam James
2021-01-26 11:37 Joonas Niilola
2021-01-26 11:37 Joonas Niilola
2021-01-26 11:37 Joonas Niilola
2021-01-24 8:09 Joonas Niilola
2021-01-24 8:09 Joonas Niilola
2021-01-18 12:27 Joonas Niilola
2021-01-18 12:27 Joonas Niilola
2021-01-18 12:27 Joonas Niilola
2020-06-01 13:10 Joonas Niilola
2020-06-01 13:07 Joonas Niilola
2020-06-01 13:07 Joonas Niilola
2020-06-01 12:28 Joonas Niilola
2020-06-01 12:28 Joonas Niilola
2020-06-01 12:28 Joonas Niilola
2020-06-01 12:28 Joonas Niilola
2020-03-16 18:55 Michał Górny
2019-08-30 11:46 Joonas Niilola
2019-08-30 11:46 Joonas Niilola
2019-06-01 14:26 Andreas Sturmlechner
2019-05-19 17:54 Andreas Sturmlechner
2018-09-05 21:08 Andreas Sturmlechner
2018-09-05 21:08 Andreas Sturmlechner
2018-09-05 21:08 Andreas Sturmlechner
2018-03-18 12:42 Pacho Ramos
2018-03-18 12:42 Pacho Ramos
2017-02-20 0:36 Robin H. Johnson
2016-08-10 20:18 Michael Palimaka
2016-08-10 20:18 Michael Palimaka
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=1536181602.9d8706f11b83454bf7c9ed4c27c8707c77446513.asturm@gentoo \
--to=asturm@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