Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH] runningbuild.py: fix goggle ui
Date: Wed, 21 Mar 2012 16:44:51 +0100	[thread overview]
Message-ID: <1332344691-24973-1-git-send-email-eric@eukrea.com> (raw)

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>
---
 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"):
-- 
1.7.7.6




             reply	other threads:[~2012-03-21 15:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21 15:44 Eric Bénard [this message]
2012-03-22  1:10 ` [PATCH] runningbuild.py: fix goggle ui Joshua Lock
  -- 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=1332344691-24973-1-git-send-email-eric@eukrea.com \
    --to=eric@eukrea.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox