All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Reynolds <jrey@linux.ibm.com>
To: www <ouyangxuan10@163.com>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: how to solve the error that basehash value changed from 'xxx' to 'aaaa' ?
Date: Sat, 16 Nov 2019 15:50:38 -0600	[thread overview]
Message-ID: <adf92df5-06d4-ea38-ad9f-55dde92148b2@linux.ibm.com> (raw)
In-Reply-To: <275367c1.6307.16e63b2e1cf.Coremail.ouyangxuan10@163.com>

Byron,

What modification did you put into the os-release recipe?  It would help 
us help you if you put that in your email.


Are you adding the build date to the generated os-release file?  If so, 
be aware that might cause the issues with the shared state cache you are 
experiencing.  Also be aware this practice wrecks reproducible builds.

A better way to get the same effect might be to create a git tag with 
the information you want to appear in the generated os-release file.  
When you buld with this tag is then picked up by the OpenBMC 
meta-phosphor os-release.bbappend (via `git describe`) and included in 
the genersted os-release file as the BUILD_ID.  See:
https://github.com/ibm-openbmc/openbmc/blob/d1c59b7a36c10c18838c07af10b18080174cd61d/meta-phosphor/recipes-core/os-release/os-release.bbappend
(But I have not tried that.)

A way to work around the hash change is to add a line to your recipe 
like: PR[vardepsxeclude]="DATETIME"
As suggested by: 
https://forums.openpli.org/topic/41447-how-to-get-rid-of-taskhash-mismatch/


My apologies for top posting -- my email reader was not quoting the 
message properly, so I cut/pasted it below.

- Joseph


On 11/13/19 1:38 AM, www wrote:

When I modify the os-release file in my yocto project, it appear some 
error, and how can I solve it ? Who can give me some help or advice? 
Thank you!
I execute the recommended command on the console and it didn't work.

ERROR: os-release-1.0-r0 do_compile: Taskhash mismatch 
ce133f0458608e03aa55224df28156e523e54903115efbbcd62946f84a867201 versus 
7269881f0eb1759ed420a2db4c04fb477cd8c1288bc5f82df5c8161bb926ea1f 
for  /home/temp/xxx/wsp/obmc-source/entity_xxx/meta/recipes-core/os-release/os-release.bb.do_compile
ERROR: Taskhash mismatch 
ce133f0458608e03aa55224df28156e523e54903115efbbcd62946f84a867201 versus 
7269881f0eb1759ed420a2db4c04fb477cd8c1288bc5f82df5c8161bb926ea1f 
for /home/temp/xxx/wsp/obmc-source/entity_xxx/meta/recipes-core/os-release/os-release.bb.do_compile
ERROR: When reparsing 
/home/temp/xxx/wsp/obmc-source/entity_xxx/meta/recipes-core/os-release/os-release.bb.do_compile, the 
basehash value changed from 
99a42a1a3b1a151de604267b159558ecaf1031a3bec8917df132c81302e729a5 to 
4f3288a8763e2e1af78e4b3cdd9c0c0ccb3b0d5c78a3073c188b22200df2a9b0. The 
metadata is not deterministic and this needs to be fixed.
ERROR: The following commands may help:
ERROR: $ bitbake os-release -cdo_compile -Snone
ERROR: Then:
ERROR: $ bitbake os-release -cdo_compile -Sprintdiff

ERROR: When 
reparsing /home/temp/xxx/wsp/obmc-source/entity_xxx/meta/recipes-core/os-release/os-release.bb.do_compile, the 
basehash value changed from 
99a42a1a3b1a151de604267b159558ecaf1031a3bec8917df132c81302e729a5 to 
47c30012daa6aa77be09a93fe21e66995361ef26b4487111005617db8cb4de59. The 
metadata is not deterministic and this needs to be fixed.
ERROR: The following commands may help:
ERROR: $ bitbake os-release -cdo_compile -Snone
ERROR: Then:
ERROR: $ bitbake os-release -cdo_compile -Sprintdiff

thanks,
Byron

  reply	other threads:[~2019-11-16 21:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13  7:38 how to solve the error that basehash value changed from 'xxx' to 'aaaa' ? www
2019-11-16 21:50 ` Joseph Reynolds [this message]
2019-11-16 21:56   ` How to add build date? (was: ... basehash value changed...) Joseph Reynolds
2019-11-17 21:19     ` Alexander Kanavin
2019-11-18  8:58       ` Mikko.Rapeli
2019-11-20 16:28       ` How to add build date? Joseph Reynolds
2019-11-18  9:53     ` Ross Burton
2019-11-18 16:07       ` Joseph Reynolds
2019-11-18  1:52   ` Re:Re: how to solve the error that basehash value changed from 'xxx' to 'aaaa' ? www
2019-11-18 16:02     ` Add build date to image (was: error basehash value changed) Joseph Reynolds
2019-11-19  1:23       ` www
2019-11-20 16:38         ` Add build date to image Joseph Reynolds
2019-11-20 18:08           ` Vijay Khemka
2019-11-21  1:02             ` www
2019-11-22  9:06               ` rgrs
2019-11-22  9:17                 ` www

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=adf92df5-06d4-ea38-ad9f-55dde92148b2@linux.ibm.com \
    --to=jrey@linux.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=ouyangxuan10@163.com \
    /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.