On Thursday, May 7, 2020 5:43 AM, Rich Freeman <ri...@gentoo.org> wrote:
> Are you overriding something, or were you running this right in the > middle of an update? emerge was updating, then some ebuild failed and i didn't have --keep-going. then next time i tried to sync layman it failed. i'm now re-running emerge and it seems to work normally. > > 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. i have layman-2.4.3, emerged with python3_6, and is now about to be moved to python3_7. no biggie. i can fix it. but, my point is, this hassle is needless and keeps coming. > 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). true, but needless hassle imo. > Really though this is pretty tame. There have been some updates to > expat and especially glibc in the past that were pretty hairy. are you referring to python's dependence on expat and glibc? yeah, so many layers of mistakes get born when one relies on python as a dependency for a system app that manages other apps (including itself).
