port upgrade outdated from 2.0.2 to 2.0.3 messed up user database

[Ryan Schmidt]

While I don't think this has anything to do with this thread...


On Oct 10, 2011, at 19:15, Jeremy Lavergne wrote:

> Have we completely dropped the ball on informing users to run selfupdate twice?

When you selfupdate *from* MacPorts 2.0.2 or later you'll be told to run selfupdate a second time. MacPorts 2.0.1 and earlier didn't know to tell you to do that so you just have to know.


> I feel that, if that's the case, we should start ensuring that selfupdate can run itself twice (looks a file to signal "do selfupdate").

That would be a possible enhancement, but of course, it won't help anybody upgrading *from* any existing version of MacPorts. It'll only help us in the future.