Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Where is libunique?
Date: Mon, 7 Sep 2015 17:09:06 +0200	[thread overview]
Message-ID: <20150907150906.GA2457@jama> (raw)
In-Reply-To: <55ED8405.6050709@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]

On Mon, Sep 07, 2015 at 03:33:09PM +0300, Alexander Kanavin wrote:
> On 09/07/2015 12:13 PM, Mike Looijmans wrote:
> > Current meta-openembedded master fails to build with errors like this:
> >
> > ERROR: Nothing PROVIDES 'libunique' (but
> > .../meta-oe/meta-gnome/recipes-gnome/gnome-disk-utility/gnome-disk-utility_2.32.0.bb
> > DEPENDS on or otherwise requires it).
> >
> > Searching for 'unique' in meta-openembedded and openembedded-core
> > reveiled nothing that would provide it, there's no recipe with 'unique'
> > in its name, nor any recipe that mentions the word 'unique' provides it,
> > even though I found various recipes that DEPEND on it.
> >
> > Where is libunique?
> 
> You should check not just the current state of master branches of 
> various layers, but also their commit history.
> 
> libunique was just removed from oe-core and a patch was sent to add it 
> to meta-oe. There is no way to keep the removal/addition perfectly in 
> sync because the two layers are kept in separate repos and have 
> different maintainers.

This case can be prevented by adding it to meta-oe before it's removed
from oe-core (just like when someone is migrating recipes from meta-oe
to oe-core, they are first added to oe-core and then removed from
meta-oe).

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2015-09-07 15:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-07  9:13 Where is libunique? Mike Looijmans
2015-09-07 12:33 ` Alexander Kanavin
2015-09-07 15:09   ` Martin Jansa [this message]
2015-09-07 15:23     ` Christopher Larson
2015-09-07 17:25     ` Mike Looijmans

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=20150907150906.GA2457@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox