All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Steffen Sledz <sledz@dresearch.de>
Cc: openembedded-devel <openembedded-devel@openembedded.org>,
	bitbake-dev <bitbake-dev@lists.berlios.de>,
	openembedded-devel@lists.openembedded.org
Subject: Re: Bitbake 1.12.0 released! - ImportError: No module named ply
Date: Mon, 21 Feb 2011 12:31:59 +0000	[thread overview]
Message-ID: <1298291519.11289.3167.camel@rex> (raw)
In-Reply-To: <4D60DA13.5070806@dresearch.de>

On Sun, 2011-02-20 at 10:08 +0100, Steffen Sledz wrote:
> Trying bitbake 1.12.0 together with the testscript from contrib
> results in an error for me (openSUSE 11.3 32bit, bitbake 1.10.2 works
> fine):
> 
> sledz@mobil-400-586:~/tmp/xy> MACHINE=hipox TARGET_RECIPE=minimal-image DISTRO=angstrom-2008.1 TESTING_BRANCH=testing-release-2011.03 BB_MIN_VERSION=1.12.0 ~/work/openembedded/contrib/testing/testscript.sh
> Branch testing-release-2011.03 set up to track remote branch testing-release-2011.03 from origin.
> Already on 'testing-release-2011.03'
> Already up-to-date.
> hipox angstrom-2008.1 minimal-image testing-release-2011.03 72a088f7e1cf2eb0b50f285301478278c616c1cd
> Traceback (most recent call last):
>   File "/home/sledz/tmp/xy/bitbake-1.12.0/bin/bitbake", line 35, in <module>
>     import bb
>   File "/home/sledz/tmp/xy/bitbake-1.12.0/lib/bb/__init__.py", line 138, in <module>
>     deprecate_import(__name__, "bb.fetch", ("MalformedUrl", "encodeurl", "decodeurl"))
>   File "/home/sledz/tmp/xy/bitbake-1.12.0/lib/bb/__init__.py", line 126, in deprecate_import
>     module = __import__(modulename, fromlist = fromlist)
>   File "/home/sledz/tmp/xy/bitbake-1.12.0/lib/bb/fetch/__init__.py", line 32, in <module>
>     from   bb import data
>   File "/home/sledz/tmp/xy/bitbake-1.12.0/lib/bb/data.py", line 48, in <module>
>     from bb import data_smart
>   File "/home/sledz/tmp/xy/bitbake-1.12.0/lib/bb/data_smart.py", line 34, in <module>
>     import bb, bb.codeparser
>   File "/home/sledz/tmp/xy/bitbake-1.12.0/lib/bb/codeparser.py", line 7, in <module>
>     from pysh import pyshyacc, pyshlex
>   File "/home/sledz/tmp/xy/bitbake-1.12.0/lib/bb/pysh/pyshyacc.py", line 13, in <module>
>     import pyshlex
>   File "/home/sledz/tmp/xy/bitbake-1.12.0/lib/bb/pysh/pyshlex.py", line 22, in <module>
>     from ply import lex
> ImportError: No module named ply

Did you try installing python-ply or whatever the name of the ply module
for python is on openSUSE?

Cheers,

Richard




  parent reply	other threads:[~2011-02-21 12:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18 17:18 Bitbake 1.12.0 released! Richard Purdie
2011-02-18 17:50 ` Tom Rini
2011-02-20  9:08 ` Bitbake 1.12.0 released! - ImportError: No module named ply Steffen Sledz
2011-02-21  8:22   ` Steffen Sledz
2011-02-21 12:31   ` Richard Purdie [this message]
2011-02-21 13:28     ` Sledz, Steffen
2011-02-20 15:24 ` Bitbake 1.12.0 released! Koen Kooi
2011-02-21 14:36   ` Richard Purdie
2011-02-27 14:29 ` Jonathan Cameron
2011-02-27 15:30   ` Mike Westerhof
2011-02-27 20:14     ` Chris Larson
2011-02-27 22:15       ` Chris Larson
2011-02-28 16:47         ` Chris Larson
2011-02-27 15:36 ` Jonathan Cameron

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=1298291519.11289.3167.camel@rex \
    --to=rpurdie@rpsys.net \
    --cc=bitbake-dev@lists.berlios.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    --cc=sledz@dresearch.de \
    /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.