All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: update-alternatives WARNING
Date: Thu, 23 Jan 2014 16:23:18 +0100	[thread overview]
Message-ID: <20140123152318.GG3704@jama> (raw)
In-Reply-To: <CAP9ODKpdT9yypcEReFj2mDuL4UEuj5_0xOOJqnO4Q3qfS=NcdQ@mail.gmail.com>

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

On Thu, Jan 23, 2014 at 11:41:12AM -0200, Otavio Salvador wrote:
> Hello,
> 
> I am seeing this:
> 
> WARNING: The recipe opkg-utils-native is trying to install files into
> a shared area when those files already exist. Those files and their
> manifest location are:
>    /home/otavio/hacking/fsl/yocto/build/tmp/sysroots/x86_64-linux/usr/bin/update-alternatives
>    Matched in manifest-x86_64-opkg-native.populate_sysroot
> 
> In todays' tip.
> 
> Is it a known issue?

If it's incremental build, then it's expected.

/usr/bin/update-alternatives was moved from opkg to opkg-utils and
sstate doesn't know that opkg-native should be rebuilt befor opkg-utils,
because they don't have any dependency.

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

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

      reply	other threads:[~2014-01-23 15:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23 13:41 update-alternatives WARNING Otavio Salvador
2014-01-23 15:23 ` 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=20140123152318.GG3704@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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.