From: "Denys Dmytriyenko" <denis@denix.org>
To: Mauro Ziliani <mauro@faresoftware.it>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] Strange error
Date: Thu, 11 Jun 2020 18:56:17 -0400 [thread overview]
Message-ID: <20200611225617.GC17660@denix.org> (raw)
In-Reply-To: <bfff9877-1a93-ced9-54d7-a3be42ac30c9@faresoftware.it>
You know that rootfs already creates /etc/version file with $DATETIME?
Either way, you can fix it like this:
mark_os_buildtime[vardepsexclude] = "DATETIME"
--
Denys
On Thu, Jun 11, 2020 at 09:56:42AM +0200, Mauro Ziliani wrote:
> In the image recipe i write ${DATETIME} in
> ${IMAGE_ROOTFS}/etc/buildtime by a function.
>
> This is the part of recipe
>
>
> ROOTFS_POSTPROCESS_COMMAND_append = " \
> mark_os_buildtime; \
>
> "
>
>
> mark_os_buildtime() {
> echo "${PV} ${DATETIME}" > ${IMAGE_ROOTFS}/etc/buildtime
>
> }
>
>
>
> Il 10/06/20 20:44, Josef Holzmayr ha scritto:
> >Howdy!
> >
> >Am 10.06.2020 um 19:48 schrieb Mauro Ziliani:
> >>Hi all.
> >>
> >>This error
> >>
> >>NOTE: Executing RunQueue Tasks
> >>ERROR: When reparsing <recipe_of_image>.do_rootfs, the basehash
> >>value changed from 7419bfc242fa2eee9ce87b18ebf40d25 to
> >>5b2654046d2ac406f3484b3286de0acd. The metadata is not
> >>deterministic and this needs to be fixed.
> >>
> >>
> >>Why?
> >
> >Maybe some script / part of the recipe is dependent on the
> >execution time or evaluation order? The error basically tells you
> >that your build is not reproducible across runs.
> >
> >Greetz
> >
> >
> >
>
prev parent reply other threads:[~2020-06-11 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 17:48 Strange error Mauro Ziliani
2020-06-10 17:50 ` [yocto] " Rudolf J Streif
2020-06-11 7:50 ` Mauro Ziliani
2020-06-10 18:44 ` Josef Holzmayr
2020-06-11 7:56 ` Mauro Ziliani
2020-06-11 22:56 ` Denys Dmytriyenko [this message]
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=20200611225617.GC17660@denix.org \
--to=denis@denix.org \
--cc=mauro@faresoftware.it \
--cc=yocto@lists.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.