From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"Kiszka, Jan" <jan.kiszka@siemens.com>,
"venkata.pyla@toshiba-tsip.com" <venkata.pyla@toshiba-tsip.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"dinesh.kumar@toshiba-tsip.com" <dinesh.kumar@toshiba-tsip.com>,
"kazuhiro3.hayashi@toshiba.co.jp"
<kazuhiro3.hayashi@toshiba.co.jp>
Subject: Re: [isar-cip-core] Update ISAR revision
Date: Tue, 7 Feb 2023 04:39:39 +0000 [thread overview]
Message-ID: <bfa0ec43563dca91594858896c7e5c2fe751ef03.camel@siemens.com> (raw)
In-Reply-To: <d5ebd21e-547b-1f94-8f38-986aec3ae39c@siemens.com>
On Mon, 2023-02-06 at 14:01 +0100, Jan Kiszka wrote:
> On 06.02.23 12:51, venkata.pyla@toshiba-tsip.com wrote:
> > From: venkata pyla <venkata.pyla@toshiba-tsip.com>
> >
> > Signed-off-by: venkata pyla <venkata.pyla@toshiba-tsip.com>
> > ---
> > kas-cip.yml | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/kas-cip.yml b/kas-cip.yml
> > index b970f39..049eca8 100644
> > --- a/kas-cip.yml
> > +++ b/kas-cip.yml
> > @@ -22,7 +22,7 @@ repos:
> >
> > isar:
> > url: https://github.com/ilbers/isar.git
> > - refspec: fc4f004eb67237d9d09b1ffad0de1a19217fa94a
> > + refspec: 73f0cc16ca50f1102084851b1bc0f2d59925c9ad
> > layers:
> > meta:
> >
>
> I have an update to the latest revision pending, but it is currently
> awaiting an upstream fix. Will bring bitbake 2 then.
With that version, debian bookworm targets are still broken.
The required fixes for at least amd64 are already in next, but
unfortunately after the bitbake 2.0 breaking change. A fix for riscv64
is still waiting to be integrated (I'm the author).
IMHO we should either wait till next is integrated in master, or switch
to next this time. Either way, we have to do the bitbake 2.0 migration.
Having bitbake 2.0 support anyways helps as many downstream layers are
now locked to a broken ISAR version for bookworm: no way forward
because cip-core is not bb2.0, no way backward because of the repo
changes in bookworm and expired keys.
Just bumping the version is not sufficient this time.
PS: putting the ISAR ML in CC to create more awareness on the issue.
Felix
>
> Jan
>
parent reply other threads:[~2023-02-07 4:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <d5ebd21e-547b-1f94-8f38-986aec3ae39c@siemens.com>]
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=bfa0ec43563dca91594858896c7e5c2fe751ef03.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
--cc=venkata.pyla@toshiba-tsip.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