[yocto] Problem with Python when running oe-init-build-env

Zoran Stojsavljevic zoran.stojsavljevic at gmail.com
Wed May 2 20:42:23 PDT 2018


 > Advising people to "freeze" their host system and stop taking
security/bugfix updates pushed by their distro is a bad idea.

I already said here that I am ignorant in regards to Centos. I never used
this distro. Please, read again my comments.

In contrary, if I try to compile YOCTO Krogoth with my Fedora 27 host, it
will 100% fail.

Paul, wanna bet on it?! ;-)

Thank you,
Zoran
_______

On Wed, May 2, 2018 at 10:32 PM, Paul Barker <paul at betafive.co.uk> wrote:

> On Wed, 2 May 2018, at 21:17, Zoran Stojsavljevic wrote:
> > Hello Raymond,
> >
> > YOCTO is, per say, moving target. If you have YOCTO Krogoth, you should
> > have somehow frozen host Centos 7 release around this time. As you now
> > moving to Rocko, you need to fast-forward the whole host Centos 7 (in
> other
> > words to upgrade Centos 7) to this state (maybe to latest, it'll still
> > work, I guess).
>
> Sorry, I'd say this is wrong. Centos is a pretty stable base and I
> wouldn't expect backwards incompatible changes to be made within a stable
> release series. So if a Yocto release worked on a given Centos version (say
> Centos 7) at the time of release, it should still work now.
>
> Advising people to "freeze" their host system and stop taking
> security/bugfix updates pushed by their distro is a bad idea.
>
> --
> Paul Barker
> Beta Five Ltd
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20180503/90848033/attachment.html>


More information about the yocto mailing list