All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: what to do with wrong checksum
Date: Sat, 7 Nov 2009 10:06:57 +0100	[thread overview]
Message-ID: <ac9c93b10911070106n587495a5qaf3cfc9288df7e8@mail.gmail.com> (raw)
In-Reply-To: <200911070406.18094.holger+oe@freyther.de>

2009/11/7 Holger Hans Peter Freyther <holger+oe@freyther.de>:
> On Friday 06 November 2009 21:38:40 Frans Meulenbroeks wrote:
>> While trying to build xmltv I got this:
>>
>> NOTE: The MD5Sums did not match. Wanted:
>> '495fd8c320f67a0c8e0b90ccb060f0ea' and Got:
>> '68d9a93d507bbf917e1f3ad294fd5727'
>> NOTE: Task failed: Checksum of
>> 'http://xmltwig.com/xmltwig/XML-Twig-3.33.tar.gz' failed
>>
>> How should I handle this. Of course I can change the checksum, but i
>> don't think that is the intention :-)
>> Is there a version somewhere cached that has the old checksum (so I
>> can compare).
>> Or how else should I handle this?
>
>
> Check the angstrom mirror or sources.oe.org and download that version
> and then diff it.

Hm. Did that.
Apparently version control is not very strong for Twig.
The diff for the changes file:

diff -r old/XML-Twig-3.33/Changes new/XML-Twig-3.33/Changes
13a14
> added: indented_close_tag pretty_print option (suggested by H.Merijn Brand)
14a16,23
> fix:  xml_grep bug: warning when --count is used and no match is found
>       https://rt.cpan.org/Ticket/Display.html?id=33269
>       found by Hermann Peifer
> fix:  xml_split bug when using an XML declaration and a utf8 encoding. Spotted
>       by Chris Price.
> fix:  xml_pp bug, pod2text command to display help was not properly quoted.
>       Spotted by Chris Price.
> fix:  failing tests when LWP::UserAgent is not available

Reluctantly updated checksums.ini

Frans



  parent reply	other threads:[~2009-11-07  9:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-06 20:38 what to do with wrong checksum Frans Meulenbroeks
2009-11-07  3:06 ` Holger Hans Peter Freyther
2009-11-07  8:45   ` Philip Balister
2009-11-07  9:06   ` Frans Meulenbroeks [this message]
2009-11-07  9:10     ` Holger Hans Peter Freyther
2009-11-07  9:39       ` Frans Meulenbroeks
2009-11-07 13:23     ` Mike Westerhof
2009-11-07 13:50       ` Holger Hans Peter Freyther
2009-11-07 14:42       ` Koen Kooi
2009-11-07 16:38         ` Otavio Salvador
2009-11-07 18:00           ` Frans Meulenbroeks
2009-11-07 19:01             ` Otavio Salvador
2009-11-07 20:14               ` Frans Meulenbroeks
2009-11-07 14:41 ` Koen Kooi
2009-11-07 22:02 ` Koen Kooi
2009-11-07 22:11   ` Otavio Salvador
2009-11-08 12:23   ` Michael 'Mickey' Lauer
2009-11-08 13:19     ` Koen Kooi
2009-11-08 14:08       ` Frans Meulenbroeks
2009-11-08 14:20         ` Koen Kooi
2009-11-08 14:43           ` Frans Meulenbroeks
2009-11-08 14:59           ` Otavio Salvador
2009-11-08 14:55         ` Otavio Salvador
2009-11-08 15:40           ` Koen Kooi
2009-11-08 21:31             ` Graham Gower
2009-11-08 22:26               ` Przemyslaw Wesolek
2009-11-08 14:09       ` Philip Balister

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=ac9c93b10911070106n587495a5qaf3cfc9288df7e8@mail.gmail.com \
    --to=fransmeulenbroeks@gmail.com \
    --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.