From: Srinuvasan Arjunan <srinuvasanasv@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: 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: Tue, 7 Sep 2021 05:48:40 +0530 [thread overview]
Message-ID: <CAB2Z2nNY6bC+qGSZnxMwc=5i+Pq4amafRPKLegGuPQXL+1tXPw@mail.gmail.com> (raw)
In-Reply-To: <f5dc1714-0eee-77e5-be30-035d82e0c2ed@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]
Sure jan, will send next version of patch soon.
Many thanks,
Srinuvasan.A
On Tue, 7 Sep, 2021, 12:11 am Jan Kiszka, <jan.kiszka@siemens.com> wrote:
> 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
>
> --
> 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 on the web visit
> https://groups.google.com/d/msgid/isar-users/f5dc1714-0eee-77e5-be30-035d82e0c2ed%40siemens.com
> .
>
[-- Attachment #2: Type: text/html, Size: 2771 bytes --]
prev parent reply other threads:[~2021-09-07 0:18 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
2021-09-07 0:18 ` Srinuvasan Arjunan [this message]
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='CAB2Z2nNY6bC+qGSZnxMwc=5i+Pq4amafRPKLegGuPQXL+1tXPw@mail.gmail.com' \
--to=srinuvasanasv@gmail.com \
--cc=Srinuvasan_A@mentor.com \
--cc=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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