From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Bouska, Zdenek" <zdenek.bouska@siemens.com>
Cc: "Hombourger, Cedric" <cedric.hombourger@siemens.com>
Subject: Re: [PATCH 1/1] debsbom: update to version 0.5.1 and rework dependencies
Date: Thu, 15 Jan 2026 14:28:21 +0000 [thread overview]
Message-ID: <a7ace30e449d38a3c0854e75bf5407e5aeb9f29f.camel@siemens.com> (raw)
In-Reply-To: <AS1PR10MB567502BCF4927C2FBCAF246DEB8CA@AS1PR10MB5675.EURPRD10.PROD.OUTLOOK.COM>
On Thu, 2026-01-15 at 13:56 +0000, Bouška, Zdeněk (FT D EU CZ PDS1 ICC
1) wrote:
> > PS: @Zdenek This release still does not model the virtual packages, but
> > you can use it to just update the SRCREV to the latest commit on debsbom
> > master for testing. Once you confirm that this solves the issue, we will
> > cut debsbom 0.6.0 and update this patch as well.
>
> Hi Felix,
>
> I still have the same error: ModuleNotFoundError: No module named 'license_expression'
> but with a lot longer output.
>
Ok, this happens because the upcoming debsbom 0.6.0 needs the license-
expression module at build time (but now we need a version which is
widely available instead of latest-greatest as before). Just adding it
should fix your issue:
diff --git a/meta/recipes-support/python3-debsbom/python3-
debsbom_0.5.1.bb b/meta/recipes-support/python3-debsbom/python3-
debsbom_0.5.1.bb
index f1524129..18ef2084 100644
--- a/meta/recipes-support/python3-debsbom/python3-debsbom_0.5.1.bb
+++ b/meta/recipes-support/python3-debsbom/python3-debsbom_0.5.1.bb
@@ -24,6 +24,7 @@ DEBIAN_BUILD_DEPENDS = "dh-python, \
python3-debian, \
python3-requests, \
python3-zstandard, \
+ python3-license-expression, \
"
DEBIAN_DEPENDS = "python3-apt, \${python3:Depends}, \${misc:Depends}"
@@ -34,7 +35,7 @@ SRC_URI =
"git://github.com/siemens/debsbom.git;protocol=https;branch=main; \
file://rules \
file://0001-Use-old-license-description-in-pyproject.toml.patch \
"
-SRCREV = "ba63720dfc0dc6dcb01994031e092aaebb62a399"
+SRCREV = "5e0bf7573dc89260d1d9ff8d91e347d16ae6b236"
do_prepare_build[cleandirs] += "${S}/debian"
do_prepare_build() {
Best regards,
Felix
--
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany
--
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/a7ace30e449d38a3c0854e75bf5407e5aeb9f29f.camel%40siemens.com.
next prev parent reply other threads:[~2026-01-15 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 11:27 'Felix Moessbauer' via isar-users
2026-01-15 13:56 ` 'Bouska, Zdenek' via isar-users
2026-01-15 14:28 ` 'MOESSBAUER, Felix' via isar-users [this message]
2026-01-20 15:36 ` 'Bouska, Zdenek' via isar-users
2026-01-20 15:28 ` 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=a7ace30e449d38a3c0854e75bf5407e5aeb9f29f.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=cedric.hombourger@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=zdenek.bouska@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