On Nov 15, 2014, at 2:00 PM, René J.V. Bertin wrote: > On Saturday November 15 2014 19:48:20 Clemens Lang wrote: > >> of interest here. The key is `portfiles_update_needed` being present and set >> to one, which means the conversion didn't run or successfully finish on your > > Yes, that's what I figured too... > >> system. You will have to run it again, e.g. by running >> sudo port -df selfupdate. >> If it fails again, you should at least see some error output. > > Well, it didn't fail, and now the update_needed flag is gone. > > I did have the présence d'esprit to re-run port selfupdate after the initial > failure, and it finished correctly. How come it didn't do the db update too?
If "sudo port selfupdate" updates the MacPorts version, then you must run "sudo port selfupdate" a second time to index the ports with that new version; MacPorts prints a message telling you to do this. Is that perhaps related in this case? Do you always run selfupdate a second time when prompted to do so? Does the conversion perhaps happen after the second selfupdate? _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
