From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] ui: Improve error message if bitbake cannot import python curses module
Date: Wed, 22 Aug 2012 13:56:55 +0100 [thread overview]
Message-ID: <1345640215.3907.113.camel@ted> (raw)
In-Reply-To: <1345583158-3142-1-git-send-email-mark.hatle@windriver.com>
On Tue, 2012-08-21 at 16:05 -0500, Mark Hatle wrote:
> From: Konrad Scherer <Konrad.Scherer@windriver.com>
>
> On some SuSE systems, the curses python module is not installed by default.
> Instead of a python failure, we want a nicer error message.
>
> (On SuSE systems the package is typically python-curses.)
>
> Signed-off-by: Konrad Scherer <Konrad.Scherer@windriver.com>
> Signed-off-by: Jeff Polk <jeff.polk@windriver.com>
>
> Reword commit message, rebase to latest bitbake.
>
> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
> ---
> lib/bb/ui/knotty.py | 6 +++++-
> lib/bb/ui/ncurses.py | 8 +++++++-
> 2 files changed, 12 insertions(+), 2 deletions(-)
Thanks, merged to master.
I did wonder if this shouldn't just print a warning and proceed as if
the terminal were non-interactive though. Regardless, this improves the
situation.
Cheers,
Richard
next prev parent reply other threads:[~2012-08-22 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 21:05 [PATCH] ui: Improve error message if bitbake cannot import python curses module Mark Hatle
2012-08-22 12:56 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-21 19:17 Mark Hatle
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=1345640215.3907.113.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=mark.hatle@windriver.com \
/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.