From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: patch for compcache recipe
Date: Fri, 14 Aug 2009 16:39:24 +0200 [thread overview]
Message-ID: <h63suv$dje$1@ger.gmane.org> (raw)
In-Reply-To: <4A850430.6060809@linuxbj.com>
Ming Chow 周明 wrote:
> BTW. I had experienced some checksum mismatch before. A few packages
> which just work can not pass checksum matching. I guess it may be caused
> by hosting or tarball changing without notice. For I am not very clear
> how the global checksum.ini is maintained. I lazily set
> OE_ALLOW_INSECURE_DOWNLOADS.
Take a look at
http://wiki.openembedded.net/index.php/Dealing_with_checksum_mismatch
Let us know about the packages failing the checksum test so we can fix
things.
next prev parent reply other threads:[~2009-08-14 14:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 19:10 patch for compcache recipe Ming Chow 周明
2009-08-14 2:06 ` Holger Hans Peter Freyther
2009-08-14 6:29 ` Ming Chow 周明
2009-08-14 14:39 ` Rolf Leggewie [this message]
2009-08-14 14:55 ` Ming Chow 周明
2009-08-14 15:05 ` Ming Chow 周明
2009-08-14 15:19 ` Koen Kooi
2009-08-14 15:33 ` Rolf Leggewie
2009-08-19 16:32 ` Ming Chow 周明
2009-08-19 16:50 ` Koen Kooi
2009-08-20 1:36 ` Ming Chow 周明
2009-08-20 2:09 ` Holger Hans Peter Freyther
2009-08-20 17:20 ` Ming Chow 周明
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='h63suv$dje$1@ger.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--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