From: Joshua Lock <josh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] runningbuild.py: fix goggle ui
Date: Wed, 21 Mar 2012 18:10:16 -0700 [thread overview]
Message-ID: <4F6A7BF8.7050904@linux.intel.com> (raw)
In-Reply-To: <1332344691-24973-1-git-send-email-eric@eukrea.com>
On 21/03/12 08:44, Eric Bénard wrote:
> without this fix I get the following error once the build is finished :
> Traceback (most recent call last):
> File ".../bitbake/lib/bb/ui/goggle.py", line 35, in event_handle_idle_func
> build.handle_event (event, pbar)
> File ".../bitbake/lib/bb/ui/crumbs/runningbuild.py", line 287, in handle_event
> pbar.set_text(event.msg)
> AttributeError: 'ProgressBar' object has no attribute 'set_text'
>
> Signed-off-by: Eric Bénard<eric@eukrea.com>
Signed-off-by: Joshua Lock <josh@linux.intel.com>
> ---
> lib/bb/ui/crumbs/runningbuild.py | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/lib/bb/ui/crumbs/runningbuild.py b/lib/bb/ui/crumbs/runningbuild.py
> index 4c3fe2c..343eac9 100644
> --- a/lib/bb/ui/crumbs/runningbuild.py
> +++ b/lib/bb/ui/crumbs/runningbuild.py
> @@ -284,7 +284,7 @@ class RunningBuild (gobject.GObject):
> # handle when the build is finished
> self.emit("build-complete")
> if pbar:
> - pbar.set_text(event.msg)
> + pbar.set_title(event.msg)
>
> elif isinstance(event, bb.command.CommandFailed):
> if event.error.startswith("Exited with"):
--
Joshua '贾詡' Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-03-22 1:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 15:44 [PATCH] runningbuild.py: fix goggle ui Eric Bénard
2012-03-22 1:10 ` Joshua Lock [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-19 11:56 Eric Bénard
2012-03-20 14:13 ` Richard Purdie
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=4F6A7BF8.7050904@linux.intel.com \
--to=josh@linux.intel.com \
--cc=bitbake-devel@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 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.