All of lore.kernel.org
 help / color / mirror / Atom feed
From: JC <jc@vtkloud.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: broken meta-baryon?
Date: Sat, 14 Sep 2013 00:34:27 +0200	[thread overview]
Message-ID: <523392F3.4000907@vtkloud.com> (raw)

Hi

I was trying to give a look at Baryon, but I can't bake it. It seems 
there's a package whose sources have vanised :

ERROR: Fetcher failure for URL: 
'http://code.entropywave.com/download/orc/orc-0.4.5.tar.gz;name=orc'. 
Checksum mismatch!
File: '/media/yocto/downloads/orc-0.4.5.tar.gz' has md5 checksum 
5b6d74f1453e20c09d6a20d909779ad7 when e26e59428b13ec251916f34bea96eee5 
was expected
File: '/media/yocto/downloads/orc-0.4.5.tar.gz' has sha256 checksum 
6f0e2620a2a986c8329612f1db92f273949a58480290ace72eca7f1dba1a5c98 when 
4e04953643cd8e67f8d9796da9547a606954e3944e42e7ce5a099440fd8e729e was 
expected
If this change is expected (e.g. you have upgraded to a new version 
without updating the checksums) then you can use these lines within the 
recipe:
SRC_URI[orc.md5sum] = "5b6d74f1453e20c09d6a20d909779ad7"
SRC_URI[orc.sha256sum] = 
"6f0e2620a2a986c8329612f1db92f273949a58480290ace72eca7f1dba1a5c98"
Otherwise you should retry the download and/or check with upstream to 
determine if the file has become corrupted or otherwise unexpectedly 
modified.


Is the Baryon maintainer aware of this or is this just me ?

Regards
Jay



             reply	other threads:[~2013-09-13 22:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13 22:34 JC [this message]
2013-09-16 15:57 ` broken meta-baryon? Paul Eggleton
2013-09-16 16:05   ` JC

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=523392F3.4000907@vtkloud.com \
    --to=jc@vtkloud.com \
    --cc=yocto@yoctoproject.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.