From: "Tony Vroon" <chainsaw@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-libs/pjproject/
Date: Fri, 31 Aug 2018 17:13:34 +0000 (UTC) [thread overview]
Message-ID: <1535735605.062697027374733e80e6bab2d5fa7789e61cd994.chainsaw@gentoo> (raw)
commit: 062697027374733e80e6bab2d5fa7789e61cd994
Author: Tony Vroon <chainsaw <AT> gentoo <DOT> org>
AuthorDate: Fri Aug 31 17:12:55 2018 +0000
Commit: Tony Vroon <chainsaw <AT> gentoo <DOT> org>
CommitDate: Fri Aug 31 17:13:25 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=06269702
net-libs/pjproject: Block media-plugins/mediastreamer-bcg729
This breaks the build process in a way that is not yet fully understood.
Annoying, but better to flag it up than to explode without warning.
Suggested-by: Jaco Kroon <jaco <AT> uls.co.za>
Acked-by: Mart Raudsepp <leio <AT> gentoo.org>
Fixes: https://bugs.gentoo.org/609702
Package-Manager: Portage-2.3.40, Repoman-2.3.9
net-libs/pjproject/pjproject-2.7.2.ebuild | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/net-libs/pjproject/pjproject-2.7.2.ebuild b/net-libs/pjproject/pjproject-2.7.2.ebuild
index ee569db2b4e..8f9962b2e27 100644
--- a/net-libs/pjproject/pjproject-2.7.2.ebuild
+++ b/net-libs/pjproject/pjproject-2.7.2.ebuild
@@ -44,7 +44,8 @@ RDEPEND="alsa? ( media-libs/alsa-lib )
net-libs/libsrtp:0"
DEPEND="${RDEPEND}
- virtual/pkgconfig"
+ virtual/pkgconfig
+ !!media-plugins/mediastreamer-bcg729"
REQUIRED_USE="?? ( ${SOUND_FLAGS} )"
next reply other threads:[~2018-08-31 17:13 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 17:13 Tony Vroon [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-17 16:00 [gentoo-commits] repo/gentoo:master commit in: net-libs/pjproject/ Sam James
2024-09-17 16:00 Sam James
2024-01-12 8:30 Arthur Zamarin
2023-11-22 7:20 Joonas Niilola
2023-11-22 7:20 Joonas Niilola
2023-05-18 5:07 John Helmert III
2023-05-18 5:00 John Helmert III
2023-05-18 5:00 John Helmert III
2023-05-16 6:16 Joonas Niilola
2023-05-10 9:40 Sam James
2023-04-20 21:52 Sam James
2023-04-20 21:52 Sam James
2022-12-13 5:27 Sam James
2022-12-13 5:27 Sam James
2022-10-30 2:58 John Helmert III
2022-10-27 8:00 Joonas Niilola
2022-10-25 17:55 Sam James
2022-08-19 3:46 Sam James
2022-08-04 6:37 Joonas Niilola
2022-06-15 13:32 Joonas Niilola
2021-07-24 7:58 Agostino Sarubbo
2021-07-24 7:57 Agostino Sarubbo
2021-05-02 10:56 Mikle Kolyada
2021-03-15 19:20 John Helmert III
2021-03-14 1:29 Sam James
2021-03-12 18:32 Sam James
2021-02-19 16:14 Sam James
2021-02-12 14:15 Sam James
2020-12-29 20:45 Sam James
2020-10-06 21:45 Sam James
2020-09-12 1:49 Sam James
2020-07-20 12:24 Sam James
2020-07-20 9:01 Joonas Niilola
2020-07-16 17:45 Sam James
2020-05-06 6:48 Sergei Trofimovich
2020-04-26 11:00 David Seifert
2020-04-14 12:32 Agostino Sarubbo
2020-03-31 8:25 Mikle Kolyada
2020-01-08 17:54 Joonas Niilola
2019-11-30 7:50 Joonas Niilola
2019-03-18 22:53 Patrice Clement
2018-10-06 18:40 Sergei Trofimovich
2018-10-06 18:40 Sergei Trofimovich
2018-03-12 10:51 Agostino Sarubbo
2018-02-07 9:17 Tony Vroon
2017-09-18 23:43 Tony Vroon
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=1535735605.062697027374733e80e6bab2d5fa7789e61cd994.chainsaw@gentoo \
--to=chainsaw@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