All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Chen Qi <Qi.Chen@windriver.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] populate_sdk_ext: record METADATA_REVISION
Date: Fri, 05 Mar 2021 23:29:16 +0000	[thread overview]
Message-ID: <47f42aa6bef23d8c98ea9cf2a8029f6900dd7d61.camel@linuxfoundation.org> (raw)
In-Reply-To: <20210305101040.822-1-Qi.Chen@windriver.com>

On Fri, 2021-03-05 at 18:10 +0800, Chen Qi wrote:
> As we delete the .git/ directory, it's impossible to get METADATA_REVISION
> inside eSDK. Because of this, we meet the following warning when installing eSDK.
> 
>   WARNING: The base-files:do_install sig is computed to be 16b9d96148d45de183cc94667aae016ec7d102d48255456381e718cd4bbd0aa0, \
>   but the sig is locked to 6eb0dcaed504282becee94662481d79264db920dee1f7deda18230133fff8f36 in SIGGEN_LOCKEDSIGS_t-qemux86-64
> 
> So we record METADATA_REVISION in eSDK generation time to fix this problem.
> 
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
>  meta/classes/populate_sdk_ext.bbclass | 3 +++
>  1 file changed, 3 insertions(+)

I have to wonder why base-files is depending on the metadata-revision? That
implies that base-files and hence anything that depends upon it would rebuild
each time you update to a new revision. Is that really what you want?

Cheers,

Richard




  reply	other threads:[~2021-03-05 23:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 10:10 [OE-core][PATCH] populate_sdk_ext: record METADATA_REVISION Chen Qi
2021-03-05 23:29 ` Richard Purdie [this message]
2021-03-08  2:30   ` Chen Qi
     [not found]   ` <166A3C91F1FD80D0.3944@lists.openembedded.org>
2021-03-08  6:09     ` Chen Qi
     [not found]     ` <166A488578ED5898.3944@lists.openembedded.org>
2021-03-10  8:31       ` Chen Qi
     [not found]       ` <166AED6BFC056C10.17015@lists.openembedded.org>
2021-03-10  9:11         ` Chen Qi
2021-03-10  9:11           ` Richard Purdie

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=47f42aa6bef23d8c98ea9cf2a8029f6900dd7d61.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Qi.Chen@windriver.com \
    --cc=openembedded-core@lists.openembedded.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.