From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel <openembedded-devel@openembedded.org>,
bitbake-dev <bitbake-dev@lists.berlios.de>
Subject: Re: Bitbake 1.12.0 released! - ImportError: No module named ply
Date: Mon, 21 Feb 2011 09:22:15 +0100 [thread overview]
Message-ID: <4D6220B7.8000100@dresearch.de> (raw)
In-Reply-To: <4D60DA13.5070806@dresearch.de>
Am 20.02.2011 10:08, schrieb Steffen Sledz:
> 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):
> ...
> ImportError: No module named ply
Could be fixed by installing additional python-ply package.
Next problem was the missing progressbar module. Unfortunately there is no openSUSE package for it so i had to install directly from pypi.python.org. :(
It think there should be some sanity checks for such problems.
Steffen
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@DResearch.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next prev parent reply other threads:[~2011-02-21 8:23 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 [this message]
2011-02-21 12:31 ` Richard Purdie
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=4D6220B7.8000100@dresearch.de \
--to=sledz@dresearch.de \
--cc=bitbake-dev@lists.berlios.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.