On Wed, 2019-10-23 at 22:23 +0300, Adrian Bunk wrote: > On Wed, Oct 23, 2019 at 04:29:13PM +0100, Ross Burton wrote: > > On 23/10/2019 14:03, Khem Raj wrote: > > > Hi Richard > > > > > > New master-next I see these fails > > > > > > https://errors.yoctoproject.org/Errors/Build/91645/ > > > > > > First two are important one's we already know why > > > ti-display-sharing-fw fails to fetch > > > > ERROR: QA Issue: libiio: Files/directories were installed but not > > shipped in > > any package: > > /usr/lib/python2.7 > > /usr/lib/python2.7/site-packages > > /usr/lib/python2.7/site-packages/libiio-0.18-py2.7.egg-info > > /usr/lib/python2.7/site-packages/iio.pyc > > /usr/lib/python2.7/site-packages/iio.py > > > > That may have been triggered by some change in oe-core but that's > > definitely > > an issue with libiio. > > I'd agree on that: > > Python bindings were converted from python2 to python3 last week, > and it picks up the host python 2.7. > > -inherit cmake pythonnative systemd > +inherit cmake python3native systemd > > This does not in any way guarantee that there is no python2 > interpreter > available. > > > WARNING: TOPDIR/build/tmp/work/mips32r2-yoe-linux/python3- > > astor/0.7.1-r0/temp/run.do_configure.7679:1 > > exit 1 from 'NO_FETCH_BUILD=1 TOPDIR/build/tmp/work/mips32r2-yoe- > > linux/python3-astor/0.7.1-r0/recipe-sysroot-native/usr/bin/python3- > > native/python3 > > setup.py clean' > > ERROR: Execution of 'TOPDIR/build/tmp/work/mips32r2-yoe- > > linux/python3-astor/0.7.1-r0/temp/run.do_configure.7679' > > failed with exit code 1: > > Traceback (most recent call last): > > File "setup.py", line 17, in <module> > > setup(**config['options']) > > File "TOPDIR/build/tmp/work/mips32r2-yoe-linux/python3- > > astor/0.7.1-r0/recipe-sysroot-native/usr/lib/python3.7/site- > > packages/setuptools/__init__.py", > > line 145, in setup > > return distutils.core.setup(**attrs) > > > > Looks like whatever astor is doing with setuptools doesn't agree > > with the > > upgrade to 41.4.0? > > The recipe is behind upstream, but even the latest version needs > fixing: > https://github.com/berkerpeksag/astor/issues/162 > > Temporarily broken leaf package, not really important.
Well, yes. The proposed policy is now that we should address these kinds of issues if they get reported. Whilst I understand why and that Khem doesn't get as much help as he needs with meta-oe, pushing the oe- core maintainers to fix things likely won't scale. I would like to see meta-oe quality/reliability improve though so I do understand the desire. Since I'd had to look into them, I've posted patches to oe-devel for the above two issues. Cheers, Richard -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
