From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: "openembedded-core@lists.openembedded.org layer"
<openembedded-core@lists.openembedded.org>
Subject: Re: Annoyances with dylan
Date: Sat, 27 Apr 2013 11:19:15 +0100 [thread overview]
Message-ID: <1367057955.29677.99.camel@ted> (raw)
In-Reply-To: <5E6BBD57-21F8-4282-97F0-567ACFB008CD@dominion.thruhere.net>
On Fri, 2013-04-26 at 16:47 +0200, Koen Kooi wrote:
> Hi,
>
> I have 2 big annoyances with dylan:
>
> 1) Multimachine builds trigger spurious warnings:
>
> WARNING: The recipe bonescript is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
> /build/v2013.06/deploy/eglibc/licenses/bonescript/LICENSE
> /build/v2013.06/deploy/eglibc/licenses/bonescript/generic_MIT
>
> I get that every time after switching machines for each recipe/license.
This sounds like a symptom of a deeper problem. At a guess bonescript
has some machine specific element in it but its not marked as machine
specific and hence the system is getting confused. Do you have a list of
the recipes/licenses that are showing this? It is just license issues?
> 2) PRSERV makes things go backwards:
>
> ERROR: Package version for package gadget-init-network went backwards which would break package feeds from (0:1.0-r19.3 to 0:1.0-r19.0)
>
> To trigger 2) I updated meta-linaro and switches meta-minnow to the
> new rebased branch, delete $TMPDIR (prserv db is outside out TMPDIR)
> and started building images. I only happens for some recipes, not all.
> I can't deduce a pattern or easily reproduce it. Bug filed some months
> ago.
IIRC we looked into that bug quite extensively and couldn't find a way
to reproduce it. If we want to get it fixed, we're going to need some
help distilling it down to a simpler test case to reproduce so we can
understand the issue, then we can look at fixing it.
> On the flip side: *ZERO* problems with sstate so far :)
Nice to know :)
Cheers,
Richard
next prev parent reply other threads:[~2013-04-27 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 14:47 Annoyances with dylan Koen Kooi
2013-04-27 10:19 ` Richard Purdie [this message]
2013-04-27 12:21 ` Koen Kooi
2013-04-27 11:08 ` Marcin Juszkiewicz
2013-04-27 12:18 ` Koen Kooi
2013-04-27 14:46 ` Marcin Juszkiewicz
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=1367057955.29677.99.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.