public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com, Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [FYI 0/2] Migration to bitbake 2.0
Date: Tue, 7 Jun 2022 18:46:51 +0300	[thread overview]
Message-ID: <3ef63d93-aa6c-358c-2c33-4244cc77c1bf@ilbers.de> (raw)
In-Reply-To: <20220607152531.3498370-1-adriaan.schmidt@siemens.com>

07.06.2022 18:25, Adriaan Schmidt wrote:
> Hi all,
>
> I recently spent a Friday afternoon playing with bitbake 2.0, and here are the
> findings, in patch form, without the actual updated code (which would be bitbake/*,
> meta/lib/oe/* and meta/classes/sstate.bbclass.
>
> I made it work for mc:qemuamd64-bullseye:isar-image-base, and for one of
> our downstream layers, just to get an idea of the work required.
> This post is meant as documentation, for whenever the time comes to apply the
> bitbake update...
>
> Changes required:
> - new override syntax, with ':' instead of '_'
> - some rewording (e.g. WHITELIST -> IGNORE_VARS, ABORT -> HALT)
> - new task flag "[network]", which is needed on tasks requiring network
>    access. If it is not set, networking is disabled by cloning into a new
>    namespace. The current bitbake implementation creates a new namespace for
>    network and user, with the latter breaking use of sudo. p1 would be
>    the corresponding upstream change in bitbake to make sudo work, as an alternative
>    to adding "[network] = 1" to all tasks (which I tested, and which also works).
> - SRCREV always needs to be a hash, not a branch or tag. This does not
>    actually affect Isar itself, but possibly downstream layers (we often
>    use SRCREV="v${PV}").
> - sstate internally switches from tgz to zstd compression for artifacts,
>    and from pickle to compressed json for siginfo files. This affects the
>    isar-sstate script.
>
> Adriaan

Hello Adriaan,
Thanks for the patch. I'm already working on "Bitbake update prepare" 
patchset
which will include everything needed for migration but without override 
syntax
update itself.
It will also include (already configured for Isar) convert-overrides.py 
script
for automatic downstreams update. After this patch we will have Isar and
downstreams ready for fast syntax change (I hope so).
Unfortunately this task has less priority then Isar release preparation, 
but I
will try to share something soon.


      parent reply	other threads:[~2022-06-07 15:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 15:25 Adriaan Schmidt
2022-06-07 15:25 ` [FYI 1/2] bitbake: no user namespace in disable_network Adriaan Schmidt
2022-06-07 15:25 ` [FYI 2/2] migrate Isar to bitbake 2.0 Adriaan Schmidt
2022-06-07 15:46 ` 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=3ef63d93-aa6c-358c-2c33-4244cc77c1bf@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=ibr@ilbers.de \
    --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