From: "'Clara Kowalsky' via isar-users" <isar-users@googlegroups.com>
To: "Liu, Yi (FT RPD CED INW-CN)" <liuyi@siemens.com>,
"Kiszka, Jan (FT RPD CED)" <jan.kiszka@siemens.com>
Cc: "Moessbauer,
Felix (FT RPD CED OES-DE)" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"ibr@ilbers.de" <ibr@ilbers.de>
Subject: Re: Remove bootstrap support
Date: Tue, 11 Nov 2025 16:27:50 +0100 [thread overview]
Message-ID: <19c1629b-bdb4-4b33-b711-04a0223c5785@siemens.com> (raw)
In-Reply-To: <AS2PR10MB69274E05ECAB994AB60410BFBFCFA@AS2PR10MB6927.EURPRD10.PROD.OUTLOOK.COM>
On 11/11/25 09:03, Liu, Yi (FT RPD CED INW-CN) wrote:
>> -----Original Message-----
>> From: Kiszka, Jan (FT RPD CED) <jan.kiszka@siemens.com>
>> Sent: Monday, November 10, 2025 3:40 PM
>> To: Moessbauer, Felix (FT RPD CED OES-DE)
>> <felix.moessbauer@siemens.com>; isar-users@googlegroups.com;
>> ibr@ilbers.de; Kowalsky, Clara (FT RPD CED OES-DE)
>> <clara.kowalsky@siemens.com>; Liu, Yi (FT RPD CED INW-CN)
>> <liuyi@siemens.com>
>> Subject: Re: Remove bootstrap support
>>
>> On 06.11.25 17:46, 'Jan Kiszka' via isar-users wrote:
>>> On 06.11.25 17:01, Moessbauer, Felix (FT RPD CED OES-DE) wrote:
>>>> On Wed, 2025-11-05 at 14:11 +0100, 'Clara Kowalsky' via isar-users
>>>> wrote:
>>>>> Hi,
>>>>>
>>>>> I noticed that with kas 5.0 debian-trixie and using own keys in
>>>>> isar-bootstrap, one runs into the issue that apt-key is deprecated
>>>>> with trixie.
>>>>>
>>>>> With:
>>>>> +PREFERRED_PROVIDER_bootstrap-host ??= "isar-bootstrap-host"
>>>>> +PREFERRED_PROVIDER_bootstrap-target ??= "isar-bootstrap-target"
>>>>> & setting e.g., HOST_DISTRO_BOOTSTRAP_KEYS for the
>>>>> isar-bootstrap-host target, the do_generate_keyrings task returns an
>>>>> error:
>>>>> sudo: apt-key: command not found
>>>>
>>>> That's a bug...
>>>>
>>>>>
>>>>> The isar testsuite is not covering isar-bootstrap.
>>>>>
>>>>> The question is, is the support of bootstrap even needed nowadays or
>>>>> can it be removed from isar?
>>>>
>>>> I also expected that we can sunset the old bootstrap implementation,
>>>> but apparently this implementation just got a patch so that it can be
>>>> used for building openKylinOS via ISAR [1]. Looks like we still have
>>>> users on it.
>>>>
>>>> [1] "bitbake: Move the preferred bootstrap assignment before
>>>> including local.conf"
>>>>
>>>
>>> Before blocking the removal of this untested legacy code due to some
>>> not-yet-upstream-proposed extension, I would like to first of all see
>>> that extension proposed and secondly get explained why openKylinOS
>>> does not work with mmdebstrap. Or does it bring its own bootstrap?
>>>
>>
>> Ping - specifically to our openKylinOS expect. ;)
>
>
> OpenKylinOS does support build its own rootfs through both debootstrap and mmdebstrap.
> It just got failed when building via ISAR with mmdebstrap.
>
> I am trying to figure out why it happens.
>
> Dropping isar-bootstrap might affect building OpenkylinOS in the short term, but eventually it
> will work with mmdebstrap.
>
> Liu Yi
This should not be a showstopper.>
>>
>> There are only two options:
>> A) fix the isar-bootstrap issue Clara found AND re-add isar-bootstrap
>> to some tests
>> B) drop isar-bootstrap, maybe only leaving bootstrap-host/target for
>> now so that downstream can still override where needed
>>
>> Leaving things as they are or only doing half of option A) are no alternatives.
>>
>> Jan
>>
>> --
>> Siemens AG, Foundational Technologies
>> Linux Expert Center
So far, no one has come forward who absolutely needs isar-bootstrap.
With that, I would go with option B and send the patch to remove
isar-bootstrap support.
Best regards,
Clara
--
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/19c1629b-bdb4-4b33-b711-04a0223c5785%40siemens.com.
prev parent reply other threads:[~2025-11-11 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 13:11 'Clara Kowalsky' via isar-users
2025-11-06 16:01 ` 'MOESSBAUER, Felix' via isar-users
2025-11-06 16:46 ` 'Jan Kiszka' via isar-users
2025-11-10 7:39 ` 'Jan Kiszka' via isar-users
2025-11-11 8:03 ` 'Liu, Yi' via isar-users
2025-11-11 15:27 ` 'Clara Kowalsky' via isar-users [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=19c1629b-bdb4-4b33-b711-04a0223c5785@siemens.com \
--to=isar-users@googlegroups.com \
--cc=clara.kowalsky@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=ibr@ilbers.de \
--cc=jan.kiszka@siemens.com \
--cc=liuyi@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