#38601 closed defect (fixed)
py26-py: upgrade fails activation
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | akitada@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.3 |
Keywords: | Cc: | stromnov (Andrey Stromnov) | |
Port: | py26-py |
Description
$ port outdated py26-py The following installed ports are outdated: py26-py 1.1.1_0 < 1.4.13_0 $ sudo port -u upgrade py26-py ---> Computing dependencies for py26-pytest ---> Fetching distfiles for py26-pytest ---> Attempting to fetch pytest-2.3.4.zip from http://distfiles.macports.org/py-pytest ---> Attempting to fetch pytest-2.3.4.zip from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/py-pytest ---> Attempting to fetch pytest-2.3.4.zip from http://pypi.python.org/packages/source/p/pytest/ ---> Verifying checksum(s) for py26-pytest ---> Extracting py26-pytest ---> Applying patches to py26-pytest ---> Configuring py26-pytest ---> Building py26-pytest ---> Staging py26-pytest into destroot ---> Installing py26-pytest @2.3.4_0 ---> Activating py26-pytest @2.3.4_0 Error: org.macports.activate for port py26-pytest returned: Image error: /opt/local/Library/Frameworks/Python.framework/Versions/2.6/bin/py.test is being used by the active py26-py port. Please deactivate this port first, or use 'port -f activate py26-pytest' to force the activation. Please see the log file for port py26-pytest for details: /opt/local/var/macports/logs/_Users_rschmidt_macports_dports_python_py-pytest/py26-pytest/main.log Error: Problem while installing py26-pytest To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets
Deactivate hack needed perhaps?
Change History (2)
comment:1 follow-up: 2 Changed 12 years ago by stromnov (Andrey Stromnov)
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 Changed 12 years ago by EnekoGotzon
Replying to stromnov@…:
Yes, you're right. Thanks!
Fixed in r104680.
Yes, py27-py port perfectly upgraded on the machine on which the issue was reported. Thanks!
Note: See
TracTickets for help on using
tickets.
Yes, you're right. Thanks!
Fixed in r104680.