this morning I did a port -d selfupdate and then port outdated which revealed new versions of a number of python 2.5 things. When I tried to update python25, this is what I got: (and this error probably prevented all the other py25-<whatever> upgrades from succeeding... --Doug ---> Fetching python25 ---> Attempting to fetch Python-2.5.2.tar.bz2 from http:// www.python.org//ftp/python/2.5.2/ ---> Verifying checksum(s) for python25 ---> Extracting python25 ---> Applying patches to python25 ---> Configuring python25 ---> Building python25 with target all ---> Staging python25 into destroot ---> Deactivating python25 2.5.1_4+darwin_8 ---> Installing python25 2.5.2_0+darwin_8 ---> Activating python25 2.5.2_0+darwin_8 Error: Target org.macports.activate returned: Image error: /opt/local/ etc/select/python/python25 is being used by the active python_select port. Please deactivate this port first, or use the -f flag to force the activation. ---> Activating python25 2.5.2_0+darwin_8 Error: Activating python25 2.5.2_0 failed: Image error: /opt/local/ etc/select/python/python25 is being used by the active python_select port. Please deactivate this port first, or use the -f flag to force the activation.
Douglas Philips wrote:
this morning I did a port -d selfupdate and then port outdated which revealed new versions of a number of python 2.5 things. When I tried to update python25, this is what I got: (and this error probably prevented all the other py25-<whatever> upgrades from succeeding...
Reinstall python_select, sudo port -unf upgrade python_select Then activate python25, sudo port activate python25 The python25 select file was moved from the python_select port to the python25 port itself. But since python25 does not depend on python_select, port upgrade outdated could have done this in the wrong order. Rainer
participants (2)
-
Douglas Philips
-
Rainer Müller