Port upgrade outdated no longer plays nice

Jasper Frumau jasperfrumau at gmail.com
Mon Jun 11 16:26:10 PDT 2012

On Tue, Jun 12, 2012 at 1:58 AM, Lawrence Velázquez <
larry.velazquez at gmail.com> 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

Apparently it did not get installed yet either:

$ sudo port upgrade evolution-data-server
Error: evolution-data-server is not installed
To report a bug, follow the instructions in the guide:

but when I did a new selfupdate and upgrade outdated it started building
some outdated ports again so all is working. But then it tries to build
gnome-panel again and goes for evolution-data-server as that is needed for
Gnome Panel. And somehow this time it is installed successfully.

> vq
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20120612/5a897afa/attachment.html>

More information about the macports-users mailing list