-   Slackware (
-   -   HOWTO: Recover from botched upgrade (

rworkman 04-05-2007 05:00 PM

HOWTO: Recover from botched upgrade
DISCLAIMER: This is not intended to be a *complete* guide to cover all possible ways that one can botch an upgrade - rather, it is intended to cover one of the most frequent problems that people encounter when upgrading from one release of Slackware to another (or more recently, from the latest stable release to -current).

If you've failed to read UPGRADE.TXT / CHANGES_AND_HINTS.TXT before attempting an upgrade to Slackware -current, you possibly/probably wound up with errors about GLIBC stuff not found or "kernel too old" and such. This document should help you (mostly) return your system to its previous state so you can start over and do the upgrade correctly.

Enough chatter - here's the link:

vtel57 04-06-2007 04:15 PM

This saved my arse today. A friend from another forum alerted me to it. I had swaret set to "current" by accident. After recovering with this method, I edited my swaret.conf to 11.0 instead of current, and updated/upgraded from that point. All's well now. This fix in the link above does work!

All times are GMT -5. The time now is 11:27 AM.