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

[William Kenworthy]

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
>>
>>