From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>,
Anton Mikanovich <amikan@ilbers.de>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
cip-dev <cip-dev@lists.cip-project.org>
Subject: Re: Debian Buster support in Isar
Date: Mon, 17 Jul 2023 13:29:54 +0200 [thread overview]
Message-ID: <6d2d0898-33ff-b4d2-fa71-7be495cb6026@siemens.com> (raw)
In-Reply-To: <20230717132131.4b579430@md1za8fc.ad001.siemens.net>
On 17.07.23 13:21, 'Henning Schild' via isar-users wrote:
> Am Thu, 13 Jul 2023 18:06:17 +0300
> schrieb Anton Mikanovich <amikan@ilbers.de>:
>
>> Hi all,
>>
>> Debian Buster will become End of life this September, and it already
>> started feeling like something needs to be separately care about,
>> just like we had previously with a lot of Debian Stretch hacks.
>> We already experience cross-building issues on qemumipsel-buster and
>> dropped stm32mp15x-buster due to optee compatibility issues.
>>
>> Did anyone use Isar with Debian Buster targets in downstreams
>> currently?
>
> In Siemens we still have a demand for Buster, not to underestimate in
> size/number of layers. We should for sure support it in Isar at least
> until its EndOfLife.
>
> But probably not much longer, people still using it might be on an
> older Isar anyhow.
Exactly. I suspect we have not too much overlap here with "latest Isar"
and "oldoldstable Debian".
The biggest issue will more likely be around isar-cip-core where we try
to address with one layer multiple Debian versions. We may have to scope
down or also drop buster support there.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2023-07-17 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 15:06 Anton Mikanovich
2023-07-17 11:21 ` Henning Schild
2023-07-17 11:29 ` Jan Kiszka [this message]
2023-07-17 11:34 ` Anton Mikanovich
2024-08-01 7:52 ` 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=6d2d0898-33ff-b4d2-fa71-7be495cb6026@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=amikan@ilbers.de \
--cc=cip-dev@lists.cip-project.org \
--cc=henning.schild@siemens.com \
--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