Upgraded (partially?) to v2.0.3, now port updates fail, OSX 10.6.8

[Fielding, Eric J (3242)]

On 10/6/11 7:17 AM, "Jeremy Lavergne" <jeremy at lavergne.gotdns.org> wrote:

>> Thanks for your reply and explanation. It might be a good idea to add a
>> warning when the conversion starts that it could take a very long time
>>so
>> others don't make my mistake.
>>
>> I should probably just start over from scratch, to avoid future problems
>> with a partial conversion. I see the uninstall directions at
>> http://guide.macports.org/chunked/installing.macports.uninstalling.html
>>so
>> I will use those.
>
>You might try running selfupdate again (with -d so you can watch what's
>going on). It might find that there are packages remaining to be converted
>and pick up where it left off.
>
>Might.

Thanks for the suggestion, but unfortunately, that does not work. The
"selfupdate" seems to think the conversion is complete so it doesn't
convert the parts that are missing.
======
 port selfupdate -d
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.0.3 installed,
MacPorts base version 2.0.3 downloaded.
--->  Updating the ports tree
--->  MacPorts base is already the latest version

The ports tree has been updated. To upgrade your installed ports, you
should run
  port upgrade outdated
=====
The "port upgrade" command still fails in the same way.


I also tried running the gentle "sudo port -fp uninstall
--follow-dependents installed" command but that fails with the same
problems that the directories are not empty, so I think my only option now
is to nuke the whole directory tree.

++Eric