"sudo port -d selfupdate" fails to update MacPorts installation

[Ryan Schmidt]

On Mar 26, 2007, at 18:53, Paul Beard wrote:

> 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.

Yeah, sorry for answering the wrong question; I thought the complaint  
was that MacPorts base wasn't being updated. I didn't realize the  
complaint was that rsync wasn't working.

> Whatever, it's fixed now. Is there any way to monitor this, besides  
> subscribing to the svn commit feed?

Not sure... I've been using svn instead of rsync for my ports tree  
for months so I didn't notice the problem.