curent: upgrade failed after glibc-solibs, so nothing will run
I was uploading to the present batch of current updates.
Slackpkg upgraded and said to run it again. Updated, did upgrade-all. All the packages were "already in cache - not downloading". glibc-solibs upgraded, seemingly successfully. Then every package gave an error from md5sum, that there was no such file or directory, immediately after saying its in the cache. Now, of course, everything segfaults when I try to run it. How od I solve this? |
Last update of glibc-solibs was in February
did you upgrade just recently from 14.1 ? |
Quote:
|
I have chrooted into the hard drive from a usb boot stick, and enjoyed getting that connected to the internet, and am trying to proceed from there by running the upgrade again.
Edit: No, didn't work. boot image was, for some reason, using 100% of my cpu, and decided halfway through the update that it needed slacpkg update-gpg to be run, and when I tried running that it decided awk doesn't work. |
i just finished upgrading my wife's desktop from Slackware 14.1 to Slackware Current and all is fine here
|
Quote:
|
What I would do:
|
Quote:
Mount your harddrive's filesystem somewhere (/mnt is a good choice but anything is fine), mount the DVD so you have access to all the packages, and then run "ROOT=/mnt upgradepkg --reinstall --install-new" for all packages in at least the "A", "AP", "D" and "L". That should fix the basic programs on your harddisk. After that you can chroot into the harddrive installation and using "slackpkg install-new ; slackpkg upgrade-all ; slackpkg clean-system" you can fix the rest of your installation. Be sure to use the correct architecture for the DVD (32bit 0r 64bit)! DVD's for Slackware-current (re-created everytime there's an update to -current) are here: http://bear.alienbase.nl/mirrors/sla...4-current-iso/ (64bit) http://bear.alienbase.nl/mirrors/sla...e-current-iso/ (32bit). |
Quote:
the obvious change was google-chrome -> chromium but since only the icon changed, i doubt she will complaint about that back to topic, i'm pretty sure the OP had a broken package during upgrade process, thus leaving the machine into that state. |
According to the article "System Upgrade using SlackPkg"
slackwareuptodate Code:
|
All times are GMT -5. The time now is 09:30 AM. |