public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
	"Kiszka, Jan" <jan.kiszka@siemens.com>,
	Zhihang Wei <wzh@ilbers.de>, Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH v3 0/2] bitbake: Update to 2.8.1 release (no update!)
Date: Wed, 11 Mar 2026 13:18:31 +0200	[thread overview]
Message-ID: <14258f45-2493-4b79-9ac7-8a05a5a6141a@ilbers.de> (raw)
In-Reply-To: <20260311111526.665094-1-amikan@ilbers.de>

We are going to merge this patchset to next tomorrow if no objections.

11.03.2026 13:15, Anton Mikanovich wrote:
> This is just a resend patchset from Felix Moessbauer without any functional
> changes.
>
> Changes since v2:
> - restore original commit authors
>
> 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.
>
> Joshua Watt (1):
>    bitbake: Remove custom exception backtrace formatting
>
> MOESSBAUER, Felix (1):
>    partial revert of "Bitbake: use LAYERDIR_RE when setting
>      BBFILE_PATTERN_x"
>
>   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
>

-- 
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/14258f45-2493-4b79-9ac7-8a05a5a6141a%40ilbers.de.

  parent reply	other threads:[~2026-03-11 11:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11 11:15 Anton Mikanovich
2026-03-11 11:15 ` [PATCH v3 1/2] partial revert of "Bitbake: use LAYERDIR_RE when setting BBFILE_PATTERN_x" Anton Mikanovich
2026-03-11 11:15 ` [PATCH v3 2/2] bitbake: Remove custom exception backtrace formatting Anton Mikanovich
2026-03-11 11:18 ` Anton Mikanovich [this message]
2026-03-12  8:45 ` [PATCH v3 0/2] bitbake: Update to 2.8.1 release (no update!) 'MOESSBAUER, Felix' via isar-users
2026-03-12 13:06 ` Anton Mikanovich

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=14258f45-2493-4b79-9ac7-8a05a5a6141a@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=ibr@ilbers.de \
    --cc=isar-users@googlegroups.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