[MacPorts] #49169: port selfupdate breaks when going from 2.3.3 to 2.3.4

[MacPorts]

#49169: port selfupdate breaks when going from 2.3.3 to 2.3.4
---------------------------+--------------------------------
  Reporter:  FoolishEwe@…  |      Owner:  macports-tickets@…
      Type:  defect        |     Status:  reopened
  Priority:  Normal        |  Milestone:
 Component:  base          |    Version:  2.3.4
Resolution:                |   Keywords:
      Port:                |
---------------------------+--------------------------------
Changes (by fhgwright):

 * status:  closed => reopened
 * resolution:  invalid =>


Comment:

 I just ran across this on the 2.3.4 to 2.3.5 selfupdate.  I believe it was
 triggered by having updated Xcode, with Apple's deciding that I needed to
 agree to the Xcode license *again* (sigh, must be the iTunes compatibilty
 feature).

 The issue with MacPorts is just that it doesn't provide a very informative
 error message.  Running "upgrade outdated" in this state says:

 {{{
 Error: It seems you have not accepted the Xcode license; most ports will
 fail to build.
 Error: Agree to the license by opening Xcode or running `sudo xcodebuild
 -license'.
 Error: Unable to upgrade port: 1
 }}}

 But selfupdate only says:

 {{{
 Error: Error installing new MacPorts base: command execution failed
 Please run `port -v selfupdate' for details.
 Error: /opt/local/bin/port: port selfupdate failed: Error installing new
 MacPorts base: command execution failed
 }}}

 It seems to me that selfupdate could be smart enough to provide the same
 error message that "upgrade outdated" does, rather than requiring the user
 to dig into it.

--
Ticket URL: <https://trac.macports.org/ticket/49169#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS