Opened 7 years ago
Closed 4 years ago
#55653 closed defect (worksforme)
"sudo port upgrade outdated" fails
Reported by: | jhi | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 2.4.2 |
Keywords: | Cc: | ||
Port: |
Description
$ sudo port upgrade outdated Error: Follow https://guide.macports.org/#project.tickets to report a bug. $
And ... that's it.
According to "selfupdate" I'm not completely broken.
$ sudo port selfupdate Password: ---> Updating MacPorts base sources using rsync MacPorts base version 2.4.2 installed, MacPorts base version 2.4.2 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
OS:
$ sw_vers ProductName: Mac OS X ProductVersion: 10.13.2 BuildVersion: 17C88
Change History (4)
comment:1 Changed 7 years ago by mf2k (Frank Schima)
Component: | ports → base |
---|
comment:2 Changed 7 years ago by mf2k (Frank Schima)
Version: | → 2.4.2 |
---|
comment:3 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
comment:4 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Closing due to lack of response. Hopefully we fixed the circular dependency somewhere along the way. If not, please reopen the ticket and provide the output I requested above. Enabling debug output (sudo port -d upgrade outdated
) might also help us pinpoint which ports are causing the problem.
Note: See
TracTickets for help on using
tickets.
Replying to jhi:
That could happen if there is a circular dependency in your outdated ports. MacPorts doesn't support circular dependencies, but sometimes they are accidentally introduced into the ports tree.
What are your outdated ports?