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: dev-libs/folks/
Date: Sat, 23 Feb 2019 13:58:25 +0000 (UTC)	[thread overview]
Message-ID: <1550927977.44989ec34fb0a38c960df12961d97b189b88ed8c.leio@gentoo> (raw)

commit:     44989ec34fb0a38c960df12961d97b189b88ed8c
Author:     Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Sat Feb 23 13:19:37 2019 +0000
Commit:     Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Sat Feb 23 13:19:37 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=44989ec3

dev-libs/folks: restrict >=vala-0.42 for now

Seems that folks isn't buildable with 0.42 without patches.
Restrict to 0.40 and older for the time being, until patch
is tested to work with both old and new vala and included.

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

 dev-libs/folks/folks-0.11.4-r1.ebuild | 3 ++-
 dev-libs/folks/folks-0.11.4.ebuild    | 1 +
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/dev-libs/folks/folks-0.11.4-r1.ebuild b/dev-libs/folks/folks-0.11.4-r1.ebuild
index 821d24168b2..9e8680df222 100644
--- a/dev-libs/folks/folks-0.11.4-r1.ebuild
+++ b/dev-libs/folks/folks-0.11.4-r1.ebuild
@@ -1,9 +1,10 @@
-# Copyright 1999-2018 Gentoo Authors
+# Copyright 1999-2019 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
 GNOME2_LA_PUNT="yes"
 VALA_USE_DEPEND="vapigen"
+VALA_MAX_API_VERSION="0.40"
 
 inherit gnome2 vala virtualx
 

diff --git a/dev-libs/folks/folks-0.11.4.ebuild b/dev-libs/folks/folks-0.11.4.ebuild
index 0eb6f1710ee..ce787854756 100644
--- a/dev-libs/folks/folks-0.11.4.ebuild
+++ b/dev-libs/folks/folks-0.11.4.ebuild
@@ -4,6 +4,7 @@
 EAPI=6
 GNOME2_LA_PUNT="yes"
 VALA_USE_DEPEND="vapigen"
+VALA_MAX_API_VERSION="0.40"
 
 inherit gnome2 vala virtualx
 


             reply	other threads:[~2019-02-23 13:58 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-23 13:58 Mart Raudsepp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-13 17:27 [gentoo-commits] repo/gentoo:master commit in: dev-libs/folks/ Pacho Ramos
2024-04-22 17:38 Arthur Zamarin
2024-04-17 22:01 Sam James
2024-04-17 22:01 Sam James
2024-03-24 20:46 Mart Raudsepp
2023-07-27  8:29 WANG Xuerui
2023-05-04 16:32 Arthur Zamarin
2023-05-02 18:34 Arthur Zamarin
2023-05-02 17:34 Arthur Zamarin
2023-03-08 15:10 Matt Turner
2022-11-01  3:54 Matt Turner
2022-10-29 23:21 Matt Turner
2022-03-26 18:01 Matt Turner
2022-01-22  9:51 Pacho Ramos
2021-10-09 11:23 Mart Raudsepp
2021-07-23  4:27 Matt Turner
2021-04-21  4:15 Matt Turner
2021-04-17  1:20 Matt Turner
2020-04-05 10:30 Mart Raudsepp
2020-02-29 21:22 Mart Raudsepp
2020-02-22 14:25 Mart Raudsepp
2019-08-04 15:05 Aaron Bauman
2019-07-28  6:42 Mart Raudsepp
2019-04-10 12:20 Mart Raudsepp
2019-04-09 21:09 Mikle Kolyada
2019-04-08  2:18 Thomas Deutschmann
2019-02-15 13:42 Mart Raudsepp
2018-12-11 13:21 Gilles Dartiguelongue
2018-05-15 13:05 Mikle Kolyada
2017-12-20 20:23 Mart Raudsepp
2017-07-09 23:23 Mart Raudsepp
2017-07-09 22:14 Mart Raudsepp
2015-08-31  0:19 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=1550927977.44989ec34fb0a38c960df12961d97b189b88ed8c.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