From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libgdata/
Date: Wed, 15 Mar 2017 13:48:20 +0000 (UTC) [thread overview]
Message-ID: <1489583792.f4be32b6152bb9a4d654e8e9c6d7535637e3dc26.leio@gentoo> (raw)
commit: f4be32b6152bb9a4d654e8e9c6d7535637e3dc26
Author: Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 15 13:16:04 2017 +0000
Commit: Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Wed Mar 15 13:16:32 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f4be32b6
dev-libs/libgdata: tests: don't remove https testing if libsoup is new enough
The issue was identified to be with older libsoup, so only revert the TLS
patch if available libsoup is buggy for the test. Next libgdata release will
fix it properly (grabbing the upstream fix verbatim would mean unnecesary
eautoreconf)
Package-Manager: Portage-2.3.4, Repoman-2.3.1
dev-libs/libgdata/libgdata-0.17.7.ebuild | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/dev-libs/libgdata/libgdata-0.17.7.ebuild b/dev-libs/libgdata/libgdata-0.17.7.ebuild
index ce01bdd4863..bf51fdf868f 100644
--- a/dev-libs/libgdata/libgdata-0.17.7.ebuild
+++ b/dev-libs/libgdata/libgdata-0.17.7.ebuild
@@ -41,8 +41,10 @@ DEPEND="${RDEPEND}
"
src_prepare() {
- # https://bugzilla.gnome.org/show_bug.cgi?id=780081
- eapply -R "${FILESDIR}/${PV}"-streams-https-tests.patch
+ # https://bugzilla.gnome.org/show_bug.cgi?id=780081 - remove with 0.17.8
+ if use test && ! has_version '>=net-libs/libsoup-2.55.90:2.4'; then
+ eapply -R "${FILESDIR}/${PV}"-streams-https-tests.patch
+ fi
# x86 test fix from upstream git post-0.17.7
eapply "${FILESDIR}/${PV}"-fix-x86-tests.patch
next reply other threads:[~2017-03-15 13:48 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 13:48 Mart Raudsepp [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-30 1:50 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libgdata/ Matt Turner
2022-10-01 17:16 Matt Turner
2022-09-28 13:03 Matt Turner
2022-05-26 4:45 WANG Xuerui
2022-04-17 19:02 Matt Turner
2021-08-02 16:42 Marek Szuba
2021-05-29 15:27 Sam James
2021-05-28 19:20 Sam James
2021-05-28 19:18 Sam James
2021-05-28 19:11 Sam James
2021-04-13 15:03 Sam James
2021-04-12 21:59 Matt Turner
2020-11-08 15:15 Matt Turner
2020-07-29 11:23 Mart Raudsepp
2020-07-29 4:49 Sam James
2020-02-28 20:14 Mart Raudsepp
2020-02-09 15:56 Mart Raudsepp
2019-12-25 19:52 Mart Raudsepp
2019-12-09 0:10 Aaron Bauman
2019-12-08 11:59 Mikle Kolyada
2019-12-08 11:58 Mikle Kolyada
2019-08-25 12:31 Mart Raudsepp
2019-08-24 18:30 Mart Raudsepp
2019-07-05 3:26 Sobhan Mohammadpour
2019-05-23 6:39 Aaron Bauman
2019-01-18 21:00 Mart Raudsepp
2018-11-01 20:42 Mart Raudsepp
2018-01-16 20:33 Mart Raudsepp
2017-11-23 20:47 Sergei Trofimovich
2017-11-06 20:49 Tobias Klausmann
2017-09-03 5:03 Mart Raudsepp
2017-09-02 23:33 Gilles Dartiguelongue
2017-09-02 23:33 Gilles Dartiguelongue
2017-08-27 17:57 Gilles Dartiguelongue
2017-07-07 10:12 Agostino Sarubbo
2017-07-02 22:05 Gilles Dartiguelongue
2017-06-30 4:58 Alexis Ballier
2017-04-30 9:58 Jeroen Roovers
2017-04-23 21:23 Agostino Sarubbo
2017-04-22 19:08 Tobias Klausmann
2017-04-22 17:53 Tobias Klausmann
2017-04-20 12:09 Mart Raudsepp
2017-04-12 10:10 Jeroen Roovers
2017-03-16 23:40 Mart Raudsepp
2017-03-16 13:24 Jeroen Roovers
2017-03-15 11:44 Mart Raudsepp
2017-03-14 22:07 Mart Raudsepp
2017-02-21 9:16 Tobias Klausmann
2017-02-15 19:24 Mart Raudsepp
2016-10-08 9:51 Pacho Ramos
2016-09-17 14:03 Gilles Dartiguelongue
2016-07-02 10:43 Pacho Ramos
2016-07-02 10:43 Pacho Ramos
2016-03-19 13:14 Agostino Sarubbo
2016-03-17 10:10 Tobias Klausmann
2016-03-06 16:43 Mikle Kolyada
2015-12-30 14:57 Jeroen Roovers
2015-12-30 10:24 Pacho Ramos
2015-12-30 10:24 Pacho Ramos
2015-12-13 22:10 Gilles Dartiguelongue
2015-12-13 22:10 Gilles Dartiguelongue
2015-11-18 5:47 Jeroen Roovers
2015-09-20 18:45 Pacho Ramos
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=1489583792.f4be32b6152bb9a4d654e8e9c6d7535637e3dc26.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