Good news: I managed to replace !makeMTX by !new_mtx.
Bad news:
- Strange enough, the "commit" field of the ticket has not been correctly set, I needed to edit it manually.
- THE PACKAGE DOES NOT EVEN START TO BUILD. ARRGHH!!!
I have posted the tar ball in its original location (see ticket description). The attempt to install the package ends in an infinite loop:
...
[p_group_cohomology-3.0] Installing p_group_cohomology-3.0
[p_group_cohomology-3.0] Warning: This package has a badly-behaved setup.py which outputs
[p_group_cohomology-3.0] more than the package name for 'setup.py --name'; using the last
[p_group_cohomology-3.0] line as the package name: pGroupCohomology
[p_group_cohomology-3.0] Skipping pGroupCohomology as it is not installed.
[p_group_cohomology-3.0] Skipping pGroupCohomology as it is not installed.
[p_group_cohomology-3.0] Skipping pGroupCohomology as it is not installed.
[p_group_cohomology-3.0] Skipping pGroupCohomology as it is not installed.
[p_group_cohomology-3.0] Skipping pGroupCohomology as it is not installed.
[p_group_cohomology-3.0] Skipping pGroupCohomology as it is not installed.
[p_group_cohomology-3.0] Skipping pGroupCohomology as it is not installed.
[p_group_cohomology-3.0] Skipping pGroupCohomology as it is not installed.
...
Of course it is not installed! That's why I want to install it, stupid!
Can you explain what is going wrong here?
I noticed that the python setup.py --name results in a compilation of the cython files, which certainly shouldn't happen. How to prevent it?
But if I understand correctly, the installation went past that point and did correctly obtain the package name. So, why does it REPEATEDLY complain that the package to be installed is not installed.
