[MacPorts] #44091: In port interactive mode, pseudo-portnames corrupted after selfupdate

[MacPorts]

#44091: In port interactive mode, pseudo-portnames corrupted after selfupdate
------------------------+------------------------------------------------
  Reporter:  pjkim00@…  |      Owner:  macports-tickets@…
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  base       |    Version:  2.3.0
Resolution:             |   Keywords:  corrupt pseudo-portname selfupdate
      Port:             |
------------------------+------------------------------------------------

Comment (by pjkim00@…):

 I usually run individual port commands from the bash shell but sometimes
 my sudo times out so I wondered whether starting 'sudo port' once followed
 by calling everything else in interactive mode would save having to type
 my password.

 I just tried again and noted one thing. If selfupdate actually finds an
 outdated port, 'outdated' correctly contains the outdated ports. If
 however I upgrade those ports and selfupdate again, then 'outdated' now
 contains the entire port list of 19K items.

 I just found another method way to reproduce the same issue. In
 interactive mode, 'list outdated' returns nothing. But after the command
 'outdated', 'list outdated' now returns the full list. Here is what I
 mean:

 [~]$ port[[BR]]

 MacPorts 2.3.0[[BR]]
 Entering interactive mode... ("help" for help, "quit" to quit)[[BR]]
 [Users/pjkim] > list outdated[[BR]]
 [Users/pjkim] > outdated[[BR]]
 No installed ports are outdated.[[BR]]
 [Users/pjkim] > list outdated[[BR]]
 AppHack                        @1.1            aqua/AppHack[[BR]]
 AppKiDo                        @0.997          aqua/AppKiDo[[BR]]
 ..... lots more lines[[BR]]

 Not a big deal because I will just stop using interactive mode and the
 problem/bug is absent when called non-interactively. My only concern is
 that this was an unexpected behavior that was possibly a real problem.
 After reading the FAQ you linked, I see that this is somewhat expected
 behavior, although the example above still puzzles me as it appears
 inconsistent/erratic.

-- 
Ticket URL: <https://trac.macports.org/ticket/44091#comment:2>
MacPorts <http://www.macports.org/>
Ports system for OS X