From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org, "Purdie,
Richard" <richard.purdie@intel.com>
Cc: "yocto-builds@yoctoproject.org" <yocto-builds@yoctoproject.org>
Subject: Re: Master Failures
Date: Wed, 18 Jul 2012 10:25:21 +0100 [thread overview]
Message-ID: <4121168.JiPW7RAvvb@helios> (raw)
In-Reply-To: <500602C8.6090805@linux.intel.com>
On Tuesday 17 July 2012 17:26:48 Saul Wold wrote:
> The "ls: cannot access" are coming from license.bbclass, seems to be a
> timing issue related to the last patch here, not sure what triggered it
> here (I am not seeing it on other builds!)
>
> Paul's Change:
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=sgw%2Fstage&qt=
> grep&q=license
It seems to me the problem is that the pkgdata is in non-debian renamed format
whereas license.bbclass by virtue of using the final list of installed packages
is expecting to use the post-rename names (e.g. pkgdata/*/runtime contains
zlib-dev whereas the installed package is called libz-dev). Given that this
renaming happens much earlier in the process, I'm not sure how my change could
have triggered this or why it would only be a problem sometimes.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-07-18 9:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 21:58 Master Failures Saul Wold
2012-07-18 0:26 ` Saul Wold
2012-07-18 0:38 ` Martin Jansa
2012-07-18 0:52 ` Glib-2.0 cross-compile issue Was: " Martin Jansa
2012-07-18 0:57 ` Saul Wold
2012-07-18 1:01 ` Colin Walters
2012-07-18 1:05 ` Martin Jansa
2012-07-18 9:17 ` [PATCH] glib-2.0: revert one commit in target recipe Martin Jansa
2012-07-18 21:25 ` Richard Purdie
2012-07-18 9:25 ` Paul Eggleton [this message]
2012-07-18 9:36 ` Master Failures Burton, Ross
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=4121168.JiPW7RAvvb@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@intel.com \
--cc=yocto-builds@yoctoproject.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.