OK, you're not likely to run into this problem.
However, if you do things the Agaric way, and point a domain at a server, and Apache sends it to a valid Drupal installation with a custom installation profile option, and you select that installation profile, and then realize you really want Apache pointing your domain to a different, 5.2 installation.
You may get an error about the user being rejected for the database table. And you can keep trying this page with reset passwords and anything and keep getting the same error. It's weird, but that's what happened to us.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution 3.0 Unported License.