From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Linux-libc-headers do_fetch Failed due to cheksum mismatch
Date: Mon, 07 Mar 2011 07:38:16 -0700 [thread overview]
Message-ID: <4D74EDD8.8080709@balister.org> (raw)
In-Reply-To: <1299424825.28285.20.camel@mattotaupa>
On 03/06/2011 08:20 AM, Paul Menzel wrote:
> Dear Saleh,
>
>
> Am Sonntag, den 06.03.2011, 19:49 +0500 schrieb saleh usman:
>
> […]
>
> please do not insert empty lines at the beginning of messages.
>
>> I am building console-image
>
> What machine do you use?
>
>> and having problem while fetching liunx-libc-headers. do_fetch task is
>> failed due to checksum mismatch. Kindly guide me how to resolve this
>> issue.console log follows
>>
>> NOTE: Running task 16 of 4329 (ID: 678, virtual:native:/oe/openembedded/recipes/linux-libc-headers/linux-libc-headers_2.6.31.bb, do_fetch)
>> NOTE: package linux-libc-headers-native-2.6.31-r6: task do_fetch: Started
>> FATAL: linux-libc-headers-native-2.6.31: http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.31.tar.bz2 cannot check archive integrity
>> ERROR: Error in executing python function in: /oe/openembedded/recipes/linux-libc-headers/linux-libc-headers_2.6.31.bb
>> ERROR: Exception:<type 'exceptions.SystemExit'> Message:1
>> ERROR: Printing the environment of the function
>> ERROR: Function base_do_fetch failed
>> ERROR: TaskFailed event exception, aborting
>> ERROR: Build of virtual:native:/oe/openembedded/recipes/linux-libc-headers/linux-libc-headers_2.6.31.bb do_fetch failed
>> NOTE: The checksums for '/oe/openembedded/sources/linux-2.6.31.tar.bz2' did not match.
>> Expected MD5: '84c077a37684e4cbfa67b18154390d8a' and Got: '9244b699b966804dfc2e243c89b3ead4'
>> Expected SHA256: '0acd83f7b85db7ee18c2b0b7505e1ba6fd722c36f49a8870a831c851660e3512' and Got: 'c522e06dc9639473f9962ed49b038ef5577e5d10cd2f4d9e4c62cdf3223de089'
>> NOTE: Your checksums:
>> SRC_URI[md5sum] = "9244b699b966804dfc2e243c89b3ead4"
>> SRC_URI[sha256sum] = "c522e06dc9639473f9962ed49b038ef5577e5d10cd2f4d9e4c62cdf3223de089"
>>
>> FATAL: linux-libc-headers-native-2.6.31: http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.31.tar.bz2 cannot check archive integrity
>
> As you can see in the recipe [1] and read in the user manual each
> downloaded file has a checksum to check the validity. The file you got
> seems to be corrupt, since the checksums in the recipes [1] are also the
> ones I got.
>
> $ wget http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.31.tar.bz2
> --2011-03-06 16:09:49-- http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.31.tar.bz2
> Auflösen des Hostnamen kernel.org... 130.239.17.4, 149.20.4.69, 149.20.20.133, ...
> Verbindungsaufbau zu kernel.org|130.239.17.4|:80... verbunden.
> HTTP-Anforderung gesendet, warte auf Antwort... 200 OK
> Länge: 61494822 (59M) [application/x-bzip2]
> In »linux-2.6.31.tar.bz2« speichern.
>
> 100%[======================================>] 61.494.822 1,29M/s in 46s
>
> 2011-03-06 16:10:35 (1,28 MB/s) - »linux-2.6.31.tar.bz2« gespeichert [61494822/61494822]
>
> $ md5sum linux-2.6.31.tar.bz2
> 84c077a37684e4cbfa67b18154390d8a linux-2.6.31.tar.bz2
> $ sha256sum linux-2.6.31.tar.bz2
> 0acd83f7b85db7ee18c2b0b7505e1ba6fd722c36f49a8870a831c851660e3512 linux-2.6.31.tar.bz2
>
> So something has gone wrong when the file was downloaded to your system.
> I suggest to delete `linux-2.6.31.tar.bz2` from your download directory
> and try again.
Don't forget to delete the linux-2.6.31.tar.bz2.md5sum file from the
same directory. (I think I have the extension right)
Philip
>
>
> Thanks,
>
> Paul
>
>
> [1] http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux-libc-headers/linux-libc-headers_2.6.31.bb?id=9f1368c60dcef32eb965c0f9ecb81c4adc4f49c5#n27
> [2] http://docs.openembedded.org/usermanual/usermanual.html#src_uri_variable
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2011-03-07 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAY127-W1192DA5D5640002E5C3260D8DE0@phx.gbl>
2011-03-01 14:50 ` linux-libc-headers do fetch Failed saleh usman
2011-03-06 14:49 ` Linux-libc-headers do_fetch Failed due to cheksum mismatch saleh usman
2011-03-06 15:20 ` Paul Menzel
2011-03-07 14:38 ` Philip Balister [this message]
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=4D74EDD8.8080709@balister.org \
--to=philip@balister.org \
--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.