cannot deactivate any port

[thabangh@…]

I am running MacPorts under Snow Leopard, and something seems to be messed up in such a way that various ports cannot be deactivated. Here is an example:

bash-3.2$ sudo port deactivate freetype @2.3.12_0+macosx
--->  Deactivating freetype @2.3.12_0+macosx

This command hangs forever. Nothing appears in the log file. The only way to stop it is with a "sudo kill <pid>" command. Is there any way to get more verbose output from the port command, so that I can find out what's going wrong? Can I deactivate the port manually?

The same thing happens with other "deactivate" commands. I think the problem might have arisen because I issued the command "sudo port upgrade outdated" and then lost internet connectivity while the command was still executing.

[thabangh@…]

Here is some more insight, perhaps, into this problem. The following command generates an explicit error and the attached log file.

bash-3.2$ sudo port install gconf
--->  Computing dependencies for gconf
--->  Building gconf
Error: Target org.macports.build returned: shell command failed
Log for gconf is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gconf/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

[jmroot (Joshua Root)]

Please remember WikiFormatting for your preformatted text. The gconf build failure seems unrelated and should go in a separate ticket. Please attach debug output, i.e. the result of sudo port -d deactivate freetype.

[thabangh@…]

As requested, I re-ran the command with the "-d" option, but got no output either on the command line or in the log file.

bash-3.2$ sudo port -d deactivate freetype
--->  Deactivating freetype

[ryandesign (Ryan Carsten Schmidt)]

Replying to jmr@…:

The gconf build failure seems unrelated and should go in a separate ticket.

This has now been filed as #25818.

[ryandesign (Ryan Carsten Schmidt)]

Replying to thabangh@…:

As requested, I re-ran the command with the "-d" option, but got no output either on the command line or in the log file.

Really? In debug mode, there should have been about a dozen additional lines before "---> Deactivating freetype" was printed, and likely more after. Try again? Note the "-d" has no effect unless it goes immediately after the word "port", before the word "deactivate".

[thabangh@…]

Honest! I cut and pasted the command line and the output in my previous entry. I just tried it again. I don't get anything different when I do "sudo port deactivate freetype" versus "sudo port -d deactivate freetype".

Is there anything else I should try?

[mf2k (Frank Schima)]

Replying to thabangh@…:

Is there anything else I should try?

Just curious, what is the output of the following?

port version

[jmroot (Joshua Root)]

Do you perhaps have another port process running? Check with

ps -A | grep tclsh

[thabangh@…]

The output of "port version" is "Version: 1.9.1."

The output of "ps -A | grep tclsh" is

27349 ??         0:26.15 /usr/bin/tclsh /opt/local/bin/port upgrade gnucash
50814 ??         0:15.09 /usr/bin/tclsh /opt/local/bin/port upgrade outdated
54345 ??         0:07.12 /usr/bin/tclsh /opt/local/bin/port upgrade outdated
54663 ??         0:07.21 /usr/bin/tclsh /opt/local/bin/port upgrade outdated
57307 ttys003    0:00.00 grep tclsh

So this seems like a problem, eh?

I killed all those processes, and now I can successfully deactivate freetype.

Thanks.