From: Joshua Lock <josh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/2] fetch2: improve usability of checksums
Date: Wed, 19 Oct 2011 10:22:16 -0700 [thread overview]
Message-ID: <4E9F0748.3090901@linux.intel.com> (raw)
In-Reply-To: <63dc9197eb483863e1cec5e58f036b7493850787.1318352470.git.josh@linux.intel.com>
On 10/11/2011 10:07 AM, Joshua Lock wrote:
> if ud.sha256_expected != sha256data:
> - raise SHA256SumError(ud.localpath, ud.sha256_expected, sha256data, u)
> + sha256mismatch = True
> +
> + # We want to alert the user if a checksum is defined in the recipe but
> + # it does not match.
> + msg = ""
> + if md5mismatch and ud.md5_expected:
> + msg = msg + "\nFile: '%s' has %s checksum %s when %s was expected (from URL: '%s')" % (ud.localpath, 'md5', ud.md5_expected, md5data, u)
> +
> + if sha256mismatch and ud.sha256_expected:
> + msg = msg + "\nFile: '%s' has %s checksum %s when %s was expected (from URL: '%s')" % (ud.localpath, 'sha256', ud.sha256_expected, sha256data, u)
> +
Just realised I was passing the expected and data parameters in the
wrong order - I've pushed a fix to the same branch.
Cheers,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-10-19 17:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 17:07 [PATCH 0/2] Improve usability of checksums Joshua Lock
2011-10-11 17:07 ` [PATCH 1/2] fetch2: improve " Joshua Lock
2011-10-12 19:21 ` Chris Larson
2011-10-13 12:49 ` Martin Jansa
2011-10-19 17:22 ` Joshua Lock [this message]
2011-10-11 17:07 ` [PATCH 2/2] fetch2: enable checksum definition as SRC_URI parameter Joshua Lock
2011-10-11 18:05 ` Khem Raj
2011-10-11 20:21 ` Joshua Lock
2011-10-11 17:19 ` [PATCH 0/2] Improve usability of checksums Scott Garman
2011-10-24 16:38 ` 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=4E9F0748.3090901@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox