<div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jan 27, 2020 at 10:06 AM Khem Raj <<a href="mailto:raj.khem@gmail.com">raj.khem@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, Jan 27, 2020 at 8:54 AM Andrey Zhizhikin <<a href="mailto:andrey.z@gmail.com" target="_blank">andrey.z@gmail.com</a>> wrote:<br>
><br>
> On Mon, Jan 27, 2020 at 4:24 PM Khem Raj <<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>> wrote:<br>
> ><br>
> > Awesome, thanks for the help!<br>
><br>
> No probs!<br>
><br>
> I've actually looked into the list and would have couple of<br>
> components, which are sort-of "python2-only":<br>
> - dnssec-conf: did not receive any update since 9(!) years, written<br>
> totally in python2. Should this be bumped up of bumped out of<br>
> [oe-core]?<br>
<br>
yes meta-python2 is a good place for them if they are primarily<br>
written in python, otherwise retire or blacklist them<br>
</blockquote><div dir="auto"><br></div><div dir="auto">I agree. This is one of use cases for which meta-python2 was created.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> - mozjs: this one pulls the most of dependencies and produces the most<br>
> of errors. It's version is also quite old (60.9.0esr), and there is a<br>
> lot of python2-only code inside. Should this one be bumped out? Latest<br>
> ESR version available upstream is<br>
> 68.4.2esr [1], dated 01/20/2020<br>
><br>
<br>
Andreas is working on it IIRC, we have updated to latest 60.x ESR<br>
but perhaps 68.x might be a path if it addresses py3 migration.<br>
<br>
> For some other recipes I would send out the patch series later today.<br>
><br>
<br>
thanks<br>
<br>
> [1]: <a href="https://archive.mozilla.org/pub/firefox/releases/68.4.2esr/source/" rel="noreferrer" target="_blank">https://archive.mozilla.org/pub/firefox/releases/68.4.2esr/source/</a><br>
><br>
> ><br>
> > On Mon, Jan 27, 2020 at 2:51 AM Andrey Zhizhikin <<a href="mailto:andrey.z@gmail.com" target="_blank">andrey.z@gmail.com</a>> wrote:<br>
> > ><br>
> > > Hello Raj,<br>
> > ><br>
> > > On Fri, Jan 24, 2020 at 8:27 PM Khem Raj <<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>> wrote:<br>
> > > ><br>
> > > > On 1/20/20 8:51 AM, Andrey Zhizhikin wrote:<br>
> > > > > On Mon, Jan 20, 2020 at 4:52 PM Khem Raj <<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>> wrote:<br>
> > > > >><br>
> > > > >> Hi all<br>
> > > > >><br>
> > > > >> Recently py2 is removed from oe-core, So I did quick patches to get a<br>
> > > > >> world build going. And<br>
> > > > >> here are initial failures, please help out with recipes your can or<br>
> > > > >> care for. Eventually, the remaining<br>
> > > > >> ones we can blacklist for 3.1 release.<br>
> > > > >><br>
> > > > >> <a href="http://errors.yoctoproject.org/Errors/Build/97185/" rel="noreferrer" target="_blank">http://errors.yoctoproject.org/Errors/Build/97185/</a><br>
> > > > >><br>
> > > > >> I will post more arches as they become available. If you want to try<br>
> > > > >> the same for machines/distros you can try yoe/mut for meta-oe<br>
> > > > ><br>
> > > > > I've actually asked Ross about similar failures, specifically in<br>
> > > > > [meta-openembeeded/meta-python] where there is a good mix of Pytho2<br>
> > > > > and Python3 still present. I've started to remove those yesterday, and<br>
> > > > > would continue with that layer further.<br>
> > > > ><br>
> > > > >><br>
> > > > >> <a href="https://git.openembedded.org/meta-openembedded-contrib/log/?h=yoe/mut" rel="noreferrer" target="_blank">https://git.openembedded.org/meta-openembedded-contrib/log/?h=yoe/mut</a><br>
> > > > >><br>
> > > ><br>
> > > > All these changes are now in master and its again buildable, with or<br>
> > > > without meta-python2, with meta-python2, its back to where it was with<br>
> > > > everything building however, without py2 layer we have some work to do<br>
> > > > so if you are interested in this here [1] is initial list of failures<br>
> > > > I will keep posting more as we go along.<br>
> > > ><br>
> > ><br>
> > > Thanks a lot for the update! I've actually saw this in the master<br>
> > > before this mail and went ahead with pulling the latest - my builds<br>
> > > for i.MX8M series went fine.<br>
> > ><br>
> > > I'd also have a look at remaining things and try to fix some of those<br>
> > > as I'll progress.<br>
> > ><br>
> > > > [1]<br>
> > > > <a href="https://autobuilder.yoctoproject.org/typhoon/#/builders/88/builds/220/steps/8/logs/errors" rel="noreferrer" target="_blank">https://autobuilder.yoctoproject.org/typhoon/#/builders/88/builds/220/steps/8/logs/errors</a><br>
> > ><br>
> > > --<br>
> > > Regards,<br>
> > > Andrey.<br>
><br>
><br>
><br>
> --<br>
> Regards,<br>
> Andrey.<br>
-- <br>
_______________________________________________<br>
Openembedded-devel mailing list<br>
<a href="mailto:Openembedded-devel@lists.openembedded.org" target="_blank">Openembedded-devel@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-devel" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-devel</a><br>
</blockquote></div></div>