Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libdap 3.19.1 source checksum fails #5471

Closed
hajgato opened this issue Dec 5, 2017 · 7 comments
Closed

libdap 3.19.1 source checksum fails #5471

hajgato opened this issue Dec 5, 2017 · 7 comments
Milestone

Comments

@hajgato
Copy link
Collaborator

hajgato commented Dec 5, 2017

Just tried to build libdap 3.19.1 (PR #5384, from 2 weeks ago), and the checksum of the source fails.

== 2017-12-05 21:57:03,092 filetools.py:700 DEBUG Computed sha256 checksum for /apps/brussel/sources/l/libdap/libdap-3.19.1.tar.gz: fb7014b6047cf3fa47d05c0faf258636f664c5fc232ff0886a78dfc5aae29f8f (correct checksum: 5215434bacf385ba3f7445494ce400a5ade3995533d8d38bb97fcef1478ad33e)

@boegel Thughts?

@boegel
Copy link
Member

boegel commented Dec 5, 2017

Here's what I have:

$ sha256sum /prefix/sources/l/libdap/libdap-3.19.1.tar.gz
5215434bacf385ba3f7445494ce400a5ade3995533d8d38bb97fcef1478ad33e  /prefix/sources/l/libdap/libdap-3.19.1.tar.gz
[22:23:05] vsc40023@node2001:~/data $ ls -l /prefix/sources/l/libdap/libdap-3.19.1.tar.gz
-rw-rw-r-- 1 vsc40023 vsc40023 2512834 Nov 21 21:29 /prefix/sources/l/libdap/libdap-3.19.1.tar.gz

If I re-download (using --force --sourcepath /tmp/$USER), the checksum indeed fails for me too:

$ sha256sum /tmp/vsc40023/l/libdap/libdap-3.19.1.tar.gz
fb7014b6047cf3fa47d05c0faf258636f664c5fc232ff0886a78dfc5aae29f8f  /tmp/vsc40023/l/libdap/libdap-3.19.1.tar.gz
$ ls -l !$
ls -l /tmp/vsc40023/l/libdap/libdap-3.19.1.tar.gz
-rw-rw-r-- 1 vsc40023 vsc40023 2493230 Dec  5 22:26 /tmp/vsc40023/l/libdap/libdap-3.19.1.tar.gz

There's little else we can do other than:

  • issue a PR to fix the checksum
  • reach out to the developers and ask them what is going on (and ask them to please stop doing it)

@boegel boegel added this to the 3.5.0 milestone Dec 5, 2017
@hajgato
Copy link
Collaborator Author

hajgato commented Dec 5, 2017

@boegel you did the PR 14 days ago (around 20th November), and I checked the date of the source file and it is from 3rd December. It seems that they changed the source after you did the easyconfig.

@boegel
Copy link
Member

boegel commented Dec 6, 2017

@hajgato Indeed, so there's little else we can do than i) update the checksum, ii) ask them to stop doing in-place updates.

@hajgato
Copy link
Collaborator Author

hajgato commented Dec 6, 2017

@boegel will do the PR.

@boegel
Copy link
Member

boegel commented Dec 6, 2017

fixed in #5473

@boegel boegel closed this as completed Dec 6, 2017
@zao
Copy link
Contributor

zao commented May 3, 2018

Checksum is reverted to 5215434bacf385ba3f7445494ce400a5ade3995533d8d38bb97fcef1478ad33e upstream now.
Of course, the website doesn't even have a 3.19.1 page.

@boegel
Copy link
Member

boegel commented May 8, 2018

@zao Fixed in #6305

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants