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