Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Damian, Alexandru" <alexandru.damian@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: python error when building various packages
Date: Thu, 12 Jul 2012 10:34:38 +0100	[thread overview]
Message-ID: <1901411.bouqtbEZ1W@helios> (raw)
In-Reply-To: <CAJ2CSBt+NSLH0_WhdDfMN8GUw5epy_u31aeESaZxT=7rQ90WfQ@mail.gmail.com>

On Thursday 12 July 2012 11:56:16 Damian, Alexandru wrote:
> Solved by do_clean on the packages.
> 
> Still Alex doesn't know what triggers the error.

I'm not sure either, but would you mind filing a bug for this?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-07-12  9:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06 14:44 python error when building various packages Damian, Alexandru
2012-07-12  8:56 ` Damian, Alexandru
2012-07-12  9:34   ` Paul Eggleton [this message]
2012-07-12 13:47     ` Damian, Alexandru
2012-07-12 18:47       ` Randy MacLeod

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=1901411.bouqtbEZ1W@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=alexandru.damian@intel.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