From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: Ulrich Teichert <ulrich.teichert@ebs-group.io>,
Isar <isar-users@googlegroups.com>
Cc: "krypton@ulrich-teichert.org" <krypton@ulrich-teichert.org>
Subject: Re: [PATCH 1/1] Bugfix: add a check for "None" to raise a WicError
Date: Wed, 15 Jul 2026 09:26:40 +0000 [thread overview]
Message-ID: <d43020611c65db3331d6ed534388ef5ca673553d.camel@siemens.com> (raw)
In-Reply-To: <DB9PR08MB7448CACF902B3BD447CF4C51C3F82@DB9PR08MB7448.eurprd08.prod.outlook.com>
On Wed, 2026-07-15 at 09:04 +0000, Ulrich Teichert wrote:
> Hi Felix,
>
> > > Add a check for "None" to raise a WicError because
> > > get_bitbake_var may return "None" if the variable is not available, which
> > > would result in an exception inside os.path.isdir and not to the WicError
> > > exception as intended.
>
> > Hi,
> >
> > did you also send this patch to OE? Changes in the wic plugins that are
> > not purely isar related have to be accepted by OE first (to avoid that
> > our plugins diverge up to the point of not being able to update them
> > anymore).
>
> No, I wasn't aware of the fact that the rootfs plugin comes from stock OE - but
> in that case I'll divert my patch in that direction ;-)
Thanks!
>
> BTW, is there a rule or a list what is from stock OE in Isar and what isn't?
Unfortunately not that I'm aware of.
Some parts like bitbake, oe-libs and the sstate.bbclass are taken as-
is. Other parts like the wic plugins are patched versions of upstream.
I hope this will get better once isar also splits the repo into
upstream bitbake and the isar-core layer (as Yocto already did). But
I'm not sure if and when that will happen.
Maybe the maintainers can say something about this.
Best regards,
Felix
>
> CU,
> Uli
--
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/d43020611c65db3331d6ed534388ef5ca673553d.camel%40siemens.com.
next prev parent reply other threads:[~2026-07-15 9:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 6:41 'Ulrich Teichert' via isar-users
2026-07-15 8:11 ` 'MOESSBAUER, Felix' via isar-users
2026-07-15 9:04 ` 'Ulrich Teichert' via isar-users
2026-07-15 9:26 ` 'MOESSBAUER, Felix' via isar-users [this message]
2026-07-15 9:55 ` Anton Mikanovich
2026-07-15 16:15 ` 'MOESSBAUER, Felix' via isar-users
2026-07-15 16:30 ` 'Jan Kiszka' via isar-users
2026-07-16 6:21 ` Anton Mikanovich
2026-07-15 11:33 ` 'Ulrich Teichert' via isar-users
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=d43020611c65db3331d6ed534388ef5ca673553d.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=krypton@ulrich-teichert.org \
--cc=ulrich.teichert@ebs-group.io \
/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