From: Jan Kiszka <jan.kiszka@siemens.com>
To: Baurzhan Ismagulov <ibr@radix50.net>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 1/2] Revert "Revert "isar-init-build-env: Add /sbin to PATH""
Date: Wed, 16 Mar 2022 12:19:42 +0100 [thread overview]
Message-ID: <e9e422c9-858c-536e-3868-6009ecce75ce@siemens.com> (raw)
In-Reply-To: <3cca4fe9-d13c-2555-ea34-f52eb3d113ee@siemens.com>
[Re-adding the list that I dropped]
On 16.03.22 12:18, Jan Kiszka wrote:
> On 16.03.22 09:41, Baurzhan Ismagulov wrote:
>> On Wed, Mar 16, 2022 at 06:06:51AM +0100, Jan Kiszka wrote:
>>> Why this ping-pong, why not fixing it directly? Raspios limitations?
>>> With Debian, it's a no-brainer to use wic for generating Raspi images,
>>> as done multiple times downstream by now.
>>
>> Yes, this is already in our pipe. I'm open to either; that said, the idea was
>> to unblock Vijai first, since it's an error in the current implementation with
>> an obvious fix, and refactor on top. Reimplementation usually requires some
>> stabilization phase. How do you see this?
>
> If we want a quick hack, that should go to the raspi image recipe which
> currently breaks, not this central script.
>
> Jan
>
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-03-16 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 18:40 [PATCH v2 0/2] Fix rpi targets build on Bullseye Anton Mikanovich
2022-03-15 18:40 ` [PATCH v2 1/2] Revert "Revert "isar-init-build-env: Add /sbin to PATH"" Anton Mikanovich
2022-03-16 5:06 ` Jan Kiszka
2022-03-16 5:10 ` Jan Kiszka
2022-03-16 8:41 ` Baurzhan Ismagulov
[not found] ` <3cca4fe9-d13c-2555-ea34-f52eb3d113ee@siemens.com>
2022-03-16 11:19 ` Jan Kiszka [this message]
2022-03-15 18:40 ` [PATCH v2 2/2] rpi-sdimg: Limit volume id value Anton Mikanovich
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=e9e422c9-858c-536e-3868-6009ecce75ce@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=ibr@radix50.net \
--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