From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [Patch v3] gconf: enable gtk+ 2.0 support to build gconf-sanity-check-2
Date: Mon, 16 Jan 2012 18:06:05 +0000 [thread overview]
Message-ID: <1326737165.2933.7.camel@ted> (raw)
In-Reply-To: <1326395831-5121-1-git-send-email-koen@dominion.thruhere.net>
On Thu, 2012-01-12 at 20:17 +0100, Koen Kooi wrote:
> This is needed for e.g. gnome-session:
>
> gnome-session[424]: WARNING: Failed to run gconf-sanity-check-2:
> Failed to execute child process
> "/usr/libexec/gconf-sanity-check-2" (No such file or directory)
>
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> ---
> meta/recipes-gnome/gnome/gconf_3.2.3.bb | 20 +++++++++++---------
> 1 files changed, 11 insertions(+), 9 deletions(-)
This broke OE-Core since gtk+ depends on pango, pango depends on gconf
and gconf depends on gtk+.
Why wasn't this tested? I can only assume there are things in meta-oe
masking pieces of OE-Core and this shows how harmful they can be.
Since this was breaking things for pretty much everyone who does use
OE-Core, I pushed a patch changing pango to inherit gnomebase instead of
gnome.bbclass which resolves the circular dependency.
Cheers,
Richard
next prev parent reply other threads:[~2012-01-16 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 19:17 [Patch v3] gconf: enable gtk+ 2.0 support to build gconf-sanity-check-2 Koen Kooi
2012-01-16 14:07 ` Steve Sakoman
2012-01-16 14:12 ` Richard Purdie
2012-01-16 18:06 ` Richard Purdie [this message]
2012-01-16 18:19 ` Steve Sakoman
2012-01-16 18:45 ` Phil Blundell
2012-01-17 16:30 ` Philip Balister
2012-01-17 18:19 ` Joshua Lock
2012-01-22 2:39 ` Khem Raj
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=1326737165.2933.7.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.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 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.