From: Srinuvasan Arjunan <srinuvasanasv@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 0/1] Add SBOM generation with debsbom
Date: Fri, 12 Sep 2025 02:34:35 -0700 (PDT) [thread overview]
Message-ID: <cce16b7c-3500-494e-b8ae-3f4365909124n@googlegroups.com> (raw)
In-Reply-To: <96a80423-234b-4dcc-9620-5209f2744e4dn@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 2698 bytes --]
Hi,
When generating SBOM for foreign architectures (e.g., arm64), some
Python packages fail to build. One such example is
python3-cyclonedx-python-lib. During arm64 builds it throws the below error:
| The following packages have unmet dependencies:
| sbuild-build-depends-main-dummy:arm64 : Depends: dh-python:arm64
| Depends: python3-all:arm64 but
it is not going to be installed
| Depends: python3-setuptools:arm64
| Depends:
pybuild-plugin-pyproject:arm64
| Depends: python3-hatchling:arm64
but it is not installable
The fix is to add the :native suffix for Python build dependencies. For
example:
DEBIAN_BUILD_DEPENDS = "debhelper (>= 11~), \
dh-python, \
python3-all:native, \
python3-setuptools, \
pybuild-plugin-pyproject, \
python3-poetry:native, \
python3-py-serializable:native, \
python3-packageurl-python:native, \
python3-sortedcontainers, \
python3-ddt:native, \
python3-defusedxml:native, \
python3-license-expression:native, \
python3-jsonschema:native, \
python3-lxml:native, \
"
In short, Python recipes required for the build must explicitly use the
:native suffix to avoid cross-architecture dependency resolution issues.
Similar fixes are needed for all the python recipes in this patch.
Many thanks,
Srinu
On Friday, September 12, 2025 at 1:47:13 PM UTC+5:30 Srinuvasan Arjunan
wrote:
Hi Steiger,
In this patch series, the first patch (*meta: package Python dependencies
for SBOM generation*) does not work on foreign architectures. I have fixed
those cross-build issues — shall I send a v2 of this patch in the series?
Many thanks,
Srinu
On Thursday, September 11, 2025 at 6:31:54 PM UTC+5:30 srinuv...@siemens.com
wrote:
From: srinuvasan <srinuv...@siemens.com>
Includes additional fixes alongside the following patch series
https://groups.google.com/g/isar-users/c/4JntAI3gL1s
srinuvasan (1):
meta: derive ROOTFS_DISTRO correctly in sbom-chroot's
do_prepare_rootfs
meta/recipes-devtools/sbom-chroot/sbom-chroot.bb | 5 -----
1 file changed, 5 deletions(-)
--
2.39.5
--
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/cce16b7c-3500-494e-b8ae-3f4365909124n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 5080 bytes --]
next prev parent reply other threads:[~2025-09-12 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 13:04 srinuvasan.a via isar-users
2025-09-11 13:04 ` [PATCH 1/1] meta: derive ROOTFS_DISTRO correctly in sbom-chroot's do_prepare_rootfs srinuvasan.a via isar-users
2025-09-11 13:53 ` 'MOESSBAUER, Felix' via isar-users
2025-09-12 8:17 ` [PATCH 0/1] Add SBOM generation with debsbom Srinuvasan Arjunan
2025-09-12 9:34 ` Srinuvasan Arjunan [this message]
2025-09-12 11:02 ` 'MOESSBAUER, Felix' 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=cce16b7c-3500-494e-b8ae-3f4365909124n@googlegroups.com \
--to=srinuvasanasv@gmail.com \
--cc=isar-users@googlegroups.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