Description of Problem:
'up2date -p' doesn't traverse the code for version migration and it
probably should, as after people perform a manual upgrade, they are
probably going to run 'up2date -p' to sync up their database with the site.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
should be fixed in cvs code now.