I changed a lot of stuff on our base sources on svn last night and worked on the new rsycn server, so I expect a little turmoil before things settle down again and start working seamlessly. I guess the main issue is that DNS entries still haven't propagated from the old rsync server to the new one. I'll see to that personally but I'm sure once that's through everything should be fine again! Give us some time and we'll post with a status update on the problem, thanks for your patience! Regards,... -jmpp On Jun 15, 2007, at 12:31 PM, paul beard wrote:
On Jun 15, 2007, at 6:16 AM, Bill Hernandez wrote:
Any ideas, what I need to do to correct these errors other than not use the "-d" flag ?
I don't think that would correct them: that would be akin to sticking black tape over the warning lights in your car ;-)
Your output should look something like this:
white:~ root# port -d selfupdate DEBUG: Rebuilding the MacPorts base system if needed. DEBUG: Synchronizing dports tree(s)
<snip>
sent 77 bytes received 263980 bytes 16003.45 bytes/sec total size is 14730546 speedup is 55.79 DEBUG: MacPorts base dir: /opt/local/var/db/dports/sources/ rsync.rsync.darwinports.org_dpupdate1/base DEBUG: Setting user: root DarwinPorts base version 1.442 installed DEBUG: Updating using rsync receiving file list ... done ./ <snip>
sent 22803 bytes received 13465 bytes 5579.69 bytes/sec total size is 2093103 speedup is 57.71 Downloaded MacPorts base version 1.442 The MacPorts installation is not outdated and so was not updated DEBUG: Setting ownership to root selfupdate done!
-- Paul Beard words: http://paulbeard.org/wordpress pictures: http://www.flickr.com/photos/pdb206/ Are you trying to win an argument or solve a problem?
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users