2016-04-13 18:59 GMT+02:00 Kenneth Hoste <[email protected]>: > Fix using the alternate download URL for bitstring is in > https://github.com/hpcugent/easybuild-easyconfigs/pull/2880. > > On 13/04/16 18:34, Kenneth Hoste wrote: > > Hi Yann, > > On 13/04/16 16:11, Yann Sagon wrote: > > 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? > > > This is a known issue, see also > https://github.com/hpcugent/easybuild-easyconfigs/pull/2819 (and > https://github.com/scott-griffiths/bitstring/issues/159). > > We will probably need to change the download URL for this specific version > of bitstring to GitHub. > > As a workaround, it should be fine to download the tarball manually from > the official GitHub repo into the source path where EasyBuild expects to > find files, from > https://github.com/scott-griffiths/bitstring/archive/bitstring-3.1.3.tar.gz > . > > > regards, > > Yann > > > Hello Kenneth,
Yes I was aware of the workaround, it was more a question to know what would be the correct way to contribute. But the issue is now closed, so I'll to contribute later:) Best -- 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
