From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Yu Ke <ke.yu@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/1] SRC_URI checksum support v3
Date: Mon, 20 Dec 2010 16:10:28 +0000 [thread overview]
Message-ID: <1292861428.25087.4661.camel@rex> (raw)
In-Reply-To: <cover.1292567626.git.ke.yu@intel.com>
On Fri, 2010-12-17 at 14:33 +0800, Yu Ke wrote:
> This patch add SRC_URI checksum support. With this patch,fetcher
> can verify the MD5 and SHA256 checksum of download src with the
> value defined in recipes SRC_URI.
>
> This is the v3 patch with following changes compared with v2:
> - add configurable variable BB_STRICT_CHECKSUM to handle checksum missing case
> if checksum is missing and BB_STRICT_CHECKSUM = "1", bitbake will fatal
> - add check to only verify checksum for protocol http/https/ftp/ftps, not
> verify checksum for local file and other SCM
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: kyu3/srcuri-v3
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kyu3/srcuri-v3
I merged this, then realised there was a problem with subsequent builds
proceeding with corrupt files. I've pushed a fix for at least part of
that.
I'm wondering if we should rename the file to something like the
original name + ".corrupt" to make sure we don't use a known broken
file?
Cheers,
Richard
next prev parent reply other threads:[~2010-12-20 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 6:33 [PATCH 0/1] SRC_URI checksum support v3 Yu Ke
2010-12-17 5:52 ` [PATCH 1/1] FetchData: add SRC_URI checksum Yu Ke
2010-12-20 16:10 ` Richard Purdie [this message]
2010-12-21 5:32 ` [PATCH 0/1] SRC_URI checksum support v3 Yu Ke
2010-12-21 10:54 ` Joshua Lock
2010-12-21 11:04 ` Richard Purdie
2010-12-21 13:17 ` Yu Ke
2010-12-21 13:25 ` Yu Ke
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=1292861428.25087.4661.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=ke.yu@intel.com \
--cc=poky@yoctoproject.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