From: Phil Blundell <philb@gnu.org>
To: oe-core <openembedded-core@lists.openembedded.org>
Subject: libiconv checksum wrong
Date: Wed, 20 Jul 2011 10:41:49 +0100 [thread overview]
Message-ID: <1311154909.30326.51.camel@phil-desktop> (raw)
Since updating this morning I'm getting
| ERROR: Function 'File: '/home/pb/sources/libiconv-1.13.1.tar.gz' has
md5 checksum 7ab33ebd26687c744a37264a330bbe9a when
d42b97f6ef5dd0ba4469d520ed732fed was expected (from URL:
'ftp://ftp.gnu.org/gnu/libiconv/libiconv-1.13.1.tar.gz')' failed
NOTE: package libiconv-1.13.1-r0: task do_fetch: Failed
The offending commit appears to be
bd1e627bef29830f9346b4b984905fd8fcf2e716. As far as I can tell from a
quick inspection of the files, the checksum that was added for
libiconv-1.13.1.tar.gz in that commit is actually the md5sum of the
earlier version 1.11.1.
p.
next reply other threads:[~2011-07-20 9:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 9:41 Phil Blundell [this message]
2011-07-20 11:55 ` libiconv checksum wrong Frans Meulenbroeks
2011-07-20 13:30 ` Khem Raj
2011-07-20 14:26 ` Frans Meulenbroeks
2011-07-20 14:42 ` Richard Purdie
2011-07-20 16:44 ` Saul Wold
2011-07-20 21:02 ` Frans Meulenbroeks
2011-07-20 14:37 ` Richard Purdie
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=1311154909.30326.51.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-core@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