On 11/17/19 3:19 PM, openembedded-core-requ...@lists.openembedded.org wrote:
>Message: 4 >Date: Sun, 17 Nov 2019 22:19:32 +0100 >From: Alexander
Kanavin <alex.kana...@gmail.com> >To: Joseph Reynolds
<j...@linux.ibm.com> >Cc: OE-core
<openembedded-core@lists.openembedded.org> >Subject: Re: [OE-core] How
to add build date? (was: ... basehash value > changed...) >Message-ID: >
<cannyzj8lnhf26tlhulmph6k40dxe8v5pgevv8n3maefvy+v...@mail.gmail.com>
>Content-Type: text/plain; charset="utf-8" > >I'd write the date into
the file at image creation, via >ROOTFS_POSTPROCESS_COMMAND. Got it,
thanks. I was unaware of ROOTFS_POSTPROCESS_COMMAND. >Having it in a
recipe means that you either force the recipe to not be a >part of
sstate cache, always rebuilding it and its dependencies (bad idea), >or
accept that the date comes from a previously built cache object, which
>means it will mismatch the actual image creation date. > >A bit of
context would help: why would you want that info in os-release? >Who
would use that information and how? I don't fully understand the use
case. I think the build date is being used as a substitute for a
software version. I've re-asked the question to the original poster in
the OpenBMC email list:
https://lists.ozlabs.org/pipermail/openbmc/2019-November/019493.html -
Joseph >Alex >On Sat, 16 Nov 2019 at 23:14, Joseph Reynolds
<j...@linux.ibm.com> wrote:
Is there a best practice for folks who want to put the build date into
their generated os-release file? I've seen this question come up at
least 3 times in my brief involvement with OE. I could perhaps add
comment to the OpenBMC os-release.bbappend file to provide the proper
guidance. I would like to hear your ideas.
- Joseph
-------- Forwarded Message --------
Subject: Re: how to solve the error that basehash value changed
from
'xxx' to 'aaaa' ?
Date: Sat, 16 Nov 2019 15:50:38 -0600
From: Joseph Reynolds<j...@linux.ibm.com>
To: www<ouyangxua...@163.com>,open...@lists.ozlabs.org
<open...@lists.ozlabs.org>
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.
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
