eeze 1.0.0: fix checksums
PATCH 1/1 eeze 1.0.0: fix checksums
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.
--- recipes/efl1/eeze_1.0.0.bb | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)
recipes/efl1/eeze_1.0.0.bb +2 -2
@@ -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"
Signature · 1 line
1.7.5.3
Quoted 15 lines · Eric Bénard
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 <[email protected]>--- recipes/efl1/eeze_1.0.0.bb | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)recipes/efl1/eeze_1.0.0.bb +0
-0
recipes/efl1/eeze_1.0.0.bb SRC_URI = "\ · line 10
Quoted 7 lines
recipes/efl1/eeze_1.0.0.bb +2
-2@@ -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...
Signature · 2 lines
Tom Rini Mentor Graphics Corporation
Quoted 19 lines · Tom Rini
Quoted 18 lines · Eric Bénard
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 <[email protected]>---
recipes/efl1/eeze_1.0.0.bb | 4 ++--1 files changed, 2 insertions(+), 2 deletions(-)recipes/efl1/eeze_1.0.0.bb +0
-0@@ -6,5 +6,5 @@ SRC_URI = "\ ${E_MIRROR}/${SRCNAME}-${PV}.tar.gz \"
Quoted 8 lines
recipes/efl1/eeze_1.0.0.bb SRC_URI = "\ · line 10
Quoted 4 lines
recipes/efl1/eeze_1.0.0.bb +2
-2-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)
Regards,
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 29 lines · Martin Jansa
Quoted 19 lines · Tom Rini
Quoted 18 lines · Eric Bénard
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 <[email protected]>--- recipes/efl1/eeze_1.0.0.bb | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)recipes/efl1/eeze_1.0.0.bb +0
-0@@ -6,5 +6,5 @@ SRC_URI = "\ ${E_MIRROR}/${SRCNAME}-${PV}.tar.gz \ "Quoted 8 lines
recipes/efl1/eeze_1.0.0.bb SRC_URI = "\ · line 10
Quoted 4 lines
recipes/efl1/eeze_1.0.0.bb +2
-2-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...
Quoted 6 lines
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)
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-----
Hi Tom,
Quoted 10 lines · Tom Rini
Quoted 6 lines · Martin Jansa
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)
Eric, can you please re-submit with a cherry-pick of this? Thanks!
yes I didn't even checked in master for a fix ... I also have a few other fixes but needs to test them against master before sending them.
Eric