Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Zhenfeng.Zhao@windriver.com
Subject: Re: [PATCH 0/2] createrepo 0.4.11: create wrapper for python script
Date: Sat, 4 Aug 2012 15:04:21 +0800	[thread overview]
Message-ID: <501CC975.2030009@windriver.com> (raw)
In-Reply-To: <CAMKF1srwmN9_-p5ae6999wdZGfpfXLseCnwegnQxa7ckAVOcLw@mail.gmail.com>



On 08/03/2012 07:10 PM, Khem Raj wrote:
> On Wed, Aug 1, 2012 at 2:14 AM, Robert Yang <liezhi.yang@windriver.com> wrote:
>> This is used for fixing the rpm-createsolvedb.py error:
>>
>> 'import site' failed; use -v for traceback
>> Traceback (most recent call last):
>> File "/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly/build/scripts/rpm-createsolvedb.py", line 14, in
>> import sys, os
>> ImportError: No module named os
>>
>
> this series has problem I think now bitbake meta-toolchain fails for me
>
> run.populate_sdk_image.6792: line 610: rpm-createsolvedb.py: command not found
>
> did you try bitbake meta-toolchain target from scratch with this change ?
>

Hi Khem,

I'm sorry for this, this is because I hadn't fixed the depends of
populate_sdk_image, "bitbake createrepo-native" firstly can be a workaround,
I will send a official fix sooner.

// Robert

>
>
>> // Robert
>>
>> The following changes since commit 4f31d21bcb1c8c744e9abb33248715afe4a40af0:
>>
>>    lib/oe/lsb.py: Map unknown distributions to 'Unknown' (2012-07-31 08:02:11 +0100)
>>
>> are available in the git repository at:
>>    git://git.pokylinux.org/poky-contrib robert/createrepo
>>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/createrepo
>>
>> Robert Yang (2):
>>    createrepo 0.4.11: add rpm-createsolvedb.py
>>    createrepo 0.4.11: create wrapper for python script
>>
>>   meta/classes/rootfs_rpm.bbclass                    |    2 +-
>>   .../createrepo/createrepo}/rpm-createsolvedb.py    |    0
>>   .../createrepo/createrepo_0.4.11.bb                |   17 ++++++++++++++++-
>>   3 files changed, 17 insertions(+), 2 deletions(-)
>>   rename {scripts => meta/recipes-support/createrepo/createrepo}/rpm-createsolvedb.py (100%)
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>




  reply	other threads:[~2012-08-04  7:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01  9:14 [PATCH 0/2] createrepo 0.4.11: create wrapper for python script Robert Yang
2012-08-01  9:14 ` [PATCH 1/2] createrepo 0.4.11: add rpm-createsolvedb.py Robert Yang
2012-08-01  9:14 ` [PATCH 2/2] createrepo 0.4.11: create wrapper for python script Robert Yang
2012-08-01 22:03 ` [PATCH 0/2] " Richard Purdie
2012-08-03 11:10 ` Khem Raj
2012-08-04  7:04   ` Robert Yang [this message]
2012-08-04  7:08     ` Robert Yang

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=501CC975.2030009@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=Zhenfeng.Zhao@windriver.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