Upgrading to current (2.0.3) from 1.9 fails to upgrade the first time

[keybounce]

I just upgraded from the olderr 1.9 branch (1.9.3, I think) to the current (2.0.3) branch, with "sudo port selfupdate".

The output seemed good, but "sudo port upgrade outdated" then failed:

sudo bash
Password:
bash-3.2# port upgrade outdated
--->  Computing dependencies for libiconv
--->  Building libiconv
...
--->  Activating libogg @1.3.0_0+universal
--->  Cleaning libogg
--->  p5-locale-gettext is replaced by p5.12-locale-gettext
Error: No port p5.12-locale-gettext found.
To report a bug, see <http://guide.macports.org/#project.tickets>
bash-3.2# sudo port selfupdate
--->  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
bash-3.2# port outdated
The following installed ports are outdated:
p5-locale-gettext              1.05_5 < 1.50.0_6         
python27                       2.7.2_0 < 2.7.2_1         
rsync                          3.0.7_1 < 3.0.8_0         
sqlite3                        3.7.6_0 < 3.7.7.1_0       
XviD                           1.3.2_0 < 1.3.2_1         
bash-3.2# port upgrade outdated
--->  p5-locale-gettext is replaced by p5.12-locale-gettext
--->  Computing dependencies for p5.12-locale-gettext
--->  Fetching archive for p5.12-locale-gettext

Note the following: p5-local-gettext was replaced. The first time, the upgrade stopped at this point. After a second self update, the upgrade completed.

[ryandesign (Ryan Carsten Schmidt)]

When upgrading to a new version of MacPorts, you must run "sudo port selfupdate" a second time. MacPorts 2.0.3 now prints a message telling you this; MacPorts 1.9 did not so you might not have known this. See #30739.