From: Gary Thomas <gary@mlbassoc.com>
To: "openembedded-core@openembedded.org"
<openembedded-core@openembedded.org>
Subject: Interesting bitbake/fetcher error
Date: Thu, 15 Mar 2012 06:27:36 -0600 [thread overview]
Message-ID: <4F61E038.9020700@mlbassoc.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
I have two recipes for midori (attached). When I try to build
the latest version, I get this error:
ERROR: Fetcher failure for URL: 'http://archive.xfce.org/src/apps/midori/0.4/midori-0.4.4.tar.bz2;name=midori'. Checksum mismatch!
File: '/local/my_test/downloads/midori-0.4.4.tar.bz2' has md5 checksum a6578ebfd237c0f22cce49113b95f70c when 900037557b82818d79d2dd1c5a7d7fd2 was expected
File: '/local/my_test/downloads/midori-0.4.4.tar.bz2' has sha256 checksum fadd43f76c1c9f6a16483e60a804e58fb6817c6a595b1acdd59bcbdd7b35bca2 when
fca4a0eab03358f20d7700069dbf2faaf8fa5c11aaad97f4208aea608f4bed9f was expected
It looks like having qualified checksums doesn't work quite right? It's obviously
comparing the sums from the 0.4.3 recipe even though 0.4.4 is being executed.
midori_0.4.3
SRC_URI[midori.md5sum] = "900037557b82818d79d2dd1c5a7d7fd2"
SRC_URI[midori.sha256sum] = "fca4a0eab03358f20d7700069dbf2faaf8fa5c11aaad97f4208aea608f4bed9f"
Midori_0.4.4
SRC_URI[midori.md5sum] = "a6578ebfd237c0f22cce49113b95f70c"
SRC_URI[midori.sha256sum] = "fadd43f76c1c9f6a16483e60a804e58fb6817c6a595b1acdd59bcbdd7b35bca2"
Interestingly, if I comment out those lines in the 0.4.3 recipe,
but still leave it in my tree, the fetcher works.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
[-- Attachment #2: midori_0.4.3.bb --]
[-- Type: text/plain, Size: 384 bytes --]
require midori.inc
PR = "r1"
SRC_URI = "http://archive.xfce.org/src/apps/midori/0.4/midori-${PV}.tar.bz2;name=midori \
file://waf \
"
#SRC_URI[midori.md5sum] = "900037557b82818d79d2dd1c5a7d7fd2"
#SRC_URI[midori.sha256sum] = "fca4a0eab03358f20d7700069dbf2faaf8fa5c11aaad97f4208aea608f4bed9f"
do_configure_prepend() {
cp -f ${WORKDIR}/waf ${S}/
}
[-- Attachment #3: midori_0.4.4.bb --]
[-- Type: text/plain, Size: 305 bytes --]
require midori.inc
PARALLEL_MAKE = ""
SRC_URI = "http://archive.xfce.org/src/apps/midori/0.4/midori-${PV}.tar.bz2;name=midori \
"
SRC_URI[midori.md5sum] = "a6578ebfd237c0f22cce49113b95f70c"
SRC_URI[midori.sha256sum] = "fadd43f76c1c9f6a16483e60a804e58fb6817c6a595b1acdd59bcbdd7b35bca2"
next reply other threads:[~2012-03-15 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 12:27 Gary Thomas [this message]
2012-03-15 12:47 ` Interesting bitbake/fetcher error Gary Thomas
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=4F61E038.9020700@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-core@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