From: Srinuvasan A <Srinuvasan_A@mentor.com>
To: <isar-users@googlegroups.com>
Cc: Srinuvasan A <srinuvasan_a@mentor.com>
Subject: [PATCH] debian-common: Add fdisk package as a dependency in wic
Date: Thu, 26 Aug 2021 10:46:03 +0530 [thread overview]
Message-ID: <20210826051603.3649442-1-Srinuvasan_A@mentor.com> (raw)
From: Srinuvasan A <srinuvasan_a@mentor.com>
When we build the bullseye images for de0-nano-soc target it's getting
failed in wic image creation step due to sfdisk required to build the
wic images.
We added --syste-id to WKS file and triggered the builds for buster as
well as bullseye, buster image got passed, might be that indirectly pull
the fdisk package but bullseye builds got failed hence added this
package as a dependency in wic imager install.
Signed-off-by: Srinuvasan A <srinuvasan_a@mentor.com>
---
meta/conf/distro/debian-common.conf | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/conf/distro/debian-common.conf b/meta/conf/distro/debian-common.conf
index ba5262a..4c9b225 100644
--- a/meta/conf/distro/debian-common.conf
+++ b/meta/conf/distro/debian-common.conf
@@ -16,7 +16,8 @@ WIC_IMAGER_INSTALL = "parted \
e2fsprogs \
python3 \
bmap-tools \
- tar"
+ tar \
+ fdisk"
GRUB_BOOTLOADER_INSTALL_amd64 = "grub-efi-amd64-bin"
GRUB_BOOTLOADER_INSTALL_i386 = "grub-efi-ia32-bin"
--
2.25.1
next reply other threads:[~2021-08-26 5:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 5:16 Srinuvasan A [this message]
2021-08-26 9:18 ` Henning Schild
2021-08-26 12:16 ` Srinuvasan A
2021-08-26 19:26 ` Henning Schild
2021-08-27 13:05 ` [PATCH v3] " Srinuvasan A
2021-08-27 16:00 ` Henning Schild
2021-08-27 13:10 ` Srinuvasan A
2021-08-27 13:17 ` Srinuvasan A
2021-09-06 13:48 ` Anton Mikanovich
2021-09-06 18:41 ` Jan Kiszka
2021-09-07 0:18 ` 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=20210826051603.3649442-1-Srinuvasan_A@mentor.com \
--to=srinuvasan_a@mentor.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