python34 @3.4.0_1: activation fails if another python selected

[mndavidoff (Monte Davidoff)]

Installing python34 fails during activation if I have previously selected another python port as the default.

$ sudo port select --set python none
Selecting 'none' for 'python' succeeded. 'none' is now active.
$ ls -l /opt/local/bin/2to3
ls: /opt/local/bin/2to3: No such file or directory
$ sudo port select --set python python27
Selecting 'python27' for 'python' succeeded. 'python27' is now active.
$ ls -l /opt/local/bin/2to3
lrwxr-xr-x  1 root  admin  23 Mar 22 09:16 /opt/local/bin/2to3 -> /opt/local/bin/2to3-2.7
$ sudo port -vs install python34
...
x ./Applications/MacPorts/Python 3.4/IDLE.app/Contents/Resources/PythonSource.icns
x ./Applications/MacPorts/Python 3.4/IDLE.app/Contents/MacOS/IDLE
x ./Applications/MacPorts/Python 3.4/IDLE.app/Contents/MacOS/Python
Error: org.macports.activate for port python34 returned: Image error: /opt/local/bin/2to3 already exists and does not belong to a registered port.  Unable to activate port python34. Use 'port -f activate python34' to force the activation.
Please see the log file for port python34 for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_python34/python34/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port python34 failed

The problem may have been introduced in r118099. The problem did not occur with python34 @3.4.0_0.

[michaelld (Michael Dickens)]

Yes, this issue was introduced in r118099:

% tar jtvf /opt/local/var/macports/software/python34/python34-3.4.0_0+universal.darwin_12.i386-x86_64.tbz2  | grep bin/2to3
lrwxr-xr-x  0 root   admin       0 Mar 17 09:13 ./opt/local/bin/2to3-3.4 -> /opt/local/Library/Frameworks/Python.framework/Versions/3.4/bin/2to3-3.4
-rwxr-xr-x  0 root   wheel     150 Mar 17 09:13 ./opt/local/Library/Frameworks/Python.framework/Versions/3.4/bin/2to3-3.4

% tar jtvf /opt/local/var/macports/software/python34/python34-3.4.0_1+universal.darwin_12.i386-x86_64.tbz2  | grep bin/2to3
lrwxr-xr-x  0 root   admin       0 Mar 22 10:54 ./opt/local/bin/2to3 -> /opt/local/Library/Frameworks/Python.framework/Versions/3.4/bin/2to3
lrwxr-xr-x  0 root   admin       0 Mar 22 10:54 ./opt/local/bin/2to3-3.4 -> /opt/local/Library/Frameworks/Python.framework/Versions/3.4/bin/2to3-3.4
lrwxr-xr-x  0 root   wheel       0 Mar 22 10:54 ./opt/local/Library/Frameworks/Python.framework/Versions/3.4/bin/2to3 -> 2to3-3.4
-rwxr-xr-x  0 root   wheel     150 Mar 22 10:54 ./opt/local/Library/Frameworks/Python.framework/Versions/3.4/bin/2to3-3.4

Looks like a post-destroot to delete those "bin/2to3" symlinks is in order. Or, something like that.

[michaelld (Michael Dickens)]

Cc Me!

[mndavidoff (Monte Davidoff)]

Please see #41549 (r113947), which r118099 reverted.

[petrrr]

Cc Me!

[michaelld (Michael Dickens)]

Still have to rev-bump python34 ...

[michaelld (Michael Dickens)]

Latest svn trunk still didn't work for me just now, even after uninstalling, cleaning, updating other stuff, etc... same issue.

[mndavidoff (Monte Davidoff)]

There appears to be a reason we need "frameworkinstall maninstall" instead of "altinstall", so I'm attaching a patch that fixes the problem by removing the versionless symlinks in post-destroot, similar to the python27 Portfile. I don't know if this is the best way to fix the problem.

[petrrr]

Replying to michaelld@…:

Latest svn trunk still didn't work for me just now, even after uninstalling, cleaning, updating other stuff, etc... same issue.

I do not see that anything changed which would fix this issue. Apparently r118099 introduces this issue and it is still in place. If you need a quick fix you could execute a sudo port select python none, install python34 and select your preferred python interpreter again. It is not very clean, but solves the problem temporary.

[skymoo (Adam Mercer)]

Cc Me!

[jyrkiwahlstedt]

done in r118159