From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "openembedded-commits@lists.openembedded.org"
<openembedded-commits@lists.openembedded.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [oe-commits] Ross Burton : vala: upgrade to 0.26.1
Date: Fri, 21 Nov 2014 15:31:31 +0100 [thread overview]
Message-ID: <20141121143131.GL2163@jama> (raw)
In-Reply-To: <CAJTo0LYjQqu-VWVrmTU=6BWm8b6g+9yOiv=xcMZLquJ3jEbLaA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
On Fri, Nov 21, 2014 at 02:04:17PM +0000, Burton, Ross wrote:
> On 21 November 2014 14:01, Martin Jansa <martin.jansa@gmail.com> wrote:
>
> > > vala: upgrade to 0.26.1
> > >
> > > vapigen can't be disabled anymore, so remove --disable-vapigen.
> > >
> > > Signed-off-by: Ross Burton <ross.burton@intel.com>
> >
> > Was this needed and tested with some real world applications?
> >
> > Or was it tested only because package index was showing possible
> > upgrade?
> >
> > Causes couple failures in world builds:
> >
>
> Yes and yes (the new rygel that I'm about to submit to meta-multimedia).
>
> I don't have those layers checked out - are they failing because they want
> a specific version of vala, or some other reason?
xfce4-vala fails to detect libvala version, other apps are failing in
valac so they need to be updated to be compatible with new vala
See logs in:
http://lists.openembedded.org/pipermail/openembedded-core/2014-November/099113.html
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2014-11-21 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141112153903.E7E7F50273@opal.openembedded.org>
2014-11-21 14:01 ` [oe-commits] Ross Burton : vala: upgrade to 0.26.1 Martin Jansa
2014-11-21 14:04 ` Burton, Ross
2014-11-21 14:31 ` Martin Jansa [this message]
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=20141121143131.GL2163@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-commits@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.