From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>,
Srinuvasan A <Srinuvasan_A@mentor.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH v3] debian-common: Add fdisk package as a dependency in wic
Date: Mon, 6 Sep 2021 20:41:56 +0200 [thread overview]
Message-ID: <f5dc1714-0eee-77e5-be30-035d82e0c2ed@siemens.com> (raw)
In-Reply-To: <b4092b44-4196-c168-0fee-2953cdcfd566@ilbers.de>
On 06.09.21 15:48, Anton Mikanovich wrote:
> 27.08.2021 16:17, Srinuvasan A wrote:
>> From: Srinuvasan A <srinuvasan_a@mentor.com>
>>
>> In downstream 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.
>>
>> To reproduce this issue in upstream we triggered the de0-nano-soc build
>> with --system-id option enabled in wks.in file, this issue present in
>> upstream build hence added the dependency package fdisk to the wic
>> imager install.
>>
>> Ref commit for de0-nano-soc.wks.in: c8eb30bfbff4
>>
>> Signed-off-by: Srinuvasan A <srinuvasan_a@mentor.com>
>
> This will fail in stretch, because there is no such a package in it.
> sfdisk was already included in util-linux, but moved to separate fdisk
> package started from buster.
>
WIC_IMAGER_INSTALL_remove_stretch = "fdisk"
should fix that and can easily be dropped when we retire stretch.
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-09-06 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 5:16 [PATCH] " Srinuvasan A
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 [this message]
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=f5dc1714-0eee-77e5-be30-035d82e0c2ed@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Srinuvasan_A@mentor.com \
--cc=amikan@ilbers.de \
--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