Dunfell Update Status

[Andrew Geissler]

> On May 8, 2020, at 5:12 PM, Vijay Khemka <vijaykhemka at fb.com> wrote:
> 
> Do we need to install or upgrade any package in our build system to build this new dunfel.
> I am seeing lots of build error starting from sanity checker. My build machine is centos 
> CentOS Linux release 7.7.1908.

The main thing that bit us was we needed gcc 6 or greater but that was a
pretty obvious error bitbake spit out before it started building anything.

If you have docker installed you could run the build-setup.sh script
that CI uses to verify all builds well with that.
https://github.com/openbmc/openbmc-build-scripts/blob/master/build-setup.sh 

> 
> On 5/5/20, 1:06 PM, "openbmc on behalf of Gunnar Mills" <openbmc-bounces+vijaykhemka=fb.com at lists.ozlabs.org on behalf of gmills at linux.vnet.ibm.com> wrote:
> 
>    On 5/5/2020 12:38 PM, Andrew Geissler wrote:
>> An update on the email below. Upstream yocto (including the new Dunfell release)
>> went into openbmc master this morning with the following commit:
>> 
>> https://github.com/openbmc/openbmc/commit/82c905dc58a36aeae40b1b273a12f63fb1973cf4
>> 
>> 
>> Now that we’re past the python3 migration issue, we’ll be doing rebases
>> on upstream yocto once a week again (which should prevent needing
>> big painful updates like this).
>    Awesome!
> 
>>> On Apr 28, 2020, at 2:05 PM, Andrew Geissler <geissonator at gmail.com> wrote:
>>> 
>>> A fairly quick update on where we are with getting back onto upstream yocto.
>>> 
>>> For those that don’t know, dunfell is the name of the next yocto release.
>>> 
>>> The move from python2 to python3 is mostly behind us, thanks everyone,
>>> especially Patrick (stwcx) for all the help there.
>>> 
>    Thank you Andrew for driving this and to everyone who helped!
> 
>