-
Notifications
You must be signed in to change notification settings - Fork 683
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
Checksums have changed for all libxc versions #20417
Comments
Someone ran into this on Slack today, I took a look and it seems like there's not much stability in the checksums generated for these tarballs on GitLab. On the dual checksums, the first set is from when we used to take libxc sources from another site; GitLab as a source was added in late March this year in #20163 as the first place became defunct. This introduced a new checksum. Unfortunately, it seems like GitLab is still GitLab and doesn't necessarily have stable checksums on "release assets", which probably are generated on the fly from tags and other repo state. For example for
This might need some investigation into whether GitLab is being silly again with regard to stable archive generation. |
see also #20452 |
I've opened an issue upstream for this, since I'm not seeing any differences for other projects hosted on GitLab: https://gitlab.com/libxc/libxc/-/issues/511 |
Sorry, I just read through all the discussion. I only noticed that a few files are different since the last time the source was downloaded from Gitlab. I don't know whether they can be modified from Gitlab autogenerated tarball, but if so that may mean the history has been rebased?
|
I think it would be helpful if others also comment in https://gitlab.com/libxc/libxc/-/issues/511, to make it clear to the libxc team that this doesn't affect just me? |
Hi,
It looks like checksums have changes for all .tar.gz files downloaded by all (recent?) versions of
libxc
easyconfigs. The files are "release assets" on gitlab, I don't suppose those should change. Does anyone know if this is anyhow expected - I am wary of just changing the checksums in case something fishy is going on.Also, I notices that two checksums are given although only one file is downloaded, could that be because this has happened before and the new checksums have just been added to the list?
/Jakob
CC: @OleHolmNielsen
The text was updated successfully, but these errors were encountered: