From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Joshua Lock <josh@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] fetch2: fix Exception parameters when BB_STRICT_CHECKSUM enabled
Date: Mon, 05 Dec 2011 16:18:08 +0000 [thread overview]
Message-ID: <1323101888.25960.99.camel@ted> (raw)
In-Reply-To: <1322852315-7036-1-git-send-email-josh@linux.intel.com>
On Fri, 2011-12-02 at 10:58 -0800, Joshua Lock wrote:
> BB_STRICT_CHECKSUM caused a backtrace as the FetchError parameters are
> incorrectly specified such that FetchError is being passed 8 params
> when it's expecting 3. This fixes the parameters so we're passing a
> formatted string and the url.
>
> Signed-off-by: Joshua Lock <josh@linux.intel.com>
> ---
> lib/bb/fetch2/__init__.py | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
Merged to master, thanks.
Richard
next prev parent reply other threads:[~2011-12-05 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 18:58 [PATCH] fetch2: fix Exception parameters when BB_STRICT_CHECKSUM enabled Joshua Lock
2011-12-05 16:18 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-06 10:06 Martin Jansa
2011-12-13 22:11 ` Joshua Lock
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=1323101888.25960.99.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=josh@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox