Just checked the ticket #34599 that was related to mine and decided to do a selfupdate and sudo port upgrade outdated and I got this:
jaspersmbp:wpscan jasper$ sudo port selfupdate ---> Updating MacPorts base sources using rsync MacPorts base version 2.1.1 installed, MacPorts base version 2.1.1 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 jaspersmbp:wpscan jasper$ port upgrade outdated Error: No ports matched the given expression Never had this before. How can this happen and how do I remedy this? On Mon, Jun 11, 2012 at 2:33 PM, MacPorts <[email protected]> wrote: > #34825: evolution-data-server fails to install > > -------------------------------------+-------------------------------------- > Reporter: jasperfrumau@… | Owner: macports-tickets@… > Type: defect | Status: closed > Priority: Normal | Milestone: > Component: ports | Version: 2.1.1 > Resolution: duplicate | Keywords: > Port: | > > -------------------------------------+-------------------------------------- > Changes (by jeremyhu@…): > > * status: new => closed > * resolution: => duplicate > > > Comment: > > #34599 > > -- > Ticket URL: <https://trac.macports.org/ticket/34825#comment:1> > MacPorts <http://www.macports.org/> > Ports system for Mac OS >
_______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
