Re: [isar-cip-core] Update ISAR revision

Re: [isar-cip-core] Update ISAR revision

[Moessbauer, Felix]

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
>