"sudo port -d selfupdate" fails to update MacPorts installation
paulbeard at gmail.com
Mon Mar 26 16:53:20 PDT 2007
-----BEGIN PGP SIGNED MESSAGE-----
On Mar 26, 2007, at 2:37 PM, Ryan Schmidt wrote:
> There's nothing wrong here. "sudo port selfupdate" is the same
> thing as "sudo port sync", only that it also updates your base
> MacPorts installation if necessary. MacPorts 1.320 is the latest
> version of MacPorts base, which you already have, so it did not
> update it. And just like "sudo port sync", it has synchronized your
> ports tree. Now you can say things like "port outdated" to see
> which ports might be outdated, and use "sudo port upgrade
> <portname>" to upgrade them.
I have to call bulldust on this. It's just not credible that no port
updates have been made in the past 3-4 days, especially if committers
have said they have made changes. Nor is it credible that several
committers had somehow botched their check-ins so that changes were
not propagated out. Shortly after this exchange, I ran port sync and
found 5 ports had been updated.
Whatever, it's fixed now. Is there any way to monitor this, besides
subscribing to the svn commit feed?
contact info: www.paulbeard.org/paulbeard.vcf
Are you trying to win an argument or solve a problem?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
-----END PGP SIGNATURE-----
More information about the macports-users