public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 0/3] Update bitbake to 2.8.1
Date: Wed,  4 Mar 2026 14:31:45 +0100	[thread overview]
Message-ID: <20260304133148.1838456-1-felix.moessbauer@siemens.com> (raw)

Prior to the update we ensure the bitbake dir is patch-free.

This makes bitbake compatible with Python 3.14 and fixes a critical
error on Debian Trixie hosts where no stacktrace was shown on a
parser exception.

Given that isar releases happen quite rarely and considering that
Debian Trixie is the current stable release, I consider this patch
series release critical (despite coming late to the table).

Best regards,
Felix Moessbauer
Siemens AG

Felix Moessbauer (3):
  partial revert of "Bitbake: use LAYERDIR_RE when setting
    BBFILE_PATTERN_x"
  Revert "bitbake: Downgrade python requirements"
  bitbake: Update to 2.8.1 release

 bitbake/bin/bitbake                           |   2 +-
 bitbake/bin/bitbake-diffsigs                  |   9 +-
 .../bitbake-user-manual-ref-variables.rst     |   2 +-
 bitbake/lib/bb/__init__.py                    |  47 ++++++-
 bitbake/lib/bb/asyncrpc/client.py             |   6 +-
 bitbake/lib/bb/asyncrpc/serv.py               |   2 +-
 bitbake/lib/bb/codeparser.py                  |  33 +++--
 bitbake/lib/bb/command.py                     |  21 ++-
 bitbake/lib/bb/cooker.py                      |  54 +++++---
 bitbake/lib/bb/data.py                        |   2 +-
 bitbake/lib/bb/data_smart.py                  |  16 +--
 bitbake/lib/bb/event.py                       |  19 +--
 bitbake/lib/bb/exceptions.py                  |  96 --------------
 bitbake/lib/bb/fetch2/__init__.py             |  64 ++++-----
 bitbake/lib/bb/fetch2/gcp.py                  |  13 +-
 bitbake/lib/bb/fetch2/git.py                  |   3 +-
 bitbake/lib/bb/fetch2/gitsm.py                |  44 +++----
 bitbake/lib/bb/fetch2/wget.py                 |  29 +++--
 bitbake/lib/bb/msg.py                         |   4 -
 bitbake/lib/bb/parse/__init__.py              |  12 +-
 bitbake/lib/bb/parse/ast.py                   |  20 +--
 bitbake/lib/bb/persist_data.py                |   1 +
 bitbake/lib/bb/runqueue.py                    | 123 +++++++++++++-----
 bitbake/lib/bb/server/process.py              |   2 +-
 bitbake/lib/bb/siggen.py                      |  11 +-
 bitbake/lib/bb/tests/fetch.py                 |  14 +-
 .../lib/bb/tests/runqueue-tests/recipes/g1.bb |   2 +
 .../lib/bb/tests/runqueue-tests/recipes/h1.bb |   0
 bitbake/lib/bb/tests/runqueue.py              |  11 +-
 bitbake/lib/bb/tests/support/httpserver.py    |   4 +-
 bitbake/lib/bb/tinfoil.py                     |  16 ++-
 bitbake/lib/bb/ui/knotty.py                   |  20 ++-
 bitbake/lib/bb/ui/teamcity.py                 |   5 -
 bitbake/lib/bb/utils.py                       |  33 ++++-
 bitbake/lib/bblayers/query.py                 |  15 ++-
 bitbake/lib/hashserv/client.py                | 106 +++++++++++++--
 bitbake/lib/hashserv/tests.py                 |  77 ++++++++++-
 .../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 +-
 bitbake/lib/toaster/tests/builds/buildtest.py |   2 +-
 42 files changed, 604 insertions(+), 344 deletions(-)
 delete mode 100644 bitbake/lib/bb/exceptions.py
 create mode 100644 bitbake/lib/bb/tests/runqueue-tests/recipes/g1.bb
 create mode 100644 bitbake/lib/bb/tests/runqueue-tests/recipes/h1.bb

-- 
2.53.0

-- 
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/20260304133148.1838456-1-felix.moessbauer%40siemens.com.

             reply	other threads:[~2026-03-04 13:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 13:31 'Felix Moessbauer' via isar-users [this message]
2026-03-04 13:31 ` [PATCH 1/3] partial revert of "Bitbake: use LAYERDIR_RE when setting BBFILE_PATTERN_x" 'Felix Moessbauer' via isar-users
2026-03-04 13:31 ` [PATCH 2/3] Revert "bitbake: Downgrade python requirements" 'Felix Moessbauer' via isar-users
2026-03-04 13:31 ` [PATCH 3/3] bitbake: Update to 2.8.1 release 'Felix Moessbauer' via isar-users
2026-03-06 10:10   ` Zhihang Wei
2026-03-06 10:25     ` 'MOESSBAUER, Felix' via isar-users
2026-03-06 11:05       ` 'Jan Kiszka' via isar-users
2026-03-06 15:51         ` 'MOESSBAUER, Felix' via isar-users
2026-03-06 15:55           ` Zhihang Wei

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=20260304133148.1838456-1-felix.moessbauer@siemens.com \
    --to=isar-users@googlegroups.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