Rich Freeman wrote: > On Tue, Jun 18, 2019 at 11:51 AM Alan Mackenzie <[email protected]> wrote: >> At this stage, /lib32 should be a symlink. I think that step 12 means >> just the symlink should be removed, NOT all the stuff inside what it >> points to. >> >> So I think what you should do is: >> >> $ rm /lib32 >> >> , but definitely NOT a recursive rm on that symlink. > This is the correct answer. Large scale breakage should not be an > issue if you've followed the other instructions. It is possible that > something minor might break, but this is all 32-bit stuff. I ran > revdep-rebuild immediately after removing the symlink and it found > nothing wrong, but this is probably a step you can do to be > extra-sure. >
That's what I did as well and I got this: root@fireball / # revdep-rebuild -i * This is the new python coded version * Please report any bugs found using it. * The original revdep-rebuild script is installed as revdep-rebuild.sh * Please file bugs at: https://bugs.gentoo.org/ * Collecting system binaries and libraries * Checking dynamic linking consistency Your system is consistent root@fireball / # So, I guess I'm done with the switch but I'm going to do that emerge -K world just to be sure. It may be a while before I get around to rebooting but I'd like to be sure I can when I get around to it. ;-) We are supposed to have some storms in the next few days. I've already had a few blinks on the lights here. Thank goodness for the UPS. Thanks to all. Dale :-) :-)
