Skip to contentSkip to conversation

Revert "busybox_1.18.4.bb: Fix checksums of busybox-1.18.4-hush.patch"

PATCH In review Paul Menzel 3 participants 4 messages Jun 4, 2011

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Revert "busybox_1.18.4.bb: Fix checksums of busybox-1.18.4-hush.patch"

Date: Sat, 4 Jun 2011 19:35:03 +0200

This reverts commit 688b8dc036f504ae1bdf1736bf211a0c62de03f8.

        commit 688b8dc036f504ae1bdf1736bf211a0c62de03f8
        Author: Khem Raj <[email protected]>
        Date:   Fri Jun 3 11:38:12 2011 -0700
        
            busybox_1.18.4.bb: Fix checksums of busybox-1.18.4-hush.patch
            
            Signed-off-by: Khem Raj <[email protected]>

The old checksums are the ones I get when downloading the patch.

        $ zless minimal-dev/work/armv7a-oe-linux-gnueabi/busybox-1.18.4-r43.2/temp/log.do_fetch
        NOTE: The checksums for 'busybox-1.18.4-hush.patch' did not match.
        Expected MD5: '91005640b4b434ab5029fa5a0349a33c' and Got: 'a81f2d7d3bdf1a35ab77c4414a530d38'
        Expected SHA256: 'e76da947c40784c9a0527c38b1e9edb615c80cfe911d28b9d8a5d67a492bf67c' and Got: 'c87e73ad942d53c8a2a5ffe6037c1cdf52d4b20d3f29caae5fffc7a99009b7cb'
        NOTE: Your checksums:
        SRC_URI[patch01.md5sum] = "a81f2d7d3bdf1a35ab77c4414a530d38"
        SRC_URI[patch01.sha256sum] = "c87e73ad942d53c8a2a5ffe6037c1cdf52d4b20d3f29caae5fffc7a99009b7cb"
---
 recipes/busybox/busybox_1.18.4.bb |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
recipes/busybox/busybox_1.18.4.bb +2 -2
index b72510d..68a023a 100644
@@ -7,5 +7,5 @@ PR = "${INC_PR}.2"
 
 SRC_URI[md5sum] = "b03c5b46ced732679e525a920a1a62f5"
 SRC_URI[sha256sum] = "4d24d37bd6f1bd153e8cf9a984ec2f32f18464f73ca535e2cc2e8be9694097fa"
-SRC_URI[patch01.md5sum] = "91005640b4b434ab5029fa5a0349a33c"
-SRC_URI[patch01.sha256sum] = "e76da947c40784c9a0527c38b1e9edb615c80cfe911d28b9d8a5d67a492bf67c"
+SRC_URI[patch01.md5sum] = "a81f2d7d3bdf1a35ab77c4414a530d38"
+SRC_URI[patch01.sha256sum] = "c87e73ad942d53c8a2a5ffe6037c1cdf52d4b20d3f29caae5fffc7a99009b7cb"
Signature · 1 line
1.7.5.3
#1 lore raw

Dear OpenEmbedded folks,

Am Samstag, den 04.06.2011, 19:38 +0200 schrieb Paul Menzel:

Quoted 14 lines

Date: Sat, 4 Jun 2011 19:35:03 +0200

This reverts commit 688b8dc036f504ae1bdf1736bf211a0c62de03f8.

        commit 688b8dc036f504ae1bdf1736bf211a0c62de03f8
        Author: Khem Raj <[email protected]>
        Date:   Fri Jun 3 11:38:12 2011 -0700
        
            busybox_1.18.4.bb: Fix checksums of busybox-1.18.4-hush.patch
            
            Signed-off-by: Khem Raj <[email protected]>

The old checksums are the ones I get when downloading the patch.

Quoted 7 lines
        $ zless minimal-dev/work/armv7a-oe-linux-gnueabi/busybox-1.18.4-r43.2/temp/log.do_fetch
        NOTE: The checksums for 'busybox-1.18.4-hush.patch' did not match.
        Expected MD5: '91005640b4b434ab5029fa5a0349a33c' and Got: 'a81f2d7d3bdf1a35ab77c4414a530d38'
        Expected SHA256: 'e76da947c40784c9a0527c38b1e9edb615c80cfe911d28b9d8a5d67a492bf67c' and Got: 'c87e73ad942d53c8a2a5ffe6037c1cdf52d4b20d3f29caae5fffc7a99009b7cb'
        NOTE: Your checksums:
        SRC_URI[patch01.md5sum] = "a81f2d7d3bdf1a35ab77c4414a530d38"
        SRC_URI[patch01.sha256sum] = "c87e73ad942d53c8a2a5ffe6037c1cdf52d4b20d3f29caae5fffc7a99009b7cb"

[…]

Please ignore this patch as I had the old patch file in cached my download directory.

Is there a way in BitBake to check and redownload a file if the checksums do not match?

Another solution would be to handle all patches in OpenEmbedded directly.

Thanks,

Paul

#2 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 2 lines · Paul Menzel

Another solution would be to handle all patches in OpenEmbedded directly.

That is what I have been saying for a while now... -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFN6nQGMkyGM64RGpERAkZbAJ9pE5fAuNMdnKbpPB2ChXInOAtgAACgsSLr /xXZSPeVhGjaDJpTxUyL+t4=
=xeAs
-----END PGP SIGNATURE-----

#3 lore raw
Quoted 9 lines · Koen Kooi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 2 lines · Paul Menzel

Another solution would be to handle all patches in OpenEmbedded directly.

That is what I have been saying for a while now...

that's what was initially done but I was asked to change to remotely fetched patches which can create this trouble if busybox's patches are updated.

Eric