From: Andrei Gherzan <andrei@gherzan.ro>
To: Trevor Woerner <twoerner@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-raspberrypi] taskhash mismatch
Date: Fri, 14 Oct 2016 10:25:01 +0100 [thread overview]
Message-ID: <20161014092501.GD28288@resin> (raw)
In-Reply-To: <20161002143422.GA24664@openSUSE-i7.site>
[-- Attachment #1: Type: text/plain, Size: 2174 bytes --]
On Sun, Oct 02, 2016 at 10:34:22AM -0400, Trevor Woerner wrote:
> Hi,
>
> For the last week or so my raspberry pi builds have been failing with:
>
> ERROR: core-image-minimal-1.0-r0 do_image_rpi_sdimg: Taskhash mismatch 2920e557ac3a011d5679a52590cb664d versus a47bfc12fdfa29c58fe72cf8e0a28e91 for /z/raspi2/poky/meta/recipes-core/images/core-image-minimal.bb.do_image_rpi_sdimg
> ERROR: Taskhash mismatch 2920e557ac3a011d5679a52590cb664d versus a47bfc12fdfa29c58fe72cf8e0a28e91 for /z/raspi2/poky/meta/recipes-core/images/core-image-minimal.bb.do_image_rpi_sdimg
>
> This is with both poky and oe+bitbake, master branches all around, and fully
> up-to-date. Before sending this email I pulled yet again and re-tested just to
> confirm.
>
> Poky:
>
> Build Configuration:
> BB_VERSION = "1.31.1"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "SUSELINUX-42.1"
> TARGET_SYS = "arm-poky-linux-gnueabi"
> MACHINE = "raspberrypi"
> DISTRO = "poky"
> DISTRO_VERSION = "2.1+snapshot-20161002"
> TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"
> TARGET_FPU = "hard"
> meta
> meta-poky = "master:3a73fe0efcb7aeefcca7011bba887caad03d4d03"
> meta-raspberrypi = "master:4817e2c087097c02755d6309304878e42cf61d3c"
>
> OE + bitbake:
>
> Build Configuration:
> BB_VERSION = "1.31.1"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "SUSELINUX-42.1"
> TARGET_SYS = "arm-oe-linux-gnueabi"
> MACHINE = "raspberrypi"
> DISTRO = "nodistro"
> DISTRO_VERSION = "nodistro.0"
> TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"
> TARGET_FPU = "hard"
> meta = "master:21cc2a3f63ea260dbf6b50e2fd4dd50cacdd9935"
> meta-raspberrypi = "master:4817e2c087097c02755d6309304878e42cf61d3c"
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
I know I'm kinda late to the party but just wanted to say that this was
fixed in master. Cheers!
--
Andrei Gherzan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 817 bytes --]
next prev parent reply other threads:[~2016-10-14 9:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 14:34 [meta-raspberrypi] taskhash mismatch Trevor Woerner
2016-10-02 23:51 ` Khem Raj
2016-10-03 16:31 ` Karim ATIKI
2016-10-03 18:45 ` Karim ATIKI
2016-10-03 18:48 ` Trevor Woerner
2016-10-03 20:39 ` Trevor Woerner
2016-10-03 21:35 ` Khem Raj
2016-10-04 14:18 ` Trevor Woerner
2016-10-04 5:26 ` Gary Thomas
2016-10-14 9:25 ` Andrei Gherzan [this message]
2016-10-14 12:50 ` Trevor Woerner
2016-10-14 12:56 ` Andrei Gherzan
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=20161014092501.GD28288@resin \
--to=andrei@gherzan.ro \
--cc=twoerner@gmail.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.