Update /etc/make.profile and Lose Package DB?

[rabbit]

We've had an older sparc64 system running our file mirror for awhile, and we've been keeping it up with all the GLSAs. Recently after a sync, I went to emerge a package when I was told that I needed to update the system's profile to the latest default-sparc64-2004.0, which I did.

Now when trying to emerge anything, it wants to start from scratch -- i.e. if I want to emerge the new portage, there are 20-some packages until I get there. All these depdencies are marked as new even when trying to emerge packages already listed in the world file (i.e. apache, proftpd, etc).

Any ideas on how I can either rebuild my package database or something so at least I don't have to rebuild the machine from scratch?