From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: "Moessbauer,
Felix (FT RPD CED OES-DE)" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"wzh@ilbers.de" <wzh@ilbers.de>
Subject: Re: [PATCH v2 0/2] bitbake: Update to 2.8.1 release (no update!)
Date: Mon, 9 Mar 2026 13:37:23 +0100 [thread overview]
Message-ID: <f42314d6-1eda-4f47-87cb-f683cce3900e@siemens.com> (raw)
In-Reply-To: <f553fc200ca4ee5d4cd13f966c820bae05fe7b65.camel@siemens.com>
On 09.03.26 12:07, Moessbauer, Felix (FT RPD CED OES-DE) wrote:
> On Mon, 2026-03-09 at 10:56 +0100, Zhihang Wei wrote:
>> On 3/6/26 17:15, Felix Moessbauer wrote:
>>> Changes since v1:
>>>
>>> - do not update bitbake (due to python requirements)
>>> - do not change python requirements
>>> - only backport exception handling patch from upstream,
>>> needed for debian trixie hosts (applies cleanly)
>>>
>>> For testing the exception, create an invalid variable assignment,
>>> e.g. MYVAR = "no-closing-quote
>>>
>>> The error should properly propagate back to the caller, indicating in
>>> which file it happened.
>>>
>>> Best regards,
>>> Felix Moessbauer
>>> Siemens AG
>>>
>>> Felix Moessbauer (2):
>>> partial revert of "Bitbake: use LAYERDIR_RE when setting
>>> BBFILE_PATTERN_x"
>>> Remove custom exception backtrace formatting
>>>
>>> bitbake/lib/bb/cooker.py | 32 +++++--
>>> bitbake/lib/bb/event.py | 9 +-
>>> bitbake/lib/bb/exceptions.py | 96 -------------------
>>> bitbake/lib/bb/msg.py | 4 -
>>> bitbake/lib/bb/ui/teamcity.py | 5 -
>>> .../tests/testdata/layer1/conf/layer.conf | 2 +-
>>> .../tests/testdata/layer2/conf/layer.conf | 2 +-
>>> .../tests/testdata/layer3/conf/layer.conf | 2 +-
>>> .../tests/testdata/layer4/conf/layer.conf | 2 +-
>>> 9 files changed, 29 insertions(+), 125 deletions(-)
>>> delete mode 100644 bitbake/lib/bb/exceptions.py
>>>
>> CI passed on my side.
>
> Ok, feel free to adjust the author (and the signoff) as proposed by
> Jan. I didn't do that, as this is just a copy-in of the bitbake commit
> and previously we also didn't do it.
We did in many cases, and in all where we didn't, it was just wrong,
specifically from the copyright attribution perspective.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
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/f42314d6-1eda-4f47-87cb-f683cce3900e%40siemens.com.
prev parent reply other threads:[~2026-03-09 12:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 16:15 'Felix Moessbauer' via isar-users
2026-03-06 16:15 ` [PATCH v2 1/2] partial revert of "Bitbake: use LAYERDIR_RE when setting BBFILE_PATTERN_x" 'Felix Moessbauer' via isar-users
2026-03-06 16:15 ` [PATCH v2 2/2] bitbake: Remove custom exception backtrace formatting 'Felix Moessbauer' via isar-users
2026-03-06 16:40 ` 'Jan Kiszka' via isar-users
2026-03-10 11:21 ` Anton Mikanovich
2026-03-09 9:56 ` [PATCH v2 0/2] bitbake: Update to 2.8.1 release (no update!) Zhihang Wei
2026-03-09 11:07 ` 'MOESSBAUER, Felix' via isar-users
2026-03-09 12:37 ` 'Jan Kiszka' 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=f42314d6-1eda-4f47-87cb-f683cce3900e@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=wzh@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