Re: [PATCH 1/3] bitbake: Update to fixed master revision

[Henning Schild <henning.schild@siemens.com>]

Am Thu, 22 Nov 2018 15:28:06 +0100
schrieb Jan Kiszka <jan.kiszka@siemens.com>:

> On 22.11.18 14:58, Henning Schild wrote:
> > Am Thu, 22 Nov 2018 14:25:25 +0100
> > schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> >   
> >> On 22.11.18 14:18, Henning Schild wrote:  
> >>> Am Thu, 22 Nov 2018 14:14:11 +0100
> >>> schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> >>>      
> >>>> On 22.11.18 14:12, Henning Schild wrote:  
> >>>>> I got a report that bitbake 1.40 and this one are affected by a
> >>>>> "gitsm://" bug. Still waiting for details but this will only fix
> >>>>> one new bitbake bug.
> >>>>> Was there a reason to bump, except wanting to stay up to date?  
> >>>>
> >>>> Broken multiconfig in current next. So far a downstream issue
> >>>> (jailhouse-images, possibly other multiconfig-using layers), with
> >>>> patch 3 then also an upstream topic. But patch 3 is needed for
> >>>> other reasons (see log).  
> >>>
> >>> Is that the answer to 1.37->1.40 or just 1.40 -> this ?
> >>>      
> >>
> >> The step 1.37->1.40 caused the multiconfig problem
> >> (http://lists.openembedded.org/pipermail/bitbake-devel/2018-November/019558.html)
> >> that is now fixed with this update again.  
> > 
> > I got that, i was already thinking about going back to 1.37 ...
> > maybe.  
> 
> Well, if we cannot sort out the gitsm issue AND it is blocking for
> you, I would consider that.

gitsm thing is known upstream and we can work around it by adjusting
out .gitmodules, bet seems we need one of the changes this patch
includes.

So i guess it is solved and we want this one merged fast ;).

http://lists.openembedded.org/pipermail/bitbake-devel/2018-November/019532.html

Henning

> Jan
>