"sudo port -d selfupdate" fails to update MacPorts installation
Hi! For more than a week, "sudo port -d selfupdate" fails to update my MacPorts installation. All worked fine a week ago. The command output is: pmmbp:~ pmoura$ sudo port -d selfupdate DEBUG: Rebuilding the MacPorts base system if needed. Synchronizing from rsync://rsync.darwinports.org/dpupdate/dports receiving file list ... done sent 77 bytes received 234721 bytes 5944.25 bytes/sec total size is 14267567 speedup is 60.77 DEBUG: MacPorts base dir: /opt/local/var/db/dports/sources/ rsync.rsync.darwinports.org_dpupdate1/base DEBUG: Setting user: root DarwinPorts base version 1.320 installed DEBUG: Updating using rsync receiving file list ... done sent 77 bytes received 4524 bytes 296.84 bytes/sec total size is 2504037 speedup is 544.24 Downloaded MacPorts base version 1.320 The MacPorts installation is not outdated and so was not updated DEBUG: Setting ownership to root selfupdate done! I know for a fact that portfiles are update in the lat few days. I've no idea why updating is failing your help is appreciated. I'm running the latest version of MacOS X (10.4.9) on a MacBook Pro. All the best, Paulo ----------------------------------------------------------------- Paulo Jorge Lopes de Moura Dep. of Computer Science, University of Beira Interior 6201-001 Covilhã, Portugal Office 4.3 Ext. 3257 Phone: +351 275319891 Fax: +351 275319899 Email: <mailto:pmoura@di.ubi.pt> Home page: <http://www.di.ubi.pt/~pmoura> Research: <http://logtalk.org/> -----------------------------------------------------------------
On Mar 26, 2007, at 13:22, Paulo Moura wrote:
For more than a week, "sudo port -d selfupdate" fails to update my MacPorts installation. All worked fine a week ago. The command output is:
pmmbp:~ pmoura$ sudo port -d selfupdate DEBUG: Rebuilding the MacPorts base system if needed. Synchronizing from rsync://rsync.darwinports.org/dpupdate/dports receiving file list ... done
sent 77 bytes received 234721 bytes 5944.25 bytes/sec total size is 14267567 speedup is 60.77 DEBUG: MacPorts base dir: /opt/local/var/db/dports/sources/ rsync.rsync.darwinports.org_dpupdate1/base DEBUG: Setting user: root DarwinPorts base version 1.320 installed DEBUG: Updating using rsync receiving file list ... done
sent 77 bytes received 4524 bytes 296.84 bytes/sec total size is 2504037 speedup is 544.24 Downloaded MacPorts base version 1.320 The MacPorts installation is not outdated and so was not updated DEBUG: Setting ownership to root selfupdate done!
I know for a fact that portfiles are update in the lat few days. I've no idea why updating is failing your help is appreciated. I'm running the latest version of MacOS X (10.4.9) on a MacBook Pro.
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.
On 2007/03/26, at 22:37, Ryan Schmidt wrote:
I know for a fact that portfiles are update in the lat few days. I've no idea why updating is failing your help is appreciated. I'm running the latest version of MacOS X (10.4.9) on a MacBook Pro.
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'm quite familiar with DarwinPorts/MacPorts and with the semantics of the commands above. What I find hard to believe is that no portfile got updated in the last four or five days. E.g. I submitted an updated portfile for SWI-Prolog that got committed March 20 but so far the command above failed to retrieve it. I suspect some problem upstream related to server synchronization. Thanks anyway for your feedback. All the best, Paulo ----------------------------------------------------------------- Paulo Jorge Lopes de Moura Dep. of Computer Science, University of Beira Interior 6201-001 Covilhã, Portugal Office 4.3 Ext. 3257 Phone: +351 275319891 Fax: +351 275319899 Email: <mailto:pmoura@di.ubi.pt> Home page: <http://www.di.ubi.pt/~pmoura> Research: <http://logtalk.org/> -----------------------------------------------------------------
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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? - -- Paul Beard contact info: www.paulbeard.org/paulbeard.vcf pictures: http://www.flickr.com/photos/pdb206/ Are you trying to win an argument or solve a problem? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGCFzwfHLPwpj1/JQRAttTAJwLdRWiNCuFPe307j1mrqPsneVNPQCggY2P KFfKypUR9dRqEwXvnng4Oas= =STwd -----END PGP SIGNATURE-----
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.
participants (3)
-
Paul Beard
-
Paulo Moura
-
Ryan Schmidt