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: gnome-extra/libgda/
Date: Sun, 30 Dec 2018 11:28:57 +0000 (UTC)	[thread overview]
Message-ID: <1546167056.f45a16054d54e562153adf0e74e4c810840f3230.leio@gentoo> (raw)

commit:     f45a16054d54e562153adf0e74e4c810840f3230
Author:     Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Sun Dec 30 10:49:58 2018 +0000
Commit:     Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Sun Dec 30 10:50:56 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f45a1605

gnome-extra/libgda: workaround build failures without vala

Upstream configure has a bad check for the libgee not existing failure,
by checking a variable that's not used anymore, so the check will
always fail with no libgee found - no matter if vala extensions
are actually requested or not. Due to older version not building
against new openssl, workaround it quickly and temporarily by
always requiring libgee during build, pending a proper fix that
fixes the check in configure.

Bug: https://bugs.gentoo.org/674066
Package-Manager: Portage-2.3.52, Repoman-2.3.12
Signed-off-by: Mart Raudsepp <leio <AT> gentoo.org>

 gnome-extra/libgda/libgda-5.2.8.ebuild | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/gnome-extra/libgda/libgda-5.2.8.ebuild b/gnome-extra/libgda/libgda-5.2.8.ebuild
index 1b78dd77194..0eb06d4b35c 100644
--- a/gnome-extra/libgda/libgda-5.2.8.ebuild
+++ b/gnome-extra/libgda/libgda-5.2.8.ebuild
@@ -59,7 +59,9 @@ RDEPEND="
 "
 
 # java dep shouldn't rely on slots, bug #450004
+# TODO: libgee shouldn't be needed at build with USE=-vala, but needs build system fixes - bug 674066
 DEPEND="${RDEPEND}
+	dev-libs/libgee:0.8
 	>=app-text/gnome-doc-utils-0.9
 	app-text/yelp-tools
 	dev-util/glib-utils


             reply	other threads:[~2018-12-30 11:29 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-30 11:28 Mart Raudsepp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-01 19:26 [gentoo-commits] repo/gentoo:master commit in: gnome-extra/libgda/ Andreas K. Hüttel
2024-10-29 22:13 Sam James
2024-10-29 15:39 Sam James
2023-05-29 21:25 Sam James
2023-05-18 12:17 Andreas Sturmlechner
2022-12-12 21:06 James Le Cuirot
2022-12-12 17:52 Arthur Zamarin
2022-12-12  1:59 Sam James
2022-11-19  1:44 Matt Turner
2022-11-19  1:44 Matt Turner
2022-10-30 22:29 Matt Turner
2022-04-16 12:25 Yixun Lan
2021-04-21 18:51 Sam James
2020-10-03 16:06 Pacho Ramos
2020-09-19 20:38 Pacho Ramos
2020-09-19 20:04 Pacho Ramos
2019-02-11 18:25 Brian Evans
2018-12-31 21:49 Mart Raudsepp
2018-12-28 16:24 Mart Raudsepp
2018-12-28 11:06 Mart Raudsepp
2018-11-13 22:08 Mart Raudsepp
2018-11-13 20:29 Craig Andrews
2017-11-26 23:02 David Seifert
2017-02-15 20:38 Mart Raudsepp
2016-10-08  9:51 Pacho Ramos
2016-03-06 18:58 Mikle Kolyada
2016-02-08  9:54 Patrick Lauer
2016-02-01 21:05 Pacho Ramos
2016-01-03 16:03 Gilles Dartiguelongue
2015-12-26  5:39 Dennis Lamm
2015-09-07 21:11 Mikle Kolyada
2015-08-31  0:22 Alexandre Rostovtsev

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=1546167056.f45a16054d54e562153adf0e74e4c810840f3230.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