public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: RE: [PATCH v2] meta: Add Debian Trixie
Date: Thu, 25 Jan 2024 12:01:28 +0000	[thread overview]
Message-ID: <AS4PR10MB53186C770A2587D99916EBA0ED7A2@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <10826eb3-53a3-400f-863e-de577c557927@ilbers.de>

Anton Mikanovich <amikan@ilbers.de>, Thursday, January 25, 2024 12:13 PM:
> 25/01/2024 12:53, Schmidt, Adriaan wrote:
> > Trixie does not yet provide any RT kernel packages. [1]
> > I experimented with building trixie images, and ended up adding the
> bookworm-backports
> > repository to get a RT Kernel.
> >
> > Adriaan
> >
> > [1] https://packages.debian.org/search?keywords=linux-image-rt-amd64
> 
> Hello, Adriaan.
> 
> Thanks for this notice. I was checking available kernels during prepare
> v1, but
> probably missed rt kernels (or can they be removed?).
> Will recheck the list in next patch version.

Hi Anton,

In general, we want/need the rt kernels.

With the current state, I don't think Isar should be "fixing" this (e.g., by
automatically adding another deb repo providing the rt kernels), but instead
anyone wanting to use Trixie+rt at this time needs to address this downstream.

So for Isar, the question is just about how such builds would fail.
I guess the clean thing would be to correctly reflect what's there,
so remove the rt kernels from DISTRO_KERNELS and add them back once the packages
are provided by Trixie. Then builds trying Trixie+rt now would fail early in 
bitbake because "nothing provides linux-image-rt-amd64".

Or the dirty approach, ignore the problem, it should fix itself over time...
Then trying to build Trixie+rt now would fail when apt can't find linux-image-rt-*.

I think either way would be fine. Just maybe document that limitation.

Adriaan


  reply	other threads:[~2024-01-25 12:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25 10:29 Anton Mikanovich
2024-01-25 10:53 ` Schmidt, Adriaan
2024-01-25 11:13   ` Anton Mikanovich
2024-01-25 12:01     ` Schmidt, Adriaan [this message]
2024-03-11  9:48       ` Anton Mikanovich
2024-03-13  6:44         ` Schmidt, Adriaan

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=AS4PR10MB53186C770A2587D99916EBA0ED7A2@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM \
    --to=adriaan.schmidt@siemens.com \
    --cc=amikan@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