Help With Nasty Slackpkg/Slackpkg+ SNAFU
by enorbet from LinuxQuestions.org on (#5FR17)
Greetz and thank all for any insights On my Main boxen I have 4 installs of Current at various levels of updates and development. My Main, I backup weekly so there's that but I did a lot of development this past week so I don't prefer to revert if avoidable. I have complained quite a bit about the annoyance of so many unnecessary .new files, unnecessary because there is no substantive changes other than making me rewrite them yet again when my preferences are highly unlikely to change. If my preference does change then editing is warranted, but in this case a .new file that came with an upgrade recommendation actually contained a fairly serious error. A previous upgrade noted that we should switch to using "Slackware -15" for proper mirrors for we who have done near daily upgrades or just a recent one. I've been using the "us.kernel.org mirror" for some weeks now so I located it in the "Slackware-15" section and it error-ed out - essentially a 404. So I checked in a browser on another machine and discovered there is no "15" on "kernel.org.
I made matters worse when I vim'd slackpkg.conf and re-commented "kernel.org" under "15" and made the mistake of forgetting the default is 14.2. Needless to say an avalanche of errors ensued and that system is down in kernel panic land. I did manage to get back to runlevel 3 login but could do nothing to fix things because of glibc errors that made several operations like grep, sed, pkgtool, and even bash crippled. Now I have new directories labelled "/installpackage-foo" and files labelled "upgrading" and "pending" etc.
Enough of my shameful mistakes, what I'd like to do is just wipe out that failed upgrade by copying over such directories as /lib, /lib64, /usr/lib, usr/lib64, /libexec? and any others some kind and informed soul might recommend from a working and updated separate install.
Is this even remotely workable? FWIW I intend to try before I resort to backup but some advice might reduce the sting of "airing my dirty laundry".
Thanks in advance.
I made matters worse when I vim'd slackpkg.conf and re-commented "kernel.org" under "15" and made the mistake of forgetting the default is 14.2. Needless to say an avalanche of errors ensued and that system is down in kernel panic land. I did manage to get back to runlevel 3 login but could do nothing to fix things because of glibc errors that made several operations like grep, sed, pkgtool, and even bash crippled. Now I have new directories labelled "/installpackage-foo" and files labelled "upgrading" and "pending" etc.
Enough of my shameful mistakes, what I'd like to do is just wipe out that failed upgrade by copying over such directories as /lib, /lib64, /usr/lib, usr/lib64, /libexec? and any others some kind and informed soul might recommend from a working and updated separate install.
Is this even remotely workable? FWIW I intend to try before I resort to backup but some advice might reduce the sting of "airing my dirty laundry".
Thanks in advance.