Michael wrote: > Just as I was celebrating the last python upgrade has been a breeze, a disk > failed on one PC in the most inopportune moment. The / directory was on the > SSD disk which failed. The /var/db, /var/cache and /var/log are on a > different (spinning) disk. > > I restored / from a backup which was 5 weeks old, excluding /var/db, /var/ > cache and /var/log - I didn't have a backup of these. Consequently, there's > an incongruity in what portage thinks is installed - a day old update status > - > and what is actually installed - 5 weeks old packages. > > I tried to run an update @world, but it failed as some package versions were > missing/incompatible. I tried to force python3_13 following the python > upgrade guide, but may have ended up making things worse. What is the best > way to bring this system up to date?
Do you have buildpkg set in make.conf? If you do, can you try a emerge -ek world? That should reinstall to the version you have saved from all the binaries you have. You may want to try -K as well. It tells it to use binaries only. If you don't have buildpkg set, I'm not sure how to fix that. Basically, portage stores data on what is installed in /var but the packages are in /, mostly /(s)bin and /usr. Basically, portage thinks one thing but the truth is something else. I suspect emerge isn't happy since it is so confused. I hate when a drive goes bad. :-( Dale :-) :-) P. S. I hope you have a backup of /etc and your world file, just in case you have to start over.
