From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: what to do with wrong checksum
Date: Sat, 07 Nov 2009 15:41:29 +0100 [thread overview]
Message-ID: <hd40up$sbn$1@ger.gmane.org> (raw)
In-Reply-To: <ac9c93b10911061238p366f65edqeff04b25c872015f@mail.gmail.com>
On 06-11-09 21:38, 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?
From my previous run in with twig:
checksums.ini: update entry for libxml-twig-perl
The Twig people are idiots because they keep replacing the tarball, a
snippet from diffing the two:
diff -Nurd XML-Twig-3.33.old/Changes XML-Twig-3.33.new/Changes
--- XML-Twig-3.33.old/Changes 2009-05-18 14:13:23.000000000 +0200
+++ XML-Twig-3.33.new/Changes 2009-10-11 09:52:38.000000000 +0200
@@ -12,7 +12,11 @@
added: better error message if find_nodes or get_xpath are called instead
of findnodes when using XML::Twig::XPath (suggested by Zed Pobre)
added: indented_close_tag pretty_print option (suggested by H.Merijn
Brand)
-
+added: RT #49692 xml_split test on win 32 systems. Patch sent through RT
+ http://rt.cpan.org/Ticket/Display.html?id=49692
+fix: RT #48616 handler condition of foo/* crashed the module
+ reported by Osfameron
+ http://rt.cpan.org/Public/Bug/Display.html?id=48616
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
@@ -46,7 +50,9 @@
Viebrock (fix is to explicitely return null from the character
handler,
instead of the text already parsed... a few hundred thousand times)
http://rt.cpan.org/Ticket/Display.html?id=35672
-
+fix: RT #47257, minor doc bug, spotted by David Steinbrunner
+ http://rt.cpan.org/Ticket/Display.html?id=47257
+improved: speed, somewhat
next prev parent reply other threads:[~2009-11-07 14:46 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
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 [this message]
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='hd40up$sbn$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.