Sent from my iPhone
On Jun 12, 2012, at 3:29, Ryan Schmidt <[email protected]> wrote: > > On Jun 11, 2012, at 13:58, Lawrence Velázquez wrote: > >> On Jun 11, 2012, at 7:07 a.m., Jasper Frumau wrote: >> >>> 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? >> >> I'm assuming you wanted to update evolution-data-server with r94167 >> (https://trac.macports.org/changeset/94167). >> >> Since this changeset didn't increase evolution-data-server's version, >> revision, or epoch, MacPorts doesn't consider it outdated. Upgrade it >> directly: >> >> sudo port upgrade evolution-data-server > > That won't do anything. > > If you don't already have the port installed, MacPorts will tell you it can't > upgrade a port you don't have installed. That I found out yeah. > "sudo port clean evolution-data-server && sudo port install > evolution-data-server" if you want to install it for the first time. I think the patch got committed as I got it to build after a self update as it was needed for gnome panel. All good now. > > And if you do already have it installed, then because as you say there was no > change to the version, revision or epoch, asking MacPorts to upgrade it won't > do anything, because there's nothing to upgrade. > > r94167 just fixed a build problem with the latest version of automake. If you > had installed the port before automake was upgraded, you would not have > encountered the problem (and do not now need to rebuild anything). > > _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
