| 1 |
On Sun, 1 Aug 2021 at 18:51, n952162 <n952162@×××.de> wrote: |
| 2 |
> |
| 3 |
> On 8/1/21 6:19 PM, Arve Barsnes wrote: |
| 4 |
> > Many of the conflicts seem related to an old version of |
| 5 |
> > dev-python/requests. Could newer versions be masked, or could there be |
| 6 |
> > older python targets set for it in /etc/portage/package.use/ ? |
| 7 |
> > |
| 8 |
> > Regards, |
| 9 |
> > Arve |
| 10 |
> |
| 11 |
> |
| 12 |
> I have this: |
| 13 |
> |
| 14 |
> 02/etc/portage/package.use>grep -i request * |
| 15 |
> ... |
| 16 |
> 201213:>=dev-python/requests-2.24.0-r1 python_targets_python3_7 |
| 17 |
> ... |
| 18 |
> use-flags-201110:>=dev-python/requests-2.23.0 python_targets_python3_6 |
| 19 |
> |
| 20 |
> Is it not the case that those just insist on a newer version? |
| 21 |
|
| 22 |
That sets both for all versions newer than 2.24.0-r1, but the oldest |
| 23 |
version available does not support 3.6. |
| 24 |
|
| 25 |
> Or, is the problem python_targets+python3_6. I've got a lot of those. |
| 26 |
> Do they all force that version and need to come out? To be replaced |
| 27 |
> with something else? |
| 28 |
|
| 29 |
Unless you have a special reason for them, I would try to remove them |
| 30 |
all, and let portage take care of pulling in the right versions. At |
| 31 |
least remove any 3.6 lines. |
| 32 |
|
| 33 |
Regards, |
| 34 |
Arve |
Archives