From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Morgan Little : python: Update for python-native changes
Date: Mon, 23 Jul 2012 15:06:12 +0200 [thread overview]
Message-ID: <20120723130612.GF3271@jama.jama.net> (raw)
In-Reply-To: <1343048532.21788.95.camel@ted>
[-- Attachment #1: Type: text/plain, Size: 4034 bytes --]
On Mon, Jul 23, 2012 at 02:02:12PM +0100, Richard Purdie wrote:
> On Mon, 2012-07-23 at 13:37 +0200, Martin Jansa wrote:
> > On Mon, Jul 23, 2012 at 12:32:55PM +0100, Richard Purdie wrote:
> > > On Mon, 2012-07-23 at 13:18 +0200, Martin Jansa wrote:
> > > > On Sun, Jul 22, 2012 at 10:43:53AM +0000, git@git.openembedded.org wrote:
> > > > > Module: openembedded-core.git
> > > > > Branch: master
> > > > > Commit: 284a65d55f0ffad0f4f7f32d72da0f9410578643
> > > > > URL: http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=284a65d55f0ffad0f4f7f32d72da0f9410578643
> > > > >
> > > > > Author: Morgan Little <morgan.little@windriver.com>
> > > > > Date: Thu Jul 19 13:46:07 2012 -0400
> > > > >
> > > > > python: Update for python-native changes
> > > > >
> > > > > Add pythonnative onto the list of inherits and update the paths to the binaries
> > > > > referenced in the recipe to the new paths.
> > > > >
> > > > > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > > > >
> > > >
> > > > Any idea why is opkg package-index now failing _sometimes_ ?
> > > >
> > > > | + '[' -e /var/lib/jenkins/jobs/shr-core/workspace/shr-core/tmp-eglibc/deploy/ipk/ ']'
> > > > | + touch /var/lib/jenkins/jobs/shr-core/workspace/shr-core/tmp-eglibc/deploy/ipk/Packages
> > > > | + flock /var/lib/jenkins/jobs/shr-core/workspace/shr-core/tmp-eglibc/deploy/ipk/Packages.flock -c 'opkg-make-index -r /var/lib/jenkins/jobs/shr-core/workspace/shr-core/tmp-eglibc/deploy/ipk/Packages -p /var/lib/jenkins/jobs/shr-core/workspace/shr-core/tmp-eglibc/deploy/ipk/Packages -m /var/lib/jenkins/jobs/shr-core/workspace/shr-core/tmp-eglibc/deploy/ipk/'
> > > > | Traceback (most recent call last):
> > > > | File "/var/lib/jenkins/jobs/shr-core/workspace/shr-core/tmp-eglibc/sysroots/x86_64-linux/usr/lib/python2.7/site.py", line 569, in <module>
> > > > | main()
> > > > | File "/var/lib/jenkins/jobs/shr-core/workspace/shr-core/tmp-eglibc/sysroots/x86_64-linux/usr/lib/python2.7/site.py", line 552, in main
> > > > | known_paths = addsitepackages(known_paths)
> > > > | File "/var/lib/jenkins/jobs/shr-core/workspace/shr-core/tmp-eglibc/sysroots/x86_64-linux/usr/lib/python2.7/site.py", line 329, in addsitepackages
> > > > | for sitedir in getsitepackages():
> > > > | File "/var/lib/jenkins/jobs/shr-core/workspace/shr-core/tmp-eglibc/sysroots/x86_64-linux/usr/lib/python2.7/site.py", line 303, in getsitepackages
> > > > | sitepackages.append(os.path.join(prefix, sys.lib,
> > > > | AttributeError: 'module' object has no attribute 'lib'
> > > > | ERROR: Function failed: do_package_index (see /var/lib/jenkins/jobs/shr-core/workspace/shr-core/tmp-eglibc/work/armv4t-oe-linux-gnueabi/package-index-1.0-r0/temp/log.do_package_index.17223 for further information)
> > > > NOTE: package package-index-1.0-r0: task do_package_index: Failed
> > >
> > > What is the header of opkg-make-index? Is it a path to python or
> > > a /usr/bin/env python?
> >
> > $ head -n1 jobs/shr-core/workspace/shr-core/tmp-eglibc/sysroots/x86_64-linux/usr/bin/opkg-make-index
> > #!/usr/bin/env python
>
> package-index doesn't inherit pythonnative. The python found from env
> would therefore be the host system python but its using files from the
> sysroot. Mixing the two is a bad idea.
>
> The question is how is it mixing these up, the host system python
> shouldn't be looking there for modules.
>
> So I'm not sure why they're getting mixed up but its likely the problem.
> Does anything jump out at you on the machine in question with the above
> in mind?
Not really and it happens only in some builds (all today - haven't seen
this error before) and sofar it failed in 4/10 image/feed builds and
worked in remaining 6.
Even for the same combination of MACHINE and target it once worked and once
failed without any metadata changes or host distro changes between.
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-07-23 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120722104358.0339C10217@opal>
2012-07-23 11:18 ` [oe-commits] Morgan Little : python: Update for python-native changes Martin Jansa
2012-07-23 11:32 ` Richard Purdie
2012-07-23 11:37 ` Martin Jansa
2012-07-23 13:02 ` Richard Purdie
2012-07-23 13:06 ` Martin Jansa [this message]
2012-07-24 7:57 ` Martin Jansa
2012-07-24 8:17 ` Richard Purdie
2012-07-24 8:25 ` Martin Jansa
2012-08-05 10:24 ` [PATCH] opkg-utils: inherit pythonnative Martin Jansa
2012-08-06 9:30 ` Martin Jansa
2012-07-29 12:50 ` [oe-commits] Morgan Little : python: Update for python-native changes Martin Jansa
2012-07-29 16:25 ` 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=20120723130612.GF3271@jama.jama.net \
--to=martin.jansa@gmail.com \
--cc=openembedded-commits@lists.openembedded.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox