[gentoo-user] How can I force emerge to use python 3.6?

[gentoo-user] How can I force emerge to use python 3.6?

[William Kenworthy]

[-- Attachment #1: Type: text/plain, Size: 307 bytes --]

How can I force emerge to use python 3.6 when 3.7 is installed? -
eselect list shows 3.6 is #1 and 3.7 as fallback so that doesn't work.

I am trying to narrow down a failure which appears to be a combination
of building packages that are stored on a moosefs network share and
python 3.7

BillK



[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 2225 bytes --]

Re: [gentoo-user] How can I force emerge to use python 3.6?

[Victor Ivanov]

[-- Attachment #1.1: Type: text/plain, Size: 1079 bytes --]

Why do you think emerge might be the issue? It's quite rare for portage
itself to be causing problems with packages.

That said, if you have good reason to believe so you can adjust the
PYTHON_TARGETS for sys-apps/portage in /etc/portage/package.use like so:

    sys-apps/portage PYTHON_TARGETS: +python3_6 -python3_7

Or you can keep both. You will of course need to rebuild portage
following this change.

Likewise, you use the syntax of the above entry to adjust the python
targets for any package.

Your default interpreter choice (as reported by eselect) is likely not
respected by portage because the current profile defaults only build
portage against python 3.7.

- Victor

On 16/05/2020 02:32, William Kenworthy wrote:
> How can I force emerge to use python 3.6 when 3.7 is installed? -
> eselect list shows 3.6 is #1 and 3.7 as fallback so that doesn't work.
> 
> I am trying to narrow down a failure which appears to be a combination
> of building packages that are stored on a moosefs network share and
> python 3.7
> 
> BillK
> 
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] How can I force emerge to use python 3.6?

[William Kenworthy]

[-- Attachment #1: Type: text/plain, Size: 1785 bytes --]

Hi Victor,

    emerge crashes when it tries to add metadata during the merge stage
in an emerge installed python module using 3.7 when the PKGDIR is on a
moosefs share.  When PKGDIR is local its fine.

I am rebuilding some systems now with 3.6 as the PYTHON_SINGLE_TARGET
but I was hoping for some way to specify emerge use 3.7 or 3.6 without
having to rebuild portage and all its dependencies everytime I want to
switch and test ...

I have a some systems with common hardware where I can use a buildhost
and the moosefs share is an easy way to access the built packages across
the network

Bill K.


On 16/5/20 9:55 am, Victor Ivanov wrote:
> Why do you think emerge might be the issue? It's quite rare for portage
> itself to be causing problems with packages.
>
> That said, if you have good reason to believe so you can adjust the
> PYTHON_TARGETS for sys-apps/portage in /etc/portage/package.use like so:
>
>     sys-apps/portage PYTHON_TARGETS: +python3_6 -python3_7
>
> Or you can keep both. You will of course need to rebuild portage
> following this change.
>
> Likewise, you use the syntax of the above entry to adjust the python
> targets for any package.
>
> Your default interpreter choice (as reported by eselect) is likely not
> respected by portage because the current profile defaults only build
> portage against python 3.7.
>
> - Victor
>
> On 16/05/2020 02:32, William Kenworthy wrote:
>> How can I force emerge to use python 3.6 when 3.7 is installed? -
>> eselect list shows 3.6 is #1 and 3.7 as fallback so that doesn't work.
>>
>> I am trying to narrow down a failure which appears to be a combination
>> of building packages that are stored on a moosefs network share and
>> python 3.7
>>
>> BillK
>>
>>

[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 2225 bytes --]

Re: [gentoo-user] How can I force emerge to use python 3.6?

[Mike Gilbert]

On Fri, May 15, 2020 at 10:17 PM William Kenworthy <billk@iinet.net.au> wrote:
>
> Hi Victor,
>
>     emerge crashes when it tries to add metadata during the merge stage
> in an emerge installed python module using 3.7 when the PKGDIR is on a
> moosefs share.  When PKGDIR is local its fine.
>
> I am rebuilding some systems now with 3.6 as the PYTHON_SINGLE_TARGET
> but I was hoping for some way to specify emerge use 3.7 or 3.6 without
> having to rebuild portage and all its dependencies everytime I want to
> switch and test ...

Set PYTHON_TARGETS=pytthon3_6. This will ensure portage and its
dependencies are built for python3.6.

You can then set python3.6 as the default interpreter globally by
putting it first in /etc/python-exec/python-exec.conf. There's a
comment with instructions at the top of that file.

If you only want emerge to use python3.6, put it in
/etc/python-exec/emerge.conf instead.

Re: [gentoo-user] How can I force emerge to use python 3.6?

[Mike Gilbert]

On Fri, May 15, 2020 at 10:17 PM William Kenworthy <billk@iinet.net.au> wrote:
>
> Hi Victor,
>
>     emerge crashes when it tries to add metadata during the merge stage
> in an emerge installed python module using 3.7 when the PKGDIR is on a
> moosefs share.  When PKGDIR is local its fine.

I have never heard of moosefs. It probably returns an error when
portage tries to use some of the more advanced file syscalls. Please
file a bug report.

Re: [gentoo-user] How can I force emerge to use python 3.6?

[William Kenworthy]

[-- Attachment #1: Type: text/plain, Size: 916 bytes --]


On 16/5/20 11:34 am, Mike Gilbert wrote:
> On Fri, May 15, 2020 at 10:17 PM William Kenworthy <billk@iinet.net.au> wrote:
>> Hi Victor,
>>
>>     emerge crashes when it tries to add metadata during the merge stage
>> in an emerge installed python module using 3.7 when the PKGDIR is on a
>> moosefs share.  When PKGDIR is local its fine.
> I have never heard of moosefs. It probably returns an error when
> portage tries to use some of the more advanced file syscalls. Please
> file a bug report.
>
I will file a bug - just trying to make sure its a real bug and not just
me :)

moosefs has been great so far, but its posix support may be incomplete
for some corner cases - its strength is large scale redundant storage
and not substituting for local storage but its been doing ok for some
months now up until the near apocalyptic mess that the python upgrade
has become for me ...

BillK



[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 2225 bytes --]