py27-pymvpa: unable to execute 'swig': No such file or directory

[andytsai@…]

When I run

$ sudo port install py27-pymvpa

I get the following error:

Error: org.macports.build for port py27-pymvpa returned: command execution failed
Please see the log file for port py27-pymvpa for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-pymvpa/py27-pymvpa/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port py27-pymvpa failed

[mf2k (Frank Schima)]

In the future, please use WikiFormatting and Cc the port maintainers (port info --maintainers py-pymvpa), if any.

[kurthindenburg (Kurt Hindenburg)]

The simple fix is to add deps which appears to work w/ py27-; however, for the py34 it doesnt' appear to install any binaries; so if that's not correct, it needs further research.

-    depends_lib-append  port:py${python.version}-numpy \
-                        port:libsvm
+    depends_lib-append  port:py${python.version}-h5py \
+                        port:py${python.version}-nibabel \
+                        port:py${python.version}-numpy \
+                        port:py${python.version}-scipy \
+                        port:libsvm \
+                        port:swig

[ryandesign (Ryan Carsten Schmidt)]

​This problem is still happening.

[reneeotten (Renee Otten)]

see ​PR4990

[reneeotten (Renee Otten)]

In e53f025c347448135d14eb360da207a0a5f418d2/macports-ports (master):

py-pymvpa: update dependencies

• add missing swig-python as build dependency
• add required scipy and nibabel dependencies
• remove unneeded setuptools dependency

Fixes: #58796
See: #51691

[reneeotten (Renee Otten)]

In 6f39e802189a7ea5ed35dec0407893a52c3d0418/macports-ports (master):

py-pymvpa: install binaries and make them PY3-compatible

Upstream provided setup.py file makes Python code compatible using the
2to3 converstion tool. However, it does not include the files in "bin"
and, therefore, scripts were only installed for py27-pymvpa.

This commits resolves that issue in the pre/post-destroot phases as I
couldn't find a way of accomplishing it by patching the setup.py file...

Also added a note about limited PY3 compatibility (there are indeed more
test failures with py37-mvpa) and upstream's recommendation to use PY27.

Closes: #51691