Opened 14 years ago

Last modified 14 years ago

#25800 closed defect

cannot deactivate any port — at Version 2

Reported by: thabangh@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: base Version: 1.9.1
Keywords: Cc:
Port:

Description (last modified by jmroot (Joshua Root))

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.

Change History (3)

comment:1 Changed 14 years ago by 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>

Changed 14 years ago by thabangh@…

Attachment: main.log added

comment:2 Changed 14 years ago by jmroot (Joshua Root)

Component: portsbase
Description: modified (diff)

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.

Note: See TracTickets for help on using tickets.