public inbox for bitbake-devel@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Freihofer, Adrian" <adrian.freihofer@siemens.com>,
	 "bitbake-devel@lists.openembedded.org"
	<bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] [PATCH v3 00/14] bitbake-setup: improvements, VSCode workspace generation
Date: Mon, 30 Mar 2026 11:17:36 +0100	[thread overview]
Message-ID: <652ec352c81776b9facec797e78fddac0a95c643.camel@linuxfoundation.org> (raw)
In-Reply-To: <e1fe66216b8b426198689c8acf27fb1c21daa800.camel@siemens.com>

On Mon, 2026-03-30 at 09:01 +0000, Freihofer, Adrian wrote:
> On Mon, 2026-03-30 at 08:09 +0100, Richard Purdie wrote:
> > On Sun, 2026-03-29 at 20:32 +0200, Adrian Freihofer via
> > lists.openembedded.org wrote:
> > > From: Adrian Freihofer <adrian.freihofer@siemens.com>
> > > 
> > > Changes from v2 to v3:
> > > - Rebased on master-next from 29.3.2026:
> > > - New commit:
> > >   bitbake-setup: Fix type annotation for descriptions parameter in
> > > print_configs
> > >   might be squashed into commit on master-next
> > > - New exception: bb.fetch2.RebaseError
> > >   - Adapted tests accordingly
> > >   - Simplified code in bitbake-setup accordingly
> > > - New commit:
> > >   bitbake-setup: catch unexpected exceptions and show a clean error
> > > message
> > > - Documentation
> > >   - git fetcher unpack_update
> > >   - bitbake-setup non destructive update mode
> > 
> > Sorry Adrian, this caused an issue on the autobuilder:
> > 
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/5/builds/3443
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/92/builds/3471
> > (and probably a few more)
> > 
> > Traceback (most recent call last):
> >   File "/srv/pokybuild/yocto-worker/qemuarm64-
> > tc/build/repos/bitbake/bin/bitbake-setup", line 49, in <module>
> >     def print_configs(prompt: str, choices: list[str], descriptions:
> > list[str] | None = None):
> > TypeError: unsupported operand type(s) for |: 'types.GenericAlias'
> > and 'NoneType'
> > 
> > python version specific?
> 
> It's the first patch which adds only this little (as I just learned
> problematic) detail. It requires Python 3.10+.
> Would you like to try this series without patch
> 
> [PATCH v3 01/14] bitbake-setup: Fix type annotation for descriptions
> parameter in print_configs

I've tried this and it is looking much better, thanks.

Cheers,

Richard


      reply	other threads:[~2026-03-30 10:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-29 18:32 [PATCH v3 00/14] bitbake-setup: improvements, VSCode workspace generation AdrianF
2026-03-29 18:32 ` [PATCH v3 01/14] bitbake-setup: Fix type annotation for descriptions parameter in print_configs AdrianF
2026-03-29 18:32 ` [PATCH v3 02/14] fetch2: add LocalModificationsError and RebaseError exceptions AdrianF
2026-03-29 18:32 ` [PATCH v3 03/14] bitbake-selftest: add GitUnpackUpdateTest AdrianF
2026-03-29 18:32 ` [PATCH v3 04/14] tests/fetch: remove unused import, fix trailing whitespace AdrianF
2026-03-29 18:32 ` [PATCH v3 05/14] doc: document the unpack_update() non-destructive git update method AdrianF
2026-03-29 18:32 ` [PATCH v3 06/14] bitbake-setup: always restore sys.stdout AdrianF
2026-03-29 18:32 ` [PATCH v3 07/14] tests/setup: cleanup imports AdrianF
2026-03-29 18:32 ` [PATCH v3 08/14] tests/setup: fix dead check_setupdir_files guards AdrianF
2026-03-29 18:32 ` [PATCH v3 09/14] bitbake-setup: generate config files for VSCode AdrianF
2026-03-29 18:32 ` [PATCH v3 10/14] tests/setup: add test_vscode for VSCode workspace generation AdrianF
2026-03-29 18:32 ` [PATCH v3 11/14] bitbake-setup: add --rebase-conflicts-strategy to the update command AdrianF
2026-03-29 18:32 ` [PATCH v3 12/14] tests/setup: add test_update_rebase_conflicts_strategy AdrianF
2026-03-29 18:33 ` [PATCH v3 13/14] bitbake-setup: catch unexpected exceptions and show a clean error message AdrianF
2026-03-29 18:33 ` [PATCH v3 14/14] doc: document new bitbake-setup init and update features AdrianF
2026-03-30  7:09 ` [bitbake-devel] [PATCH v3 00/14] bitbake-setup: improvements, VSCode workspace generation Richard Purdie
2026-03-30  9:01   ` Freihofer, Adrian
2026-03-30 10:17     ` Richard Purdie [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=652ec352c81776b9facec797e78fddac0a95c643.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=adrian.freihofer@siemens.com \
    --cc=bitbake-devel@lists.openembedded.org \
    /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