From: Anton Mikanovich <amikan@ilbers.de>
To: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH v1 00/11] Migrate to Bitbake 2.0
Date: Tue, 21 Jun 2022 18:07:37 +0300 [thread overview]
Message-ID: <3f5211b8-891b-c26a-c027-bc2dfe26b3df@ilbers.de> (raw)
In-Reply-To: <AS4PR10MB531846F7CD5C80588AD7ABDFEDB39@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM>
21.06.2022 17:49, Schmidt, Adriaan wrote:
> Hi Anton,
>
> I like the script for migration of overrides. Did it really catch the required
> changes in image.bbclass automatically? That's impressive, as some of those
> are in Python code...
Hi Adriaan,
The script was taken from Yocto with the same imagetypes code, so it
supposed
to work with it. There are also other scripts for porting parts like
'inclusive
language' vars rename, but I think it can be done manually.
> I remember having non-deterministic metadata issues, but not exactly how I solved
> it, but it's somewhere in my previous email on bitbake2.0. Might have been the new
> BB_SIGNATURE_EXCLUDE_FLAGS in bitbake.conf. I also restructured
> the *_IGNORE_VARS there to be more aligned with OE, and may have made some other changes
> to those lists.
Thanks, will check.
> Also, in my changes to bitbake.conf I needed this to make it run at all:
> -PN = "${@bb.parse.BBHandler.vars_from_file(d.getVar('FILE', False),d)[0] or 'defaultpkgname'}"
> -PV = "${@bb.parse.BBHandler.vars_from_file(d.getVar('FILE', False),d)[1] or '1.0'}"
> -PR = "${@bb.parse.BBHandler.vars_from_file(d.getVar('FILE', False),d)[2] or 'r0'}"
> +PN = "${@bb.parse.vars_from_file(d.getVar('FILE', False),d)[0] or 'defaultpkgname'}"
> +PV = "${@bb.parse.vars_from_file(d.getVar('FILE', False),d)[1] or '1.0'}"
> +PR = "${@bb.parse.vars_from_file(d.getVar('FILE', False),d)[2] or 'r0'}"
> I'm surprised that it works for you without...
I've addressed this in p1.
> And I think we need to upgrade some more files we take from OE:
> - meta/lib/oe/*
> - meta/classes/sstate.bbclass
>
> Did you run into the "broken sudo" issue I described? That might need an upstream
> fix in bitbake.
I've tried to add [network] flag to 'apt-get' tasks, but unable to test
if it helped.
Will continue after resolving hash issue.
> Adriaan
prev parent reply other threads:[~2022-06-21 15:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 13:38 Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 01/11] meta: change deprecated parse calls Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 02/11] scripts/contrib: Add override conversion script Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 03/11] scripts/contrib: configure " Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 04/11] dpkg-base: fix conflicting variable names Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 05/11] meta-isar: set default branch names Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 06/11] meta: remove non recommended syntax Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 07/11] bitbake: Update to Bitbake 2.0.1 Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 08/11] doc: require zstd tool Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 09/11] meta: update bitbake variables Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 10/11] meta: mark network access required tasks Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 11/11] meta: update overrides syntax Anton Mikanovich
2022-06-21 14:49 ` [PATCH v1 00/11] Migrate to Bitbake 2.0 Schmidt, Adriaan
2022-06-21 15:07 ` Anton Mikanovich [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=3f5211b8-891b-c26a-c027-bc2dfe26b3df@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