#59228 closed defect (duplicate)

base upgrade fails if Xcode license not accepted

Reported by: EJFielding (Eric Fielding) Owned by:
Priority: Normal Milestone:
Component: base Version: 2.6.1
Keywords: Cc:
Port:

Description

I ran a port selfupate for the first time in a while, and it tried unsuccessfully to install the base upgrade to version 2.6.1. It turned out that MacOS had also updated the Xcode to v11.1 on this Mojave machine, and I had not accepted the license again, so the base version upgrade failed silently. Then it gave me an error message when I tried to do the port upgrade outdated.

fielding% sudo port selfupdate:
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.5.4 installed,
MacPorts base version 2.6.1 downloaded.
--->  Updating the ports tree
--->  MacPorts base is outdated, installing new version 2.6.1
Installing new MacPorts release in /opt/local as root:wheel; permissions 0755

fielding% sudo port selfupdate
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.5.4 installed,
MacPorts base version 2.6.1 downloaded.
--->  Updating the ports tree
--->  MacPorts base is outdated, installing new version 2.6.1
Installing new MacPorts release in /opt/local as root:wheel; permissions 0755

fielding% sudo port upgrade outdated
Error: Unable to open port: can't set "compiler.blacklist": invalid command name "compiler.command_line_tools_version"
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

I was able to solve this by accepting the Xcode license and re-running the port selfupdate again, and then port upgrade outdated.

I think it is a bug that the port selfupdate did not report that it was unable to run Xcode and upgrade the base version.

Change History (1)

comment:1 Changed 14 months ago by jmroot (Joshua Root)

Component: portsbase
Resolution: duplicate
Status: newclosed

We can't do anything about not being able to build without accepting the license, but the failure to report the selfupdate failure without -v or -d is #56549.

Note: See TracTickets for help on using tickets.