Hi all, When I have these sorts of issues with downloads I will usually end up using *wget* to manually download via the original URL (resuming multiple fails if needed) then move the file into the eb-srcs directory (in the right subdirectory). This will mean you don't need to potentially edit numerous Easyconfigs' checksum values. In this particular case, if the original site has long term reliability issues I would advocate that the Easyconfigs are re-pointed at the Gitlab endpoint instead.
Using wget in this case seemed to work (eventually) though: wget https://www.tddft.org/programs/libxc/down/6.0.0/libxc-6.0.0.tar.gz > --2023-03-28 11:31:59-- > https://www.tddft.org/programs/libxc/down/6.0.0/libxc-6.0.0.tar.gz > Resolving www.tddft.org (www.tddft.org)... 193.137.208.252 > Connecting to www.tddft.org (www.tddft.org)|193.137.208.252|:443... > connected. > HTTP request sent, awaiting response... 200 OK > Length: 62940412 (60M) [application/x-gzip] > Saving to: ‘libxc-6.0.0.tar.gz’ > > libxc-6.0.0.tar.gz 5%[> ] 3.51M 1.36MB/s in > 2.6s > > 2023-03-28 11:32:02 (1.36 MB/s) - Connection closed at byte 3686073. > Retrying. > > --2023-03-28 11:32:03-- (try: 2) > https://www.tddft.org/programs/libxc/down/6.0.0/libxc-6.0.0.tar.gz > Connecting to www.tddft.org (www.tddft.org)|193.137.208.252|:443... > connected. > HTTP request sent, awaiting response... 206 Partial Content > Length: 62940412 (60M), 59254339 (57M) remaining [application/x-gzip] > Saving to: ‘libxc-6.0.0.tar.gz’ > > libxc-6.0.0.tar.gz 13%[+=> ] 7.89M > 1.68MB/s in 2.6s > > 2023-03-28 11:32:06 (1.68 MB/s) - Connection closed at byte 8273205. > Retrying. > > ----SNIP---- > I also eventually downloaded https://www.tddft.org/programs/libxc/down/5.2.3/libxc-5.2.3.tar.gz successfully too. Fingers crossed these are correct: sha256sum libxc-* > 7b7a96d8eeb472c7b8cca7ac38eae27e0a8113ef44dae5359b0eb12592b4bcf2 > libxc-5.2.3.tar.gz > c2ca205a762200dfba2e6c9e8ca2061aaddc6b7cf42048859fe717a7aa07de7c > libxc-6.0.0.tar.gz Cheers, James. ------------------------------ [image: photo-logo] <https://www.sheffield.ac.uk/it-services/research> Dr James Moore Research Platforms System Administrator The University of Sheffield IT-Services | Research and Innovation IT p: 0114 222 3110 ext: 23110 a: IT Services, 10-12 Brunswick Street, Sheffield, S10 2FN w: https://www.sheffield.ac.uk/it-services/research tw: @RIT_Sheffield <https://twitter.com/rit_sheffield> @DrJKWMoore <https://twitter.com/DrJKWMoore> mast: @[email protected] <https://mast.hpc.social/@jkwmoore> e-alt: [email protected] e: [email protected] PGP keys @: https://keyserver.ubuntu.com/ <https://keyserver.ubuntu.com/pks/lookup?search=j.k.moore%40sheffield.ac.uk&fingerprint=on&op=index> [image: linkedin] <https://www.linkedin.com/in/jkwmoore> [image: github] <https://github.com/jkwmoore> [image: twitter] <https://twitter.com/rit_sheffield?lang=en> ------------------------------ Need a meeting with me? <https://calendar.app.google/mHDxS2gdnUHXfau37> On Tue, 28 Mar 2023 at 11:29, Ole Holm Nielsen <[email protected]> wrote: > Hi Loris, > > I'm being hit by that libxc download problem too! It's very bad for the > modules that we're trying to build :-( > > Should EB use this download URL in stead? > https://gitlab.com/libxc/libxc/-/archive/5.2.3/libxc-5.2.3.tar.gz > > Thanks, > Ole > > On 3/28/23 11:41, Loris Bennett wrote: > > The EC libxc-5.2.3-GCC-11.3.0.eb downloads the sources from > > > > https://www.tddft.org/programs/libxc > > > > However, the site seems to be having issues such that the download gets > > interrupted before it is complete. There are other places to get the > > sources from, i.e. > > > > https://gitlab.com/libxc/libxc > > > > and > > > > https://github.com/ElectronicStructureLibrary/libxc > > > > but the checksums for the version 5.2.3 are different in these two cases > > and both different from the checksum in the EC (the Github version is > > supposed to be a mirror of the Gitlab version). > > > > What should happen here? Should I wait and hope that www.tddft.org > > stops being so flaky, or should the EC (or at least the next version > > thereof) be changed to use Gitlab as the source, since this now seems to > > be the place were development occurs? >
