From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 01/10] default-provider: also define a default provider for gconf-native
Date: Mon, 26 Sep 2011 13:41:57 +0100 [thread overview]
Message-ID: <1317040924.26109.33.camel@ted> (raw)
In-Reply-To: <j5pq7d$epu$1@dough.gmane.org>
On Mon, 2011-09-26 at 16:11 +0400, Dmitry Eremin-Solenikov wrote:
> Please delay this patch for a while.
Too late :(.
> Now I get the following warning in
> my build logs (If someone can tell me where the problem lies, that would
> help).
>
> ERROR: Trying to resolve runtime dependency gconf resulted in
> conflicting PREFERRED_PROVIDER entries being found.
> The providers found were:
> ['/home/users/mitya/OE/setup-scripts/sources/openembedded-core/meta/recipes-gnome/gnome/gconf-dbus_705.bb',
> 'virtual:native:/home/users/mitya/OE/setup-scripts/sources/openembedded-core/meta/recipes-gnome/gnome/gconf-dbus_705.bb']
> The PREFERRED_PROVIDER entries resulting in this conflict were:
> ['PREFERRED_PROVIDER_gconf = gconf-dbus',
> 'PREFERRED_PROVIDER_gconf-native = gconf-dbus-native']
> NOTE: multiple providers are available for runtime gconf
> (gconf-dbus-native, gconf-dbus, gconf)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match gconf
This asks the question why is gconf-dbus-native providing "gconf" and
not "gconf-native"?
Cheers,
Richard
prev parent reply other threads:[~2011-09-26 12:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 19:46 [PATCH 01/10] default-provider: also define a default provider for gconf-native Dmitry Eremin-Solenikov
2011-09-23 19:46 ` [PATCH 02/10] bitbake.conf: change ccache path to use MULTIMACH_HOST_SYS Dmitry Eremin-Solenikov
2011-09-23 19:46 ` [PATCH 03/10] bash-completion: new recipe Dmitry Eremin-Solenikov
2011-09-25 9:46 ` Richard Purdie
2011-09-23 19:46 ` [PATCH 04/10] dbus-glib: include bash-completion stuff Dmitry Eremin-Solenikov
2011-09-23 20:09 ` Otavio Salvador
2011-09-25 17:20 ` Richard Purdie
2011-09-25 17:34 ` Otavio Salvador
2011-09-25 17:44 ` Richard Purdie
2011-09-25 17:48 ` Anders Darander
2011-09-23 19:46 ` [PATCH 05/10] eglibc: fix packaging of some of nativesdk packages, V2 Dmitry Eremin-Solenikov
2011-09-25 17:22 ` Richard Purdie
2011-09-23 19:46 ` [PATCH 06/10] icecc-create-env-native: provide the script right in the tree Dmitry Eremin-Solenikov
2011-09-23 19:46 ` [PATCH 07/10] gcc: fix possible problems with nscd compilation during eglibc-nativesdk build Dmitry Eremin-Solenikov
2011-09-23 19:46 ` [PATCH 08/10] gcc: include libgcov.a into libgcc-dev package Dmitry Eremin-Solenikov
2011-09-23 19:46 ` [PATCH 09/10] gconf-dbus: packaging fixup Dmitry Eremin-Solenikov
2011-09-23 19:46 ` [PATCH 10/10] libffi: really populate -dev package Dmitry Eremin-Solenikov
2011-09-26 12:11 ` [PATCH 01/10] default-provider: also define a default provider for gconf-native Dmitry Eremin-Solenikov
2011-09-26 12:41 ` Richard Purdie [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=1317040924.26109.33.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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.