Skip to contentSkip to conversation

Openembedded-core Digest, Vol 106, Issue 126

DISCUSSION Joseph Reynolds 1 participant 1 message Nov 18, 2019 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): mailman.25796.1574025583.1670.openembedded-core@lists.openembedded.org

#1 lore raw
Quoted 59 lines · On 11/17/19 3:19 PM, [email protected] wrote:

Message: 4 >Date: Sun, 17 Nov 2019 22:19:32 +0100 >From: Alexander Kanavin <[email protected]> >To: Joseph Reynolds <[email protected]> >Cc: OE-core <[email protected]> >Subject: Re: [OE-core] How to add build date? (was: ... basehash value > changed...) >Message-ID: > <CANNYZj8LNhF26TLHuLMPh6K40dXe8V5pgEvv8N3MAEFVy+vveg@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 <[email protected]> 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<[email protected]>
To:     www<[email protected]>,[email protected]

<[email protected]>

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.