Re: Mythmetadatalookup not working in myth 0.25.3

On 4/10/2013 1:14 AM, Kim Bisgaard wrote:
> Hi Stephen,
>
>
>> I've found the culprit /usr/lib/rpm/atrpms/python_burninversion.sh
>
> Great! Nice dig!!
>
>>
>> it seems to be OK on i386 but not x86_64
>
> For completeness sake I have to say it still works fine on Fedora 19 
> x86_64.
>
> On this machine the commands in the script gives these results:
> # which python
> /bin/python
> # python -c "import sys; print sys.version[:3]"
> 2.7
> # which python$python_version | xargs rpm -qlf | grep 
> bin/python$python_version$
> /usr/bin/python
>
>
> How are yours different?
>
> Regards,
> Kim
>
>
>>
>> EL6 with 0.27 is working well. No gotchas so far.
>>
>> cheers
>> Stephen
>>
>>
>> _______________________________________________
>> atrpms-users mailing list
>> [email protected]
>> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>>
>
> _______________________________________________
> atrpms-users mailing list
> [email protected]
> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>
On el6.4 I get
# which python
/usr/bin/python
# python -c "import sys; print sys.version[:3]"
2.6
# which python$python_version | xargs rpm -qlf | grep 
bin/python$python_version$
/usr/bin/python2.6
/usr/bin/python2.6

I found my problem - an x86_64 and i686 versions of python from my dual 
build before moving to mock.

removing it fixed my problem

I imagine the atrpms build system may not have a rpm for python which is 
why the atrpms rpms insert blank in the space.

Cheers
Stephen