From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7106519686718685184 X-Received: by 2002:a05:6214:c4b:b0:46a:66a2:d72a with SMTP id r11-20020a0562140c4b00b0046a66a2d72amr13760118qvj.21.1654616815827; Tue, 07 Jun 2022 08:46:55 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:620a:24d1:b0:6a6:aedc:4639 with SMTP id m17-20020a05620a24d100b006a6aedc4639ls3291240qkn.0.gmail; Tue, 07 Jun 2022 08:46:55 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzckciMD9tw7HThcSQT3Je+4p0t+6CiVtR1NyyRVJSaj0AB22bzRV4pyQTn0f03VEaz1d+y X-Received: by 2002:a05:620a:288d:b0:6a2:ee69:5ce8 with SMTP id j13-20020a05620a288d00b006a2ee695ce8mr19428502qkp.233.1654616815321; Tue, 07 Jun 2022 08:46:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1654616815; cv=none; d=google.com; s=arc-20160816; b=o6hS87OiHUM6L5VmAOHz2rW5g+nXfVvQdurCD7kNVe9LK8+alkid/7i9sW25ZrTNhS mFZQx244YYXw2jmmFaMncSyXLxUfeFP3mKJXi4rhIkqF+FWAg3bFZnsUKgaRSik54zGH Q9kkkUyPIcNvnQqr81xiH6XXAlbT6VZzHPNTA9dfqXFsMOxIdkMzYXSNeTCZ1dijvv45 7juX+t+fc69jTUIPlA0qEoel7f8UZjD+MFzgsLr7njDEeFBvcKMaPckAyhYFkMgqfXbD ICnG71PT6q8kcO23XZIw4f5B8REGJh9Dw7ZbV8mEqoT93KisbdRsNgzNAoSM4LU+vK1J myrA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id; bh=8vRQ8VfHGj20oyoX5JL+kPrIGO4iFNzToZjuZoQ16aU=; b=ntPfp+aRloBai+obdtcart/D1LbsUvEOiERNvJPSWOsgquErFshx7ibagxgIQiebln ns2vIyy+S0z287h2qPihdWg8D0C7/stBEXPn/pqK6PKbb27J6Yqz2Z5uPD+FS8YpYctr X8oU7HBtBGPjIdmZqfiTKyeOgQLEWrBjiZU669IEFdERK7j9Z3F41khylyiqLg/xOV8Q UPVfN92NGwYFRsRJ5GvgvO749O6ZyAYs3yrUIFgu9D+7u19BcIURXQjXemIGsW8BPwIr /3jBNhLr3ReWeu4/3j+3Rp95Y3/s5lQ//Tee8iDfuFez65vmRnNjIOkPvFcw+vBLKiDM wSqg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of amikan@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=amikan@ilbers.de Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id b17-20020a05620a0f9100b006a39daf3540si1152025qkn.7.2022.06.07.08.46.54 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Tue, 07 Jun 2022 08:46:55 -0700 (PDT) Received-SPF: pass (google.com: domain of amikan@ilbers.de designates 85.214.156.166 as permitted sender) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of amikan@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=amikan@ilbers.de Received: from [127.0.0.1] (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8+deb9u1) with ESMTPSA id 257FkppW032125 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 7 Jun 2022 17:46:52 +0200 Message-ID: <3ef63d93-aa6c-358c-2c33-4244cc77c1bf@ilbers.de> Date: Tue, 7 Jun 2022 18:46:51 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Subject: Re: [FYI 0/2] Migration to bitbake 2.0 Content-Language: en-US To: isar-users@googlegroups.com, Baurzhan Ismagulov References: <20220607152531.3498370-1-adriaan.schmidt@siemens.com> From: Anton Mikanovich In-Reply-To: <20220607152531.3498370-1-adriaan.schmidt@siemens.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: Gi4R5QWsH9FS 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.