Hi Kenneth, Now it works here as well. When I tried yesterday, it didn’t but I only had time to look into this today. Unless the issue comes back I am inclined to agree: temporal hick-up at SF.
Thanks Joachim On 6 Mar 2018, at 15:14, Kenneth Hoste <[email protected]<mailto:[email protected]>> wrote: Hi Joachim, On 06/03/2018 14:58, Joachim Hein wrote: I am having grief building boost for intel 2018a (Boost-1.66.0-intel-2018a-Python-3.6.4.eb) it looks for the source at http://download.sourceforge.net/boost/boost_1_66_0.tar.gz, which doesn’t work any longer. This link still works fine for me, may be an issue with your local mirror, or perhaps (late) fallout from the SourceForge downtime this weekend? $ wget http://download.sourceforge.net/boost/boost_1_66_0.tar.gz --2018-03-06 15:12:54-- http://download.sourceforge.net/boost/boost_1_66_0.tar.gz Resolving download.sourceforge.net<http://download.sourceforge.net> (download.sourceforge.net<http://download.sourceforge.net>)... 216.105.38.13 Connecting to download.sourceforge.net<http://download.sourceforge.net> (download.sourceforge.net<http://download.sourceforge.net>)|216.105.38.13|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: http://downloads.sourceforge.net/project/boost/boost/1.66.0/boost_1_66_0.tar.gz [following] --2018-03-06 15:12:54-- http://downloads.sourceforge.net/project/boost/boost/1.66.0/boost_1_66_0.tar.gz Resolving downloads.sourceforge.net<http://downloads.sourceforge.net> (downloads.sourceforge.net<http://downloads.sourceforge.net>)... 216.105.38.13 Reusing existing connection to download.sourceforge.net:80<http://download.sourceforge.net:80>. HTTP request sent, awaiting response... 302 Found Location: https://vorboss.dl.sourceforge.net/project/boost/boost/1.66.0/boost_1_66_0.tar.gz [following] --2018-03-06 15:12:54-- https://vorboss.dl.sourceforge.net/project/boost/boost/1.66.0/boost_1_66_0.tar.gz Resolving vorboss.dl.sourceforge.net<http://vorboss.dl.sourceforge.net> (vorboss.dl.sourceforge.net<http://vorboss.dl.sourceforge.net>)... 5.10.152.194 Connecting to vorboss.dl.sourceforge.net<http://vorboss.dl.sourceforge.net> (vorboss.dl.sourceforge.net<http://vorboss.dl.sourceforge.net>)|5.10.152.194|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 101669839 (97M) [application/x-gzip] Saving to: ‘boost_1_66_0.tar.gz’ 100%[===========================================================================================================================================>] 101,669,839 7.48MB/s in 11s 2018-03-06 15:13:17 (8.76 MB/s) - ‘boost_1_66_0.tar.gz’ saved [101669839/101669839] $ sha256sum boost_1_66_0.tar.gz bd0df411efd9a585e5a2212275f8762079fed8842264954675a4fddc46cfcf60 boost_1_66_0.tar.gz regards, Kenneth A working URL is e.g. https://sourceforge.net/projects/boost/files/boost/1.66.0/boost_1_66_0.tar.gz, which looks as if sourceforge restructured their URLs. The config specifies source_urls = [SOURCEFORGE_SOURCE] sources = [‘%%(namelower)s_%s.tar.gz’ % ‘_’.join(version.split(‘.’))] which implies, if the change is general to all sourceforge projects, the SOURCEFORGE_SOURCE needs a general fix. Not sure this was reported before. Any comments? Should I put an issue report? Against easyconfigs or easyblocks?
