On 16/5/20 11:34 am, Mike Gilbert wrote:
> On Fri, May 15, 2020 at 10:17 PM William Kenworthy 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
On Fri, May 15, 2020 at 10:17 PM William Kenworthy 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
On Fri, May 15, 2020 at 10:17 PM William Kenworthy 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
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
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:
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
6 matches
Mail list logo
