From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH 2011.03] eeze 1.0.0: fix checksums
Date: Thu, 16 Jun 2011 07:17:28 -0700 [thread overview]
Message-ID: <4DFA1078.7090808@mentor.com> (raw)
In-Reply-To: <BANLkTinmc_Wp-vFoKuRe_LpFdwmVeU8bnQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06/15/2011 10:27 PM, Martin Jansa wrote:
> On Thu, Jun 16, 2011 at 2:25 AM, Tom Rini <tom_rini@mentor.com> wrote:
>> 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...
>
> I guess it won't be repeated with each release.. you can cherry-pick
> my commit with better commit message explaining what was changed from
> master (or Eric can send pull request for that, I'm away from my
> workstation and I'm not using 2010.13)
>
> http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=79d295c31e64e972608d5dde5d57e6250d7ca77c
Eric, can you please re-submit with a cherry-pick of this? Thanks!
- --
Tom Rini
Mentor Graphics Corporation
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJN+hBiAAoJEI4NMjfc3nJxNAIH/jSyd28xDTJl23wi8iNIkvea
QLZClHWEhM4GSxDlzLsK+C1rJCwyh21abJGoGQebbRM+1OhdRndZnRjO7b29J7sL
8Nt2QVPQ17vKWcGBBRwUxGPOYMKQosbHzNvKlr4s4PWXdbYXsN+N4tNKO4MuQNxu
D34R+HTgVgcqWzouRqLSfAzFVQ8k0nEQ2GP11lXOLOfeQa2uZFlormRiaq6fqZUP
dYt9LzH0U7d8hVNVNFYyXXnEC3PXXb46u58uk+gbbXt3DGAg2bzhP0kcnSU3pOyG
+8JL/HoBPNJJYunWg9/4Cqus0RchAK0NAz0bkIx64DFB7XHJpcqfg/o37u+CiF4=
=xFa+
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-06-16 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 21:25 [PATCH 2011.03] eeze 1.0.0: fix checksums Eric Bénard
2011-06-16 0:25 ` Tom Rini
2011-06-16 5:27 ` Martin Jansa
2011-06-16 14:17 ` Tom Rini [this message]
2011-06-16 14:50 ` Eric Bénard
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=4DFA1078.7090808@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-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 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.