From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "chombourger@gmail.com" <chombourger@gmail.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: wic missing squashfs
Date: Wed, 18 Dec 2024 10:09:30 +0000 [thread overview]
Message-ID: <671e7ea932648d1aae04cd4a3e7417bba07bf2f3.camel@siemens.com> (raw)
In-Reply-To: <8b76866b-866c-4412-8b7c-f13db0aca2c5n@googlegroups.com>
On Tue, 2024-12-17 at 12:50 -0800, Cedric Hombourger wrote:
>
>
> Le jeudi 5 décembre 2024 à 15:55:35 UTC+1, Uladzimir Bely a écrit :
> > On Thu, 2024-12-05 at 06:47 -0800, Stephen Ecker wrote:
> > > I keep getting this error:
> > >
> > > | ERROR: A native program mksquashfs required to build the image
> > > was
> > > not found (see details above).
> > > |
> > > | Please make sure wic-tools have squashfs-tools-native in its
> > > DEPENDS, build it with 'bitbake wic-tools' and try again.
> > > |
> > >
> > > I have tried adding squashfs-tools-native to WKS_FILE_DEPENDS,
> > > but I
> > > get the same error. any thoughts?
> >
> > Hello.
> >
> > Try using IMAGER_INSTALL:wic += "squashfs-tools"
>
>
> I have recently run into this (and did this in my layer)
>
> IMO the wic imager should pre-install packages for everything file-
> systems it supports / usable in .wks files. I was going to submit a
> patch along these lines so that I could get rid of this directive in
> my downstream layer. Should I? This would improve usability / user-
> experience if you ask me.
Hmm... I tend to disagree. Installing these tools takes time and
increases the attack surface of the build itself. By that we basically
penalize all users just because it makes things a bit easier for some.
Best regards,
Felix
>
> Thanks
> Cedric
>
> >
> > > --
> > > 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+...@googlegroups.com.
> > > To view this discussion visit
> > > https://groups.google.com/d/msgid/isar-users/2839131c-156b-4007-b424-854d267cb0abn%40googlegroups.com
> >
> > > .
> >
> > --
> > Best regards,
> > Uladzimir.
> >
> >
> >
--
Siemens AG, Technology
Linux Expert Center
--
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 visit https://groups.google.com/d/msgid/isar-users/671e7ea932648d1aae04cd4a3e7417bba07bf2f3.camel%40siemens.com.
next prev parent reply other threads:[~2024-12-18 10:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AQHbRyTqrCt+jfW9CEqVGNtHexJeRrLXvSmAgBM/NgCAAN8wgA==>
2024-12-05 14:47 ` Stephen Ecker
2024-12-05 14:55 ` Uladzimir Bely
2024-12-17 20:50 ` Cedric Hombourger
2024-12-18 10:09 ` 'MOESSBAUER, Felix' via isar-users [this message]
2024-12-18 19:12 ` Cedric Hombourger
2024-12-19 12:00 ` 'MOESSBAUER, Felix' via isar-users
2024-12-19 14:13 ` Roberto A. Foglietta
2024-12-19 14:38 ` 'Jan Kiszka' via isar-users
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=671e7ea932648d1aae04cd4a3e7417bba07bf2f3.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=chombourger@gmail.com \
--cc=felix.moessbauer@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