public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Moessbauer, Felix' via isar-users" <isar-users@googlegroups.com>
To: "Kowalsky, Clara" <clara.kowalsky@siemens.com>,
	"amikan@ilbers.de" <amikan@ilbers.de>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH 0/8] Update BitBake in Isar to v2.20.0
Date: Mon, 16 Nov 2026 12:12:40 +0000	[thread overview]
Message-ID: <27485ec2de1974eb33b57c4ebf298be260d93be5.camel@siemens.com> (raw)
In-Reply-To: <37912ce3-0c5a-4a8b-9bae-d6521ce7b218@siemens.com>

On Mon, 2026-11-16 at 11:44 +0100, Clara Kowalsky wrote:
> On 11/16/26 09:46, Moessbauer, Felix (FT RPD CPC OES-DE) wrote:
> > On Fri, 2026-11-13 at 18:19 +0100, 'Clara Kowalsky' via isar-users
> > wrote:
> > > On 11/13/26 15:41, Anton Mikanovich wrote:
> > > > 09.11.2026 11:17, 'Clara Kowalsky' via isar-users wrote:
> > > > > This series updates Isar's BitBake from v2.8.0 to v2.20.0, which is the
> > > > > latest stable release. The update includes Isar adaptions to the
> > > > > intervening fetcher, signature and metadata parser changes.
> > > > > 
> > > > > Debian Buster remains supported as an image target. Its imaging chroot
> > > > > provides Python 3.7, while BitBake v2.20.0 requires Python 3.9. The
> > > > > series moves WIC's Python driver to the build host and keeps image
> > > > > utilities in the imaging chroot.
> > > > Hello Clara,
> > > > 
> > > > Are there any reasons of using Bitbake 2.20 branch, but not 2.18 from LTS
> > > > version of Yocto?
> > > > Previously we've updated between Bitbake branches of LTS Yocto with
> > > > applying
> > > > any new fixes by going up through the same Bitbake branch. I just afraid
> > > > if we
> > > > choose using 2.20 in 6 months it will become a part of EOL Yocto branch
> > > > and the
> > > > new major Bitbake version upgrade will be needed.
> > > > So my proposal is to use Bitbake 2.18 from Yocto 6.0 LTS.
> > > > 
> > > That's a good point. We can also update to 2.18. Just to confirm, you
> > > mean commit
> > > https://github.com/openembedded/bitbake/commit/33581c84f3a85008239acbd940501a35de48dc91?
> > 
> > Hi, either this one, or just the latest commit from the 2.18 branch
> > (6e260eb6ab1631607ea414d9ff8ede1155faa5d9). The 2.18.0 tag is from
> > April, which makes me wonder how often they create bugfix releases (or
> > if at all).
> > 
> > I'd go with 6e260eb6.
> > 
> > Felix
> 
> I'll take 
> https://github.com/openembedded/bitbake/commit/51fd94a67fa17650a9ff623492005972bbc7d26f, 
> one commit away from 6e260eb6ab1631607ea414d9ff8ede1155faa5d9 on branch 
> 2.18, but tagged with yocto-6.0.4, so we're at least updating to a 
> tagged version.

Makes sense!

Felix

> 
> Clara
> > 
> > > 
> > > Clara
> > > 
> > > -- 
> > > You received this message because you are subscribed to the Google Groups "isar-users" group.
> > > To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
> > > To view this discussion visit https://groups.google.com/d/msgid/isar-users/b881173e-737c-4ba7-9bfa-eb115f9e082c%40siemens.com.
> > 

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/27485ec2de1974eb33b57c4ebf298be260d93be5.camel%40siemens.com.

      reply	other threads:[~2026-11-16 12:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09  9:17 'Clara Kowalsky' via isar-users
2026-11-09  9:17 ` [PATCH 1/8] base: replace BitBake's outdated persist_data 'Clara Kowalsky' via isar-users
2026-11-10 11:18   ` 'Moessbauer, Felix' via isar-users
2026-11-11 14:37     ` 'Clara Kowalsky' via isar-users
2026-11-09  9:17 ` [PATCH 2/8] isar-events: preserve cleanup for default multiconfig 'Clara Kowalsky' via isar-users
2026-11-09  9:17 ` [PATCH 3/8] isar-events: close /proc/mounts after cleanup 'Clara Kowalsky' via isar-users
2026-11-10 11:22   ` 'Moessbauer, Felix' via isar-users
2026-11-11 14:38     ` 'Clara Kowalsky' via isar-users
2026-11-09  9:17 ` [PATCH 4/8] meta: migrate fetcher references to bb.fetch 'Clara Kowalsky' via isar-users
2026-11-09  9:17 ` [PATCH 5/8] wic: run the Python driver outside the imaging chroot 'Clara Kowalsky' via isar-users
2026-11-10 11:39   ` 'Moessbauer, Felix' via isar-users
2026-11-11 14:39     ` 'Clara Kowalsky' via isar-users
2026-11-09  9:17 ` [PATCH 6/8] bitbake.conf: explicitly exclude export and func from signatures 'Clara Kowalsky' via isar-users
2026-11-09  9:18 ` [PATCH 7/8] meta: add missing whitespace around assignment operators 'Clara Kowalsky' via isar-users
2026-11-09  9:18 ` [PATCH 8/8] bitbake: update to v2.20.0 'Clara Kowalsky' via isar-users
2026-11-13 14:41 ` [PATCH 0/8] Update BitBake in Isar " Anton Mikanovich
2026-11-13 17:19   ` 'Clara Kowalsky' via isar-users
2026-11-16  8:46     ` 'Moessbauer, Felix' via isar-users
2026-11-16 10:44       ` 'Clara Kowalsky' via isar-users
2026-11-16 12:12         ` 'Moessbauer, Felix' via isar-users [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=27485ec2de1974eb33b57c4ebf298be260d93be5.camel@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=amikan@ilbers.de \
    --cc=clara.kowalsky@siemens.com \
    --cc=felix.moessbauer@siemens.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