On Sat, 13 Feb 2021 20:59:08 -0800
cal <[email protected]> wrote:
> Did you run emerge --sync before emerge -1vUD @world?
A cron job here runs "emerge --sync && emerge --update --fetchonly"
every day at 0300.
> The Python 3.7 change is old news -- by now it's already migrated to
> 3.8 on my system.
This system has been fried ever since
2020-04-22-python3-7
Title Python 3.7 to become the default target
Author Michał Górny <[email protected]>
Posted 2020-04-22
Revision 1
On 2020-05-06 (or later), Python 3.7 will replace Python 3.6 as one
of the default Python targets for Gentoo systems. The new default
values will be:
Followed those instructions -- don't use python for anything here
and the local copies of what I actually use are in /opt/perl,
/opt/postgresql, etc, built from git checkouts.
At this point I've added and removed python single and multiple
target entries from make.conf & package.use/local, with various
sets of values and exclusions.
A bare sync tells me there is a new version of portage available,
installing it fails, however with:
# emerge --sync;
<snip>
Action: sync for repo: gentoo, returned code = 0
* An update to portage is available. It is _highly_ recommended
* that you update portage now, before any other packages are updated.
* To update portage, run 'emerge --oneshot sys-apps/portage' now.
# emerge --oneshot sys-apps/portage 2>&1 | tee a;
Calculating dependencies ....... done!
[ebuild N ] dev-lang/python-exec-conf-2.4.6 PYTHON_TARGETS="python3_8
-pypy3 -python3_7 -python3_9"
[ebuild N ] acct-group/portage-0
[ebuild U ] dev-lang/python-exec-2.4.6-r4 [2.4.6-r1]
USE="native-symlinks%*" PYTHON_TARGETS="(python3_8%*) (python3_9%*)"
[ebuild N ] acct-user/portage-0
[ebuild U ] dev-python/certifi-10001-r1 [10001]
PYTHON_TARGETS="python3_8*"
[ebuild U ~] dev-python/setuptools-53.0.0 [44.0.0]
PYTHON_TARGETS="python3_8* -python3_9%"
[ebuild U ~] dev-python/setuptools_scm-5.0.1 [4.1.2]
PYTHON_TARGETS="python3_8*"
[ebuild U ] dev-python/chardet-4.0.0 [3.0.4]
PYTHON_TARGETS="python3_8* -python3_9%"
[ebuild U ] dev-python/idna-2.10-r1 [2.8] PYTHON_TARGETS="python3_8*
-python3_9%"
[ebuild U ] dev-python/PySocks-1.7.1-r1 [1.6.8]
PYTHON_TARGETS="python3_8* -python3_9%"
[ebuild U ~] dev-python/urllib3-1.26.3-r1 [1.24.2] USE="-brotli%"
PYTHON_TARGETS="python3_8%* -python3_9%"
[ebuild U ] dev-python/requests-2.25.1-r1 [2.21.0-r1] USE="-test%"
PYTHON_TARGETS="python3_8%* -python3_9%"
[ebuild U ~] app-crypt/gnupg-2.2.27 [2.2.20] USE="-scd-shared-access%"
[ebuild U ] app-portage/gemato-16.2 [14.3] PYTHON_TARGETS="python3_8*
-python3_7* -python3_9%"
[ebuild U ~] sys-apps/portage-3.0.14 [3.0.1] USE="-test%"
PYTHON_TARGETS="python3_8* -python3_7*"
[blocks B ] <=dev-lang/python-2.7.18-r3:2.7
("<=dev-lang/python-2.7.18-r3:2.7" is blocking dev-lang/python-exec-2.4.6-r4)
[blocks B ] <dev-lang/python-exec-2.4.6-r4
("<dev-lang/python-exec-2.4.6-r4" is blocking dev-lang/python-exec-conf-2.4.6)
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
dev-lang/python-exec:2
(dev-lang/python-exec-2.4.6-r4:2/2::gentoo, ebuild scheduled for merge)
USE="native-symlinks" ABI_X86="(64)" PYTHON_TARGETS="(pypy3) (python3_7)
(python3_8) (python3_9)" pulled in by
>=dev-lang/python-exec-2:=[python_targets_pypy3(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
required by (dev-python/chardet-4.0.0:0/0::gentoo, ebuild scheduled for merge)
USE="-test" ABI_X86="(64)" PYTHON_TARGETS="python3_8 -pypy3 -python3_7
-python3_9"
>=dev-lang/python-exec-2:=[python_targets_pypy3(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
required by (dev-python/setuptools-53.0.0:0/0::gentoo, ebuild scheduled for
merge) USE="-test" ABI_X86="(64)" PYTHON_TARGETS="python3_7 python3_8 -pypy3
-python3_9"
Full output at:
<https://pastebin.com/mEJg3N7N>
Q: Is there any way to clean up python at this point without
a full re-install?
thanks
--
Steven Lembark
Workhorse Computing
[email protected]
+1 888 359 3508
