MacPorts-1.6.0-10.5-Leopard.dmg Install Failure

[Ryan Schmidt]

On May 6, 2008, at 8:14 AM, Merton Campbell Crockett wrote:

> On 05 May 2008, at 20:31:16, Ryan Schmidt wrote:
>
>> On May 5, 2008, at 13:01, Merton Campbell Crockett wrote:
>>
>>> The following install step failed:  run postflight script for  
>>> MacPorts-1.6.0.  Contact the software manufacturer for assistance.
>>>
>>>
>>> It's been a long time since I've used the package installer.   
>>> What's wrong?  What other options are there for installing ports  
>>> to build some of the networking software that I need?
>>
>> The 1.6.0 disk image installer packages try to run "port sync"  
>> after installation, to update the ports tree. If this fails, the  
>> message you encountered is printed.
>>
>> Is the rsync port blocked on your network? If so, unblock it if  
>> possible.
>
> Our corporate parent has imposed some draconian security measures  
> on its subsidiaries.  What ports and IP addresses are involved to  
> maintain the Mac Ports environment?
>
> What is the difference between "port sync" and "port -d selfupdate"  
> in terms ports and IP addresses?

"port sync" updates your ports. It uses rsync (port 873 to  
rsync.macports.org) by default but you can have it use a Subverion  
working copy instead which uses HTTP (port 80 to svn.macosforge.org).  
To set this up, check out a working copy of the dports directory  
anywhere on your hard drive (svn checkout http://svn.macosforge.org/ 
repository/macports/trunk/dports /anywhere/you/want) and then point  
sources.conf at that directory (comment the rsync line, add a new  
line with the file:///-protocol URL to your working copy of dports).

"port selfupdate" updates your ports and also your MacPorts base.  
The latter part can only occur over rsync. If you cannot enable rsync  
on your network, you will have to manually download and compile the  
source of MacPorts base to update to new versions.