public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>,
	Uladzimir Bely <ubely@ilbers.de>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH 0/1] Update bitbake to version 1.50.4
Date: Wed, 2 Feb 2022 07:52:26 +0100	[thread overview]
Message-ID: <715e33cf-08c4-2301-e83e-c0f6a7cdb40a@siemens.com> (raw)
In-Reply-To: <AS4PR10MB5318DCB282169B8A38D79B87ED279@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM>

On 02.02.22 07:25, Schmidt, Adriaan wrote:
> Uladzimir Bely, 1. Februar 2022 12:42:
>> To: isar-users@googlegroups.com
>> Subject: [PATCH 0/1] Update bitbake to version 1.50.4
>>
>> Bitbake in Isar didn't get updates for almost 1.5 years. At the same time
>> the version we use have at least one annoying bug, when messages in log
>> files got duplicated if "--verbose" option is used and error happens.
>>
>> This was fixed in upstream revision 69c622b744d9, few commits before the
>> tag 1.50.4.
>>
>> Also, there is 1.52 branch exists (latest tag 1.52.1), but it seems to be
>> incompatible with Isar.
> 
> One of the major changes is a new syntax for overrides:
> https://docs.yoctoproject.org/migration-guides/migration-3.4.html#override-syntax-changes
> 
> This will of course break many (all?) downstream layers. But as it has to happen sooner or later, I'd rather vote for "sooner"...
> 

Yeah, and we likely need to start by updating Isar itself, its imported
OE bits as well as own recipes.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux

  reply	other threads:[~2022-02-02  6:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 11:42 Uladzimir Bely
2022-02-01 11:42 ` [PATCH 1/1] bitbake: Update to 1.50.4 release Uladzimir Bely
2022-02-02  6:25 ` [PATCH 0/1] Update bitbake to version 1.50.4 Schmidt, Adriaan
2022-02-02  6:52   ` Jan Kiszka [this message]
2022-03-28  8:44     ` Henning Schild
2022-03-25  6:31 ` Anton Mikanovich
2022-04-19 12:41   ` Bezdeka, Florian
2022-04-19 12:51     ` Henning Schild
2022-04-19 14:02       ` Bezdeka, Florian
2022-04-19 14:26         ` Baurzhan Ismagulov
2022-04-19 14:35         ` Henning Schild

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=715e33cf-08c4-2301-e83e-c0f6a7cdb40a@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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