From: Anton Mikanovich <amikan@ilbers.de>
To: Florian Bezdeka <florian.bezdeka@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH v5 00/21] Migrate to Bitbake 2.0
Date: Mon, 5 Dec 2022 14:57:34 +0300 [thread overview]
Message-ID: <e189be3d-01f6-8db0-ca89-1f920b530f5b@ilbers.de> (raw)
In-Reply-To: <d7e3288ae79416c889b4287ecc0373dc21fbfe7f.camel@siemens.com>
05.12.2022 14:34, Florian Bezdeka wrote:
> On Fri, 2022-12-02 at 17:36 +0300, Anton Mikanovich wrote:
>> This patchset moves Isar to use Bitbake 2.0 branch.
>>
>> scripts/contrib/convert-overrides.py is the script for overrides update and it
>> needs some testing on downstream layers. Usage:
>> $ ./scripts/contrib/convert-overrides.py meta-customlayer
>>
>> Changes since v4:
>> - Rebase on next
>> - Use Bitbake 2.0.5 / Yocto 4.0.5
>> - Fix hash exclude variables
>> - Add try/catch into sstate maintenance script
>> - Fix overrides conversion script chmod
>> - Fix clean task
>> - Some commits reorder and rewording
>>
> Something seems odd around patch 14 and 16. Something is reverted in 14
> and re-reverted in 16. No?
>
> Best regards,
> Florian
Hello Florian,
Yes. I've reverted Isar-related changes of meta/lib/oe/terminal.py in
p14 and
move them back in p16 to keep changes history of everything placed on top of
original OE files. This is not an issue.
next prev parent reply other threads:[~2022-12-05 11:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 14:36 Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 01/21] meta: change deprecated parse calls Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 02/21] scripts/contrib: Add override conversion script Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 03/21] scripts/contrib: configure " Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 04/21] meta-isar: set default branch names Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 05/21] meta: remove non recommended syntax Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 06/21] bitbake: Update to Bitbake 2.0.5 Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 07/21] doc: require zstd tool Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 08/21] meta: update bitbake variables Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 09/21] bitbake.conf: align hash vars with openembedded Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 10/21] meta: mark network and sudo tasks Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 11/21] meta: update overrides syntax Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 12/21] sstate: update bbclass Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 13/21] bitbake.conf: declare default XZ and ZSTD options Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 14/21] Revert "devshell: Use different termination test to avoid warnings" Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 15/21] meta: align with OE-core libraries update Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 16/21] Revert "Revert "devshell: Use different termination test to avoid warnings"" Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 17/21] CI: Adopt tests to syntax change Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 18/21] isar-sstate: adopt sstate maintenance script Anton Mikanovich
2022-12-03 4:57 ` Moessbauer, Felix
2022-12-03 5:29 ` Schmidt, Adriaan
2022-12-06 8:57 ` Anton Mikanovich
2022-12-06 9:36 ` Moessbauer, Felix
2022-12-02 14:36 ` [PATCH v5 19/21] RECIPE-API-CHANGELOG: Add tips after bitbake version update Anton Mikanovich
2022-12-02 14:37 ` [PATCH v5 20/21] Revert "bitbake: Make 3.6.0 the minimum python version" Anton Mikanovich
2022-12-02 14:37 ` [PATCH v5 21/21] Revert "utils/ply: Change md5 usages to work on FIPS enabled hosts" Anton Mikanovich
2022-12-02 14:45 ` [PATCH v5 00/21] Migrate to Bitbake 2.0 Anton Mikanovich
2022-12-05 11:34 ` Florian Bezdeka
2022-12-05 11:57 ` Anton Mikanovich [this message]
2022-12-05 11:52 ` Moessbauer, Felix
2022-12-05 12:31 ` Anton Mikanovich
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=e189be3d-01f6-8db0-ca89-1f920b530f5b@ilbers.de \
--to=amikan@ilbers.de \
--cc=florian.bezdeka@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