From: Anton Mikanovich <amikan@ilbers.de>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: Freezing for the following Isar release
Date: Wed, 23 Apr 2025 12:44:00 +0300 [thread overview]
Message-ID: <a4a69921-5c18-44f4-817d-8ab5573d3c80@ilbers.de> (raw)
In-Reply-To: <563a7d69-e143-4fbb-b184-1dc059f318d9@ilbers.de>
We've dropped imx6-sabrelite deprecation patch from release plan because
it is
changing metadata which cause CI issues. Updated v2 of it will be merged
right
after the release.
The patch with sstate tasks skipping is also not ready jet to be merged
as-is
right before the release.
All the others are already under the v0.11-rc1 tag.
Known issues update:
- libubootenv can't be built on de0-nano-soc-buster target because of 13
compat
level requirement.
- Dependencies issue cause qemumipsel-bullseye build failure.
- Target qemuarm-trixie unable to find rootfs on startvm test case.
- Target qemuamd64-sb-bullseye fails example module load check during
startvm
test case.
- Target qemuriscv64-trixie use deprecated QEMU_CPU variable, so startvm
test
case fails on QEMU call.
--
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/a4a69921-5c18-44f4-817d-8ab5573d3c80%40ilbers.de.
prev parent reply other threads:[~2025-04-23 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 12:37 Anton Mikanovich
2025-04-10 12:54 ` 'MOESSBAUER, Felix' via isar-users
2025-04-23 9:44 ` Anton Mikanovich [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=a4a69921-5c18-44f4-817d-8ab5573d3c80@ilbers.de \
--to=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=ibr@ilbers.de \
--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