On 17 July 2012 22:58, Saul Wold wrote:
> First seems to be missing pkgdata/runtime files, followed by a failed
> dependency by libglib-2.0-utils on the native python (from the native
> sysroot).
To keep track of these issues I've filed:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2784
"li
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/open
On Tue, Jul 17, 2012 at 05:26:48PM -0700, Saul Wold wrote:
> On 07/17/2012 02:58 PM, Saul Wold wrote:
> >
> > Folks,
> >
> > I am seeing a crop of failures on Master, this is not any failure I have
> > seen recently on any of my MUT builds. It appears to be 2 failures,
> > possibly related.
>
> No
On 07/17/2012 02:58 PM, Saul Wold wrote:
Folks,
I am seeing a crop of failures on Master, this is not any failure I have
seen recently on any of my MUT builds. It appears to be 2 failures,
possibly related.
Not related, I just confirmed this.
The "ls: cannot access" are coming from license.b
Folks,
I am seeing a crop of failures on Master, this is not any failure I have
seen recently on any of my MUT builds. It appears to be 2 failures,
possibly related.
First seems to be missing pkgdata/runtime files, followed by a failed
dependency by libglib-2.0-utils on the native python (f
