Duncan <[email protected]> posted [email protected],
excerpted below, on Thu, 22 Jan 2009 20:21:28 +0000:
> The problem was that I ended up with a mix of some "current" partitions
> and some backup partitions and a package database that wasn't at all in
> sync with what was actually on disk.
More to the point, I did have binpkgs and could thus reinstall current
and get what was running and what portage thought was installed back in
sync, but it left behind a bunch of stale old library files and etc, that
weren't removed, because portage thought the new version (with a
different filename) was already installed, and thus didn't do the cleanup
of the old installed version it would have normally done when upgrading.
I had to do a lot of manual stuff like
for candidatefile in /usr/lib64; do;
equery b $candidatefile
done
Then I'd scan the output and for every file that didn't have an owner,
I'd have to decide whether it was a legitimate file, config or other file
not actually tracked by portage, or whether it was an old stale left-
over. If it was the latter, I'd delete it.
I realized that had everything been in sync, if portage had actually
known what was installed, I'd have been able to upgrade and it would have
automatically handled the cleanup as it normally does. As I said, I
learned my lesson, and won't be making /that/ mistake again!
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
