Opened 9 years ago

Closed 9 years ago

#49309 closed defect (duplicate)

Installation hanging

Reported by: FCSMARK@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: base Version: 2.3.4
Keywords: elcapitan Cc:
Port:

Description (last modified by ryandesign (Ryan Carsten Schmidt))

Followed step for migration. Latest release. Installation hangs. Console repeats the following :

16/10/15 13:13:39,329 UserEventAgent[49]: Failed to send message because the port couldn't be created.

I´m sure I am overlooking something very simple.

El Capitan Version 10.11

Apple LLVM version 7.0.0 (clang-700.0.72)
Target: x86_64-apple-darwin15.0.0
Thread model: posix
Xcode 7.0.1
Build version 7A1001

Change History (3)

comment:1 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Component: portsbase
Description: modified (diff)
Keywords: elcapitan added; ports could not be created removed
Summary: HangingInstallation hanging

How long did you wait? It is known that the initial install on El Capitan will take ten minutes or so, varying depending on your disk and CPU speed, because the portindex must be created. See #49050.

As far as I know, the message "Failed to send message because the port couldn't be created" is not caused by or related to MacPorts.

comment:2 Changed 9 years ago by FCSMARK@…

Thank you for the update. Installation ran for 38 minuted and completed. Terminal will not run Macports commands. I am not hopeful as I am not even able to uninstall with described removal script but here goes.

bash-3.2$ port outdated No ports are installed. bash-3.2$ $ port help selfupdate bash: $: command not found bash-3.2$ sudo port clean Password: Can't map the URL 'file://.' to a port description file ("Could not find Portfile in /Users/mac"). Please verify that the directory and portfile syntax are correct. To use the current port, you must be in a port's directory. bash-3.2$ /opt/local bash: /opt/local: is a directory bash-3.2$ cd /opt/local bash-3.2$ $ port help selfupdate bash: $: command not found

Version 0, edited 9 years ago by FCSMARK@… (next)

comment:3 in reply to:  2 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: duplicate
Status: newclosed

Replying to FCSMARK@…:

Thank you for the update. Installation ran for 38 minuted and completed.

Ok great. Then that's functioning normally. Once we get a server-side portindex for El Capitan initial installations won't take so long.

Terminal will not run Macports commands. I am not hopeful as I am not even able to uninstall with described removal script but here goes.

bash-3.2$ port outdated
No ports are installed.

This indicates no ports are outdated. This could be normal.

bash-3.2$ $ port help selfupdate
bash: $: command not found

You typed (or pasted) the dollar sign ($). Don't do that; it's meant to indicate the command prompt that the terminal shows you. Type (or paste) only the actual command (in this case, "port help selfupdate", without quotation marks).

bash-3.2$ sudo port clean
Password:
Can't map the URL 'file://.' to a port description file ("Could not find Portfile in /Users/mac").
Please verify that the directory and portfile syntax are correct.
To use the current port, you must be in a port's directory.

You didn't tell MacPorts what port you wanted it to clean. For example, if you want to clean the "zlib" port, type "sudo port clean zlib", without the quotes. If you want to clean all ports, type "sudo port clean all", without the quotes.

bash-3.2$ /opt/local 
bash: /opt/local: is a directory

The message is correct. /opt/local is a directory. It's not a command you can run.

bash-3.2$ cd /opt/local 
bash-3.2$ $ port help selfupdate
bash: $: command not found 

Again, don't type (or paste) the dollar sign ($).

It doesn't sound like anything is wrong with your MacPorts installation at this point. If you need further help using MacPorts or using your terminal, please write to the macports-users mailing list.

Note: See TracTickets for help on using tickets.