All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: new meta-oe failures from master-next
Date: Wed, 23 Oct 2019 16:29:13 +0100	[thread overview]
Message-ID: <40c36a7b-6e95-efc8-4ab0-6b9e19924e54@intel.com> (raw)
In-Reply-To: <CAMKF1sq83g8Zu3FmqWtdpJAePA6XsGnWZ5Z6HN9A6YvT8Socjw@mail.gmail.com>

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.

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?

Ross


  parent reply	other threads:[~2019-10-23 15:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23 13:03 new meta-oe failures from master-next Khem Raj
2019-10-23 13:05 ` Khem Raj
2019-10-23 15:58   ` akuster808
2019-10-23 15:29 ` Ross Burton [this message]
2019-10-23 19:23   ` Adrian Bunk
2019-10-23 21:20     ` Richard Purdie
2019-10-23 22:08       ` Adrian Bunk
2019-10-23 19:31   ` Richard Purdie
2019-10-23 22:52     ` Khem Raj
2019-10-24  6:37       ` Khem Raj
2019-10-24  8:15       ` richard.purdie
2019-10-24  8:20         ` Khem Raj
2019-10-24  8:25           ` richard.purdie
2019-10-24  8:34             ` Khem Raj
2019-10-24  9:34               ` richard.purdie
2019-10-24  9:34         ` Adrian Bunk
2019-10-24  9:43           ` richard.purdie
2019-10-23 16:22 ` richard.purdie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40c36a7b-6e95-efc8-4ab0-6b9e19924e54@intel.com \
    --to=ross.burton@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.