Messed up update. How to avoid next time?
by montagdude from LinuxQuestions.org on (#5DKFW)
Hey everyone,
Last night I attempted to update my Slackware64-current installation. It had been about a week or two since I last updated, so that included the mass rebuild as well as the new glibc and slackpkg. After starting the update, since slackpkg was updated, it kicked out early and made me start again. Then havoc ensued. Every package that it tried to upgrade produced an error saying that it was not installed properly, and that the old one may need to be reinstalled to keep the system functioning properly. Of course, at this point I didn't have the old packages. Attempting a reboot resulted in a bunch of errors about the needed glibc version not being available. I attempted to chroot from recovery media and reinstall but encountered the same error. In the end, I just used Alien Bob's mirror-slackware-current script and reinstalled.
My theory about what happened is that since slackpkg kicked out early, it must have installed the new glibc but left a bunch of other things linking to the old one and therefore broken. If that is correct, then I think first upgrading slackpkg only before proceeding with the upgrade-all should avoid problems in the future. Does this sound correct? I need to update my wife's computer too, and I don't want this to happen again. I didn't see any special instructions in the ChangeLog for handling the mass upgrade.
Last night I attempted to update my Slackware64-current installation. It had been about a week or two since I last updated, so that included the mass rebuild as well as the new glibc and slackpkg. After starting the update, since slackpkg was updated, it kicked out early and made me start again. Then havoc ensued. Every package that it tried to upgrade produced an error saying that it was not installed properly, and that the old one may need to be reinstalled to keep the system functioning properly. Of course, at this point I didn't have the old packages. Attempting a reboot resulted in a bunch of errors about the needed glibc version not being available. I attempted to chroot from recovery media and reinstall but encountered the same error. In the end, I just used Alien Bob's mirror-slackware-current script and reinstalled.
My theory about what happened is that since slackpkg kicked out early, it must have installed the new glibc but left a bunch of other things linking to the old one and therefore broken. If that is correct, then I think first upgrading slackpkg only before proceeding with the upgrade-all should avoid problems in the future. Does this sound correct? I need to update my wife's computer too, and I don't want this to happen again. I didn't see any special instructions in the ChangeLog for handling the mass upgrade.