From: Ed Nelson <enelson1000@comcast.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Creating the CheckSum parser failed
Date: Thu, 01 Oct 2009 07:59:38 -0700 [thread overview]
Message-ID: <4AC4C3DA.4010904@comcast.net> (raw)
In-Reply-To: <200910010700.39010.holger+oe@freyther.de>
Holger Hans Peter Freyther wrote:
> On Thursday 01 October 2009 06:47:23 ed wrote:
>
>> What am I missing that keeps causing this message to be printed out in
>> the log.
>>
>> NOTE: Running task 10 of 2678 (ID:
>> 815,
>> /home/ed/mini2440/OE/mini2440/recipes/stage-manager/stagemanager-native_0.
>> 0.1.bb, do_setscene) NOTE: Running task 11 of 2678 (ID:
>> 816,
>> /home/ed/mini2440/OE/mini2440/recipes/stage-manager/stagemanager-native_0.
>> 0.1.bb, do_fetch) NOTE: Creating the CheckSum parser failed
>>
>
> Wow that is a crappy message that I created (I always bitch about bad error
> messages myself). This message is generated in classes/base.bbclass and
> could you try the following patch?
>
>
>
> diff --git a/classes/base.bbclass b/classes/base.bbclass
> index d29ba4b..89ee917 100644
> --- a/classes/base.bbclass
> +++ b/classes/base.bbclass
> @@ -661,7 +661,7 @@ python base_do_fetch() {
> bb.note("No conf/checksums.ini found, not checking checksums")
> return
> except:
> - bb.note("Creating the CheckSum parser failed")
> + bb.note("Creating the CheckSum parser failed: %s:%s" % (sys.exc_info()[0], sys.exc_info()[1]))
> return
>
> pv = bb.data.getVar('PV', d, True)
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>
Thanks
That did the trick.
It reported parsing errors in checksum.ini file.
line 27362 '====\n'
line 27373 '====\n'
etc
Removed them from file and now no more errors.
Thanks again.
prev parent reply other threads:[~2009-10-01 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 4:47 Creating the CheckSum parser failed ed
2009-10-01 5:00 ` Holger Hans Peter Freyther
2009-10-01 14:59 ` Ed Nelson [this message]
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=4AC4C3DA.4010904@comcast.net \
--to=enelson1000@comcast.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox