Hello,

I was trying to build SWIG-3.0.8-foss-2015a-Python-2.7.11.eb with
--try-toolchain=foss,2016a

It wasn't possible to download one of the python
package: bitstring-3.1.3.zip because it's not anymore the current version
and the archive doesn't exist.

What is the best practice? Change the source_urls of bitstring to another
one pointing to the same version of the package (on github for instance) or
upgrade the bitstring version so that the current source_urls is working
again?

Once done, should I do a PR to upgrade
the SWIG-3.0.8-foss-2015a-Python-2.7.11.eb or should I do a PR to create
the Python-2.7.11-foss-2016a.eb? Or both, or none:)

Is it possible to specify on the command line the bitstring version or ulr?

Thanks


-- 
Yann SAGON
Ingénieur système HPC
24 Rue du Général-Dufour
1211 Genève 4 - Suisse
Tél. : +41 (0)22 379 7737
[email protected] - www.unige.ch

Reply via email to