From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: libiconv checksum wrong
Date: Wed, 20 Jul 2011 06:30:34 -0700 [thread overview]
Message-ID: <4E26D87A.5020808@gmail.com> (raw)
In-Reply-To: <CACW_hTYXboQ+Zzkt3PXBuA_=uMDVovTgt7g7BNJSxbCdjuoS2A@mail.gmail.com>
On 07/20/2011 04:55 AM, Frans Meulenbroeks wrote:
> 2011/7/20 Phil Blundell<philb@gnu.org>
>
>> 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.
>>
>> This seems to indicate that the added 1.13.1 recipe has not been build by
> neither the submitter nor the committer (let alone tested by someone).
> is that the kind of quality we want to achieve in oe-core ?
>
there is already patch sent to fix it.
http://patches.openembedded.org/patch/7933/
libiconv is not default provider of virtual/libiconv on eglibc/glibc
based systems and sometimes that can trip you over. It happens and as
long as we find it and fix it quickly I don't see a problem. Do you ?
IMO we should not get so pedantic that people start getting scared of
making changes
> Frans.
>
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-07-20 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 9:41 libiconv checksum wrong Phil Blundell
2011-07-20 11:55 ` Frans Meulenbroeks
2011-07-20 13:30 ` Khem Raj [this message]
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=4E26D87A.5020808@gmail.com \
--to=raj.khem@gmail.com \
--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 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.