Opened 9 years ago
Closed 9 years ago
#48698 closed defect (invalid)
MacPorts: install hangs/remains unusable
Reported by: | kasimir@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 2.3.3 |
Keywords: | Cc: | ||
Port: |
Description
I've been trying to install MacPorts on a new Mac Pro with a fresh, fully updated Yosemite OS. The installer hangs on 'Running package scripts'. So I tried to build it from source. That works, with the installer stating:
Congratulations, you have successfully installed the MacPorts system.
However, it seems unusable. When I do sudo port install apache2 I get the message:
Error: Port apache2 not found Simply trying to do a 'self update' (as root):
sh-3.2# port -d selfupdate DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs ---> Updating MacPorts base sources using rsync receiving file list ... done base.tar
...and then nothing... I've waited for half an hour, but it won't go any further. I can't find any logs either.
Again: there's nothing special about my setup, it's out-of-the-box Yosemite, only updated through the App store and, of course, I've installed Xcode with command line utilities and formally accepted the license, as is required according to the MacPorts site.
I've also tried uninstalling it, using the instructions from the MacPorts site, and reinstalling. But it does not make a difference.
I've read quite a few forum posts, but I can't find any post relating a problem like this. I hope you can shed some light on this.
Change History (4)
comment:1 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Component: | ports → base |
---|
comment:2 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Either that, or the network is so slow that it is taking a long time to download the port definitions. While running selfupdate, did you check in Activity Monitor or Network Utility whether any information is actually being transmitted over the network? If it is, try waiting longer.
comment:3 Changed 9 years ago by kasimir@…
This issue has been resolved, it was indeed a rsync problem. Because there were no errors, rather just an extremely slow connection (apparently), it was hard to see what was going wrong or holding up the process.
rsync works okay now, so I successfully ran selfupdate, etc.
I've also posted the question to stackoverflow: http://stackoverflow.com/questions/32177436/macports-install-hangs-remains-unusable (accepted answer is from a MacPorts dev)
comment:4 Changed 9 years ago by petrrr
Resolution: | → invalid |
---|---|
Status: | new → closed |
Looks like network issue, not Macports. Closing!
Everything you describe sounds like your network is not allowing you to access our rsync server.