Patchwork [1/1] package-index: inherit pythonnative

login
register
mail settings
Submitter Robert Yang
Date July 24, 2012, 10:19 a.m.
Message ID <7affb352c173c353df0b69002f3ca0f5ee0502cf.1343124846.git.liezhi.yang@windriver.com>
Download mbox | patch
Permalink /patch/32921/
State New
Headers show

Comments

Robert Yang - July 24, 2012, 10:19 a.m.
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]

Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
---
 meta/recipes-core/meta/package-index.bb |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)
Richard Purdie - July 24, 2012, 10:49 a.m.
On Tue, 2012-07-24 at 18:19 +0800, Robert Yang wrote:
> 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]
> 
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> ---
>  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
Robert Yang - July 25, 2012, 3:31 a.m.
On 07/24/2012 06:49 PM, Richard Purdie wrote:
> On Tue, 2012-07-24 at 18:19 +0800, Robert Yang wrote:
>> 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]
>>
>> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>> ---
>>   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

> Cheers,
>
> Richard
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
Robert Yang - July 27, 2012, 1:18 a.m.
Hi Richard,

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

On 07/24/2012 06:49 PM, Richard Purdie wrote:
> On Tue, 2012-07-24 at 18:19 +0800, Robert Yang wrote:
>> 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]
>>
>> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>> ---
>>   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


> Cheers,
>
> Richard
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
Robert Yang - July 27, 2012, 10:32 a.m.
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

On 07/27/2012 09:18 AM, Robert Yang wrote:
>
> Hi Richard,
>
> There was something wrong with my mail sever, I resend the answer now.
>
> On 07/24/2012 06:49 PM, Richard Purdie wrote:
>> On Tue, 2012-07-24 at 18:19 +0800, Robert Yang wrote:
>>> 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]
>>>
>>> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>>> ---
>>>   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
>
>
>> Cheers,
>>
>> Richard
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
Martin Jansa - Aug. 6, 2012, 9:29 a.m.
On Tue, Jul 24, 2012 at 11:49:52AM +0100, Richard Purdie wrote:
> On Tue, 2012-07-24 at 18:19 +0800, Robert Yang wrote:
> > 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]
> > 
> > Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> > ---
> >  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,
Richard Purdie - Aug. 7, 2012, 4:57 p.m.
On Mon, 2012-08-06 at 11:29 +0200, Martin Jansa wrote:
> On Tue, Jul 24, 2012 at 11:49:52AM +0100, Richard Purdie wrote:
> > On Tue, 2012-07-24 at 18:19 +0800, Robert Yang wrote:
> > > 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]
> > > 
> > > Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> > > ---
> > >  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.

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
Robert Yang - Aug. 8, 2012, 7:58 a.m.
On 08/08/2012 12:57 AM, Richard Purdie wrote:
> On Mon, 2012-08-06 at 11:29 +0200, Martin Jansa wrote:
>> On Tue, Jul 24, 2012 at 11:49:52AM +0100, Richard Purdie wrote:
>>> On Tue, 2012-07-24 at 18:19 +0800, Robert Yang wrote:
>>>> 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]
>>>>
>>>> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>>>> ---
>>>>   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.
>
> 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

> Cheers,
>
> Richard
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
Robert Yang - Aug. 8, 2012, 8:29 a.m.
On 08/08/2012 03:58 PM, Robert Yang wrote:
>
>
> On 08/08/2012 12:57 AM, Richard Purdie wrote:
>> On Mon, 2012-08-06 at 11:29 +0200, Martin Jansa wrote:
>>> On Tue, Jul 24, 2012 at 11:49:52AM +0100, Richard Purdie wrote:
>>>> On Tue, 2012-07-24 at 18:19 +0800, Robert Yang wrote:
>>>>> 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]
>>>>>
>>>>> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>>>>> ---
>>>>>   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.
>>
>> 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).
>

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

// Robert


> // Robert
>
>> Cheers,
>>
>> Richard
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>>
>

Patch

diff --git a/meta/recipes-core/meta/package-index.bb b/meta/recipes-core/meta/package-index.bb
index 96d54e3..3d7bb7e 100644
--- a/meta/recipes-core/meta/package-index.bb
+++ b/meta/recipes-core/meta/package-index.bb
@@ -1,6 +1,8 @@ 
 DESCRIPTION = "Rebuild the package index"
 LICENSE = "MIT"
 
+inherit pythonnative
+
 INHIBIT_DEFAULT_DEPS = "1"
 ALLOW_EMPTY = "1"
 PACKAGES = ""