On 07/20/2011 04:55 AM, Frans Meulenbroeks wrote:
2011/7/20 Phil Blundell<[email protected]>
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
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core