1 |
On Tue, Dec 08, 2020 at 10:38:43AM +0100, Arve Barsnes wrote |
2 |
> On Tue, 8 Dec 2020 at 10:07, Walter Dnes <waltdnes@××××××××.org> wrote: |
3 |
> > I just did an "emerge --sync", and was told to update portage. But it |
4 |
> > seems that portage 3.0.8 built with python 3.7 is blocking portage 3.0.9 |
5 |
> > with python 3.8. I obviously can't remove portage to fix the block <G>. |
6 |
> > Note "grep -i python /etc/portage/make.conf" shows no output at all. In |
7 |
> > package.use, PYTHON_TARGETS: and PYTHON_SINGLE_TARGET: are commented out. |
8 |
> |
9 |
> It's a dependency problem that I find that it is not worth to |
10 |
> untangle. I had the exact same problem yesterday on a different |
11 |
> machine. |
12 |
> |
13 |
> My advice: skip this and go straight to world update. portage will |
14 |
> most likely figure out the tangle for you, and update itself during |
15 |
> the world update. |
16 |
|
17 |
Thank you. That fixed the problem. After updating world portage-3.0.9 |
18 |
is now installed, built against PYTHON_TARGETS="python3_8" |
19 |
|
20 |
-- |
21 |
Walter Dnes <waltdnes@××××××××.org> |
22 |
I don't run "desktop environments"; I run useful applications |