Skip to contentSkip to conversation

package-index: inherit pythonnative

PATCH In review Robert Yang 3 participants 10 messages Jul 24, 2012 – Aug 8, 2012

lore
Share & tools
lore
#0 lore raw

cover package-index: inherit pythonnative

This is used for fixing the rpm-createsolvedb.py error:

'import site' failed; use -v for traceback
Traceback (most recent call last):
File "/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly/build/scripts/rpm-createsolvedb.py", line 14, in import sys, os
ImportError: No module named os

// Robert

The following changes since commit 0ffb02eec2beaea27ff0ec9d3d31b0a09e675a4c:

documentation: Updated the h6 style to use a larger font (2012-07-24 10:35:34 +0100)

are available in the git repository at:
git://git.pokylinux.org/poky-contrib robert/package_index
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/package_index

Robert Yang (1):
package-index: inherit pythonnative

 meta/recipes-core/meta/package-index.bb |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)
#1 lore raw

PATCH 1/1 package-index: inherit pythonnative

The native python binary has been moved from usr/bin/python to usr/bin/python-native/python, the recipe which needs python-native should "inherit pythonnative", otherwise there would be errors when the python script runs.

[YOCTO #2822]

---
 meta/recipes-core/meta/package-index.bb |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)
meta/recipes-core/meta/package-index.bb +2 -0
index 96d54e3..3d7bb7e 100644
@@ -1,6 +1,8 @@
 DESCRIPTION = "Rebuild the package index"
 LICENSE = "MIT"
 
+inherit pythonnative
+
 INHIBIT_DEFAULT_DEPS = "1"
 ALLOW_EMPTY = "1"
 PACKAGES = ""
Signature · 1 line
1.7.1
#2 lore raw
Quoted 11 lines · Robert Yang

The native python binary has been moved from usr/bin/python to usr/bin/python-native/python, the recipe which needs python-native should "inherit pythonnative", otherwise there would be errors when the python script runs.

[YOCTO #2822]

---
 meta/recipes-core/meta/package-index.bb |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

Which part of this recipe needs python-native? Shouldn't scripts which need pythonnative be using the path to the python interpreter explicitly?

Cheers,

Richard

#3 lore raw
Quoted 8 lines · Richard Purdie
Quoted 7 lines · Robert Yang

The native python binary has been moved from usr/bin/python to usr/bin/python-native/python, the recipe which needs python-native should "inherit pythonnative", otherwise there would be errors when the python script runs.

[YOCTO #2822]

Quoted 9 lines
Quoted 4 lines
---
  meta/recipes-core/meta/package-index.bb |    2 ++
  1 files changed, 2 insertions(+), 0 deletions(-)

Which part of this recipe needs python-native? Shouldn't scripts which need pythonnative be using the path to the python interpreter explicitly?

It is the poky/scripts/rpm-createsolvedb.py which needs python-native, I think that if we want to use /path/to/python-native/python to run rpm-createsolvedb.py or create a wrapper for it, we should put the rpm-createsolvedb.py into a recipe. So I just inherit pythonnative in package-index.bb to make it work. I wonder whether this will cause something wrong, please?

// Robert

Quoted 11 lines

Cheers,

Richard

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

#4 lore raw
In reply to Richard Purdie

Hi Richard,

There was something wrong with my mail sever, I resend the answer now.

Quoted 8 lines · Richard Purdie
Quoted 7 lines · Robert Yang

The native python binary has been moved from usr/bin/python to usr/bin/python-native/python, the recipe which needs python-native should "inherit pythonnative", otherwise there would be errors when the python script runs.

[YOCTO #2822]

Quoted 9 lines
Quoted 4 lines
---
  meta/recipes-core/meta/package-index.bb |    2 ++
  1 files changed, 2 insertions(+), 0 deletions(-)

Which part of this recipe needs python-native? Shouldn't scripts which need pythonnative be using the path to the python interpreter explicitly?

It is the poky/scripts/rpm-createsolvedb.py which needs python-native, I think that if we want to use /path/to/python-native/python to run rpm-createsolvedb.py or create a wrapper for it, we should put the rpm-createsolvedb.py into a recipe. So I just inherit pythonnative in package-index.bb to make it work. I wonder whether this will cause something wrong, please?

// Robert

Quoted 11 lines

Cheers,

Richard

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

#5 lore raw

After talk with Richard, we'd better move the scripts/rpm-createsolvedb.py to meta/recipes-support/createrepo/createrepo_0.4.11.bb, I will send an update sooner, the current fix can be a workaround.

// Robert

Quoted 53 lines · Robert Yang

Hi Richard,

There was something wrong with my mail sever, I resend the answer now.

Quoted 8 lines · Richard Purdie
Quoted 7 lines · Robert Yang

The native python binary has been moved from usr/bin/python to usr/bin/python-native/python, the recipe which needs python-native should "inherit pythonnative", otherwise there would be errors when the python script runs.

[YOCTO #2822]

Quoted 9 lines
Quoted 4 lines
---
  meta/recipes-core/meta/package-index.bb |    2 ++
  1 files changed, 2 insertions(+), 0 deletions(-)

Which part of this recipe needs python-native? Shouldn't scripts which need pythonnative be using the path to the python interpreter explicitly?

It is the poky/scripts/rpm-createsolvedb.py which needs python-native, I think that if we want to use /path/to/python-native/python to run rpm-createsolvedb.py or create a wrapper for it, we should put the rpm-createsolvedb.py into a recipe. So I just inherit pythonnative in package-index.bb to make it work. I wonder whether this will cause something wrong, please?

// Robert

Quoted 11 lines

Cheers,

Richard

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

#6 lore raw
In reply to Richard Purdie
Quoted 8 lines · Richard Purdie
Quoted 7 lines · Robert Yang

The native python binary has been moved from usr/bin/python to usr/bin/python-native/python, the recipe which needs python-native should "inherit pythonnative", otherwise there would be errors when the python script runs.

[YOCTO #2822]

Quoted 8 lines
Quoted 4 lines
---
 meta/recipes-core/meta/package-index.bb |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

Which part of this recipe needs python-native? Shouldn't scripts which need pythonnative be using the path to the python interpreter explicitly?

This fixes my opkg-utils related issues too
http://lists.linuxtogo.org/pipermail/openembedded-core/2012-July/026333.html

The problem is that with pythonnative in opkg-utils it's still using #!/usr/bin/env python
in tmp-eglibc/sysroots/x86_64-linux/usr/bin/opkg-make-index

And when python-index executes this:

| + [ -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):

It depends on PATH of package-index not opkg-utils.

Cheers,

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#7 lore raw
Quoted 25 lines · Martin Jansa
Quoted 8 lines · Richard Purdie
Quoted 7 lines · Robert Yang

The native python binary has been moved from usr/bin/python to usr/bin/python-native/python, the recipe which needs python-native should "inherit pythonnative", otherwise there would be errors when the python script runs.

[YOCTO #2822]

Quoted 8 lines
Quoted 4 lines
---
 meta/recipes-core/meta/package-index.bb |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

Which part of this recipe needs python-native? Shouldn't scripts which need pythonnative be using the path to the python interpreter explicitly?

This fixes my opkg-utils related issues too
http://lists.linuxtogo.org/pipermail/openembedded-core/2012-July/026333.html

The problem is that with pythonnative in opkg-utils it's still using #!/usr/bin/env python
in tmp-eglibc/sysroots/x86_64-linux/usr/bin/opkg-make-index

Quoted 7 lines

And when python-index executes this:

| + [ -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):

It depends on PATH of package-index not opkg-utils.

I think the right fix here is to remove the PYTHONPATH line in package-index.bb. We should no longer need that and that should fix the problems but its going to be a while before I can test this on a system showing the problem.

Cheers,

Richard

#8 lore raw
Quoted 32 lines · Richard Purdie
Quoted 31 lines · Martin Jansa
Quoted 8 lines · Richard Purdie
Quoted 7 lines · Robert Yang

The native python binary has been moved from usr/bin/python to usr/bin/python-native/python, the recipe which needs python-native should "inherit pythonnative", otherwise there would be errors when the python script runs.

[YOCTO #2822]

Quoted 8 lines
Quoted 4 lines
---
  meta/recipes-core/meta/package-index.bb |    2 ++
  1 files changed, 2 insertions(+), 0 deletions(-)

Which part of this recipe needs python-native? Shouldn't scripts which need pythonnative be using the path to the python interpreter explicitly?

This fixes my opkg-utils related issues too
http://lists.linuxtogo.org/pipermail/openembedded-core/2012-July/026333.html

The problem is that with pythonnative in opkg-utils it's still using #!/usr/bin/env python
in tmp-eglibc/sysroots/x86_64-linux/usr/bin/opkg-make-index

And when python-index executes this:

| + [ -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):
Quoted 7 lines
Quoted 1 line

It depends on PATH of package-index not opkg-utils.

I think the right fix here is to remove the PYTHONPATH line in package-index.bb. We should no longer need that and that should fix the problems but its going to be a while before I can test this on a system showing the problem.

Hi Richard

I'd like to remove the PYTHONPATH and started testing package_rpm, package_deb pacakge_ipk now (meta-toolchain-sdk and core-image-sato), I will send the the patch if the testing is ok (tomorrow).

// Robert

Quoted 11 lines

Cheers,

Richard

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

#9 lore raw
Quoted 51 lines · Robert Yang
Quoted 40 lines · Richard Purdie
Quoted 39 lines · Martin Jansa
Quoted 8 lines · Richard Purdie
Quoted 7 lines · Robert Yang

The native python binary has been moved from usr/bin/python to usr/bin/python-native/python, the recipe which needs python-native should "inherit pythonnative", otherwise there would be errors when the python script runs.

[YOCTO #2822]

Quoted 8 lines
Quoted 4 lines
---
  meta/recipes-core/meta/package-index.bb |    2 ++
  1 files changed, 2 insertions(+), 0 deletions(-)

Which part of this recipe needs python-native? Shouldn't scripts which need pythonnative be using the path to the python interpreter explicitly?

This fixes my opkg-utils related issues too
http://lists.linuxtogo.org/pipermail/openembedded-core/2012-July/026333.html

The problem is that with pythonnative in opkg-utils it's still using #!/usr/bin/env python
in tmp-eglibc/sysroots/x86_64-linux/usr/bin/opkg-make-index

And when python-index executes this:
| + [ -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):

Quoted 7 lines
Quoted 1 line

It depends on PATH of package-index not opkg-utils.

I think the right fix here is to remove the PYTHONPATH line in package-index.bb. We should no longer need that and that should fix the problems but its going to be a while before I can test this on a system showing the problem.

Quoted 6 lines

Hi Richard

I'd like to remove the PYTHONPATH and started testing package_rpm, package_deb pacakge_ipk now (meta-toolchain-sdk and core-image-sato), I will send the the patch if the testing is ok (tomorrow).

Just noticed that it has been removed after a 'git pull'

// Robert

Quoted 14 lines

// Robert

Quoted 11 lines

Cheers,

Richard

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core