Rich Freeman wrote: > On Wed, May 6, 2020 at 10:14 PM Caveman Al Toraboran > <toraboracave...@protonmail.com> wrote: >> are you referring to python's dependence on expat >> and glibc? >> > More like bash's dependence. Well, and in the case of glibc just > about everything. When those break you're basically stuck recovering > from a rescue disk. > > Fortunately we haven't had glibc/gcc break ABI in quite a while, and > preserved-rebuild covers a lot of the other issues. > > In any case, if you have a solution other than statically building > half the system I'm sure patches will be welcome. FWIW Gentoo is > about as hassle-free to use as it has ever been. It isn't debian > stable, and it is unlikely to ever be that way... >
I agree that the Gentoo update process is a LOT better than it used to be. Even I run into fewer problems and that's saying something. lol There used to be a package that caused some serious problems with upgrades. It was really tricky but I can't recall the name of it since it was ages ago. It was back around the old hal days or so. I don't know if it is even used anymore. Either the update process has improved or it isn't used anymore. I just recall it was a critical package, sort of like gcc or glibc but it was some other package. OP, odds are the emerge failure is what triggered the problem. If it had completed without failure, it would likely have been a clean update. This is why I set up a chroot and do my updates there and use the -k option to install on my actual system. It takes very little time and so far, no breakages on my real system. If any thing fails, it's more likely to be in the chroot which won't hurt anything. If you able, may be a option worth thinking about for yourself as well. Dale :-) :-)
