From: Anton Mikanovich <amikan@ilbers.de>
To: Adriaan Schmidt <adriaan.schmidt@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v4 09/21] bitbake.conf: align hash vars with openembedded
Date: Fri, 5 Aug 2022 16:21:04 +0300 [thread overview]
Message-ID: <7caac7a3-2b51-f1d9-e5ea-3bdc74d868df@ilbers.de> (raw)
In-Reply-To: <20220805131035.22844-10-amikan@ilbers.de>
05.08.2022 16:10, Anton Mikanovich wrote:
> Restructure and update hash-related variables to be compatible with
> current Bitbake/Openembedded versions.
>
> Based on OE 4.0.1 commit cb8647c08959abb1d6b7c2b3a34b4b415f66d7ee
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
Hello Adriaan,
Can you please check this patch for signature calculation issues?
next prev parent reply other threads:[~2022-08-05 13:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 13:10 [PATCH v4 00/21] Migrate to Bitbake 2.0 Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 01/21] meta: change deprecated parse calls Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 02/21] scripts/contrib: Add override conversion script Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 03/21] scripts/contrib: configure " Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 04/21] meta-isar: set default branch names Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 05/21] meta: remove non recommended syntax Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 06/21] bitbake: Update to Bitbake 2.0.1 Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 07/21] doc: require zstd tool Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 08/21] meta: update bitbake variables Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 09/21] bitbake.conf: align hash vars with openembedded Anton Mikanovich
2022-08-05 13:21 ` Anton Mikanovich [this message]
2022-08-08 6:40 ` Schmidt, Adriaan
2022-08-05 13:10 ` [PATCH v4 10/21] meta: mark network and sudo tasks Anton Mikanovich
2022-08-05 13:29 ` Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 11/21] meta: update overrides syntax Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 12/21] sstate: update bbclass Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 13/21] bitbake.conf: declare default XZ and ZSTD options Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 14/21] Revert "devshell: Use different termination test to avoid warnings" Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 15/21] meta: align with OE-core libraries update Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 16/21] Revert "Revert "devshell: Use different termination test to avoid warnings"" Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 17/21] CI: Adopt tests to syntax change Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 18/21] isar-sstate: adopt sstate maintenance script Anton Mikanovich
2022-08-08 6:56 ` Schmidt, Adriaan
2022-08-05 13:10 ` [PATCH v4 19/21] Revert "bitbake: Make 3.6.0 the minimum python version" Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 20/21] Revert "utils/ply: Change md5 usages to work on FIPS enabled hosts" Anton Mikanovich
2022-08-05 13:10 ` [PATCH v4 21/21] RECIPE-API-CHANGELOG: Add tips after bitbake version update Anton Mikanovich
2022-08-10 8:01 ` [PATCH v4 00/21] Migrate to Bitbake 2.0 Henning Schild
2022-08-10 8:42 ` Anton Mikanovich
2022-08-10 15:54 ` Henning Schild
2022-08-10 16:20 ` Henning Schild
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=7caac7a3-2b51-f1d9-e5ea-3bdc74d868df@ilbers.de \
--to=amikan@ilbers.de \
--cc=adriaan.schmidt@siemens.com \
--cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox