From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: "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>,
"Kowalsky,
Clara (FT RPD CED OES-DE)" <clara.kowalsky@siemens.com>,
Liu Yi <liuyi@siemens.com>
Subject: Re: Remove bootstrap support
Date: Mon, 10 Nov 2025 08:39:33 +0100 [thread overview]
Message-ID: <933922dd-2094-4304-a3d8-202c3322ed44@siemens.com> (raw)
In-Reply-To: <152a0f93-841c-484d-acaa-30932fd4d4a4@siemens.com>
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. ;)
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
--
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/933922dd-2094-4304-a3d8-202c3322ed44%40siemens.com.
prev parent reply other threads:[~2025-11-10 7:39 UTC|newest]
Thread overview: 4+ 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 [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=933922dd-2094-4304-a3d8-202c3322ed44@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