From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Python3 error?
Date: Fri, 03 Jun 2016 14:39:46 +0100 [thread overview]
Message-ID: <1464961186.13979.19.camel@linuxfoundation.org> (raw)
In-Reply-To: <57512CE8.4030607@mlbassoc.com>
On Fri, 2016-06-03 at 09:08 +0200, Gary Thomas wrote:
> After the change over to Python3, I'm getting this error:
>
> ERROR: Unable to parse /local/poky-cutting-edge/meta-gnome/recipes
> -gnome/gnome-vfs/gnome-vfs_2.24.4.bb
> Traceback (most recent call last):
> File "/local/poky-cutting-edge/bitbake/lib/bb/siggen.py", line
> 151, in
> SignatureGeneratorOEBasicHash.finalise(fn='/local/poky-cutting
> -edge/meta-gnome/recipes-gnome/gnome-vfs/gnome-vfs_2.24.4.bb',
> d=<bb.data_smart.DataSmart object at 0x7f3d6ec78b38>, variant=None):
> try:
> > taskdeps = self._build_data(fn, d)
> except:
> File "/local/poky-cutting-edge/bitbake/lib/bb/siggen.py", line
> 104, in
> SignatureGeneratorOEBasicHash._build_data(fn='/local/poky-cutting
> -edge/meta-gnome/recipes-gnome/gnome-vfs/gnome-vfs_2.24.4.bb',
> d=<bb.data_smart.DataSmart object at 0x7f3d6ec78b38>):
>
> > tasklist, gendeps, lookupcache =
> bb.data.generate_dependencies(d)
>
> File "/local/poky-cutting-edge/bitbake/lib/bb/data.py", line 438,
> in generate_dependencies(d=<bb.data_smart.DataSmart
> object at 0x7f3d6ec78b38>):
> if dep not in deps:
> > deps[dep], values[dep] =
> build_dependencies(dep, keys, shelldeps, varflagsexcl, d)
> newdeps |= deps[dep]
>
> This is from a recipe in meta-openembedded
>
> Any ideas how to fix it?
Did you have the python3 patches I sent to oe-devel yesterday applied?
Cheers,
Richard
next prev parent reply other threads:[~2016-06-03 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 7:08 Python3 error? Gary Thomas
2016-06-03 13:39 ` Richard Purdie [this message]
2016-06-03 13:41 ` Richard Purdie
2016-06-04 6:56 ` Gary Thomas
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=1464961186.13979.19.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=gary@mlbassoc.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox