From: Jan Kiszka <jan.kiszka@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>,
isar-users@googlegroups.com, "Moessbauer,
Felix (T CED SES-DE)" <felix.moessbauer@siemens.com>
Cc: kas-devel <kas-devel@googlegroups.com>
Subject: Re: [PATCH] sbuild: fix cross-building packages on bookworm host
Date: Wed, 7 Jun 2023 07:36:36 +0200 [thread overview]
Message-ID: <6ee165a1-df47-59cf-86ce-2addd1fc4d5f@siemens.com> (raw)
In-Reply-To: <20230607044638.31037-1-ubely@ilbers.de>
On 07.06.23 06:46, Uladzimir Bely wrote:
> Bookworm uses more version of sbuild that requires from target rootfs
s/more/a newer/
> to include apt resolver (/usr/lib/apt/solvers/apt).
>
> This is automatically provided by 'bookworm' target, but not by older
> 'buster' or 'bullseye' that don't strictly depend on apt-utils package
> that provides this solver.
>
> Add `apt-utils` to host sbuild chroot in order to fix build issues.
>
> See https://groups.google.com/g/isar-users/c/OIIp6qF3C8I for details.
>
> Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
> ---
> meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb b/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb
> index d2e23d56..255d6937 100644
> --- a/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb
> +++ b/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb
> @@ -16,6 +16,7 @@ ROOTFS_BASE_DISTRO = "${HOST_BASE_DISTRO}"
> SBUILD_CHROOT_PREINSTALL ?= " \
> ${SBUILD_CHROOT_PREINSTALL_COMMON} \
> crossbuild-essential-${DISTRO_ARCH} \
> + apt-utils \
> "
>
> SBUILD_CHROOT_PREINSTALL:riscv64 ?= " \
Thanks, makes sense to me now.
>From kas perspective, there is still the catch now that we will require
users of the upcoming bookworm-based build container to update their
isar past this patch or carry it locally. Not much we can do about that
anymore, though. The key value of bookworm as host is dpkg can handle
zstd which improves interaction with the Ubuntu universe.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2023-06-07 5:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 4:46 Uladzimir Bely
2023-06-07 5:36 ` Jan Kiszka [this message]
2023-06-07 6:45 ` Uladzimir Bely
2023-06-13 6:08 ` Uladzimir Bely
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=6ee165a1-df47-59cf-86ce-2addd1fc4d5f@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=kas-devel@googlegroups.com \
--cc=ubely@ilbers.de \
/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