Re: [PATCH 2011.03] eeze 1.0.0: fix checksums

[Tom Rini <tom_rini@mentor.com>]

On 06/15/2011 02:25 PM, Eric Bénard wrote:
> the 1.0.0 archive seems to have been changed on the march 17th
> when 1.0.1 was created.
> This creates a failure when trying to build from scratch using
> Angstrom 2008.1 from the maintenance branch.
> 
> Signed-off-by: Eric Bénard <eric@eukrea.com>
> ---
>  recipes/efl1/eeze_1.0.0.bb |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/recipes/efl1/eeze_1.0.0.bb b/recipes/efl1/eeze_1.0.0.bb
> index 12d70d9..b050473 100644
> --- a/recipes/efl1/eeze_1.0.0.bb
> +++ b/recipes/efl1/eeze_1.0.0.bb
> @@ -6,5 +6,5 @@ SRC_URI = "\
>    ${E_MIRROR}/${SRCNAME}-${PV}.tar.gz \
>  "
>  
> -SRC_URI[md5sum] = "31f9b2a8fce56a73c99c1c5d2a449fb6"
> -SRC_URI[sha256sum] = "27da2b12f60b3c23cd52d16d601b5ab61734b9038beb3ab40129ac770f048d84"
> +SRC_URI[md5sum] = "8fa2aa89ba48f262700a3cf88cb1c777"
> +SRC_URI[sha256sum] = "d8ffb1af53c03c5860cd90ae78aa5ae0ce2d027a462509deaca5ee3adacd0cee"

Is it possible to check eeze 1.0.0 out of upstream scm?  That way when
1.0.2 comes out (or whatever) we don't run the risk of this going bad,
again, and so forth...

-- 
Tom Rini
Mentor Graphics Corporation