On Wed, May 6, 2020 at 9:13 PM Caveman Al Toraboran <toraboracave...@protonmail.com> wrote: > > just to say that some portagy thing (layman) can't > work now as emerge was rebuilding packages to > remove python3_6): > > running "layman -S"... > Traceback (most recent call last): > File "/usr/lib/python-exec/python3.6/layman", line 36, in <module> > from layman.cli import Main > File "/usr/lib64/python3.6/site-packages/layman/cli.py", line 29, in > <module> > from layman.api import LaymanAPI > File "/usr/lib64/python3.6/site-packages/layman/api.py", line 25, in > <module> > from layman.remotedb import RemoteDB > File "/usr/lib64/python3.6/site-packages/layman/remotedb.py", line 46, > in <module> > from sslfetch.connections import Connector > ModuleNotFoundError: No module named 'sslfetch' > > obviously solvable easily in this case, but imo > needless drama keeps coming every now and then. >
Are you overriding something, or were you running this right in the middle of an update? layman-2.4.2 strictly requires python 3.6 and the system wouldn't let you remove that version of python unless you forced it to. The newer version of layman is compatible with the newer versions of python, but of course needs to be rebuilt for it. If you read the news on the update you'd see this. If you just do a regular emerge -uD @world then while it was in the middle of updating some things would break. There are instructions in the news for how to do a more seamless upgrade by enabling both the older and newer versions of python in parallel, in which case there won't be any point where things break. That does require rebuilding everything twice (not necessarily at the same time). Really though this is pretty tame. There have been some updates to expat and especially glibc in the past that were pretty hairy. -- Rich
