From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: wrong checksum for libsdl-mixer-1.2.9
Date: Sat, 21 Nov 2009 01:15:32 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911210112500.25956@localhost> (raw)
In-Reply-To: <1258782956.5424.17.camel@gnutoo-desktop>
On Sat, 21 Nov 2009, GNUtoo wrote:
> hi, I've a bad checksum for SDL_mixer-1.2.9.tar.gz
> I've tried to download it a second time and the bad checksum persist:
> NOTE: Handling BitBake files: / (7861/7861) [100 %]
> NOTE: Parsing finished. 7056 cached, 461 parsed, 344 skipped, 0 masked.
> NOTE: Resolving any missing task queue dependencies
> NOTE: Preparing runqueue
> NOTE: Executing runqueue
> NOTE: Running task 885 of 1396 (ID:
> 209, /home/embedded/oe/org.openembedded.dev/recipes/libsdl/libsdl-mixer_1.2.9.bb, do_fetch)
> NOTE: fetch http://build.shr-project.org/sources/SDL_mixer-1.2.9.tar.gz
> --2009-11-21 06:37:49--
> http://build.shr-project.org/sources/SDL_mixer-1.2.9.tar.gz
> Resolving build.shr-project.org... 78.40.125.6
> Connecting to build.shr-project.org|78.40.125.6|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2009-11-21 06:37:50 ERROR 404: Not Found.
>
> NOTE: fetch
> http://www.libsdl.org/projects/SDL_mixer/release/SDL_mixer-1.2.9.tar.gz
> --2009-11-21 06:37:50--
> http://www.libsdl.org/projects/SDL_mixer/release/SDL_mixer-1.2.9.tar.gz
> Resolving www.libsdl.org... 69.163.143.10
> Connecting to www.libsdl.org|69.163.143.10|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 2690766 (2.6M) [application/x-tar]
> Saving to: `/home/embedded/sources/SDL_mixer-1.2.9.tar.gz'
>
> 100%[====[...]=====================>] 2,690,766 746K/s in 4.5s
>
> 2009-11-21 06:38:00 (588 KB/s) -
> `/home/embedded/sources/SDL_mixer-1.2.9.tar.gz' saved [2690766/2690766]
>
> NOTE: The MD5Sums did not match. Wanted:
> 'a9eb8750e920829ff41dbe7555850156' and Got:
> '09eb4585f46d3527fe7fce8af8f9e591'
that second checksum is, in fact, the correct one for that tarball.
and the sha256sum in conf/checksums.ini also doesn't match the one for
that tarball. if that used to be correct, does that mean someone has
replaced a tarball with a different but identically-named one?
rday
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next prev parent reply other threads:[~2009-11-21 6:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 5:55 wrong checksum for libsdl-mixer-1.2.9 GNUtoo
2009-11-21 6:15 ` Robert P. J. Day [this message]
2009-11-21 14:28 ` Philip Balister
2009-11-21 17:02 ` GNUtoo
2009-11-21 17:45 ` [PATCH] " Bernhard Kaindl
2009-11-21 18:07 ` Frans Meulenbroeks
2009-11-21 18:24 ` Philip Balister
2009-11-21 18:30 ` Martin Jansa
2009-11-22 9:51 ` Frans Meulenbroeks
2009-11-22 10:30 ` Martin Jansa
2009-11-22 12:21 ` Frans Meulenbroeks
2009-11-22 12:29 ` Martin Jansa
2009-11-22 12:55 ` Frans Meulenbroeks
2009-11-22 12:02 ` Koen Kooi
2009-11-22 15:56 ` [PATCH] libsdl-mixer: delete libsdl-mixer_1.2.9.bb (as agreed upon) Bernhard Kaindl
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=alpine.LFD.2.00.0911210112500.25956@localhost \
--to=rpjday@crashcourse.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox