From: Srinuvasan Arjunan <srinuvasan_a@mentor.com>
To: <isar-users@googlegroups.com>
Cc: <ubely@ilbers.de>, Srinuvasan A <srinuvasan.a@siemens.com>
Subject: [PATCH] sbuild-chroot/sbuild-chroot-host: enable apt-utils only for bookworm
Date: Sat, 22 Jul 2023 08:00:29 +0530 [thread overview]
Message-ID: <20230722023029.1710181-1-srinuvasan_a@mentor.com> (raw)
From: Srinuvasan A <srinuvasan.a@siemens.com>
In downstream layer we try to cross-building packages for bullseye,
but it throws the below error:
| Reading package lists...
| Building dependency tree...
| Package apt-utils is not available, but is referred to by another package.
| This may mean that the package is missing, has been obsoleted, or
| is only available from another source
| However the following packages replace it:
| apt:armhf apt
|
| E: Package 'apt-utils' has no installation candidate
| WARNING: exit code 100 from a shell command.
I hope the APT resolver (/usr/lib/apt/solvers/apt) only demands for
bookworm, hence it's enabled based on BASE_DISTRO_CODENAME.
Signed-off-by: Srinuvasan A <srinuvasan.a@siemens.com>
---
meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb b/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb
index 255d693..9738a1c 100644
--- a/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb
+++ b/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb
@@ -16,7 +16,7 @@ ROOTFS_BASE_DISTRO = "${HOST_BASE_DISTRO}"
SBUILD_CHROOT_PREINSTALL ?= " \
${SBUILD_CHROOT_PREINSTALL_COMMON} \
crossbuild-essential-${DISTRO_ARCH} \
- apt-utils \
+ ${@ 'apt-utils' if d.getVar('BASE_DISTRO_CODENAME') == 'bookworm' else ''} \
"
SBUILD_CHROOT_PREINSTALL:riscv64 ?= " \
--
2.34.1
next reply other threads:[~2023-07-22 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 2:30 Srinuvasan Arjunan [this message]
2023-07-22 8:30 ` Henning Schild
2023-07-22 10:22 ` Henning Schild
2023-07-22 11:23 ` Srinuvasan Arjunan
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=20230722023029.1710181-1-srinuvasan_a@mentor.com \
--to=srinuvasan_a@mentor.com \
--cc=isar-users@googlegroups.com \
--cc=srinuvasan.a@siemens.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