Fix the checksums for package ctypes_stubs_js-0.1 #23589
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
has most likely been recompressed with new parameters.
|
Some CI jobs succeed while others fail to obtain a tarball that matches the new checksum: |
|
This checksum inconsistency is due to a bug in gitlab (the content of a This issue is being resolved by gitlab. They estimate the fix will be deployed today or tomorrow: https://gitlab.com/gitlab-org/gitlab/-/issues/402616 The reason some of the jobs work is probably due to caching: old tarballs are not redownloaded by opam if they are in the cache. I'm closing this PR because it'd need to be reverted very soon. |
This was referenced Mar 29, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I haven't checked the package contents. Is there an easy way to do so? I haven't been able to locate the old tarball cached by opam on my machine if there is one.
Update: given that the GitLab website is healthy and serves that tarball, there's no reason to trust it less than usual.
Closes #23587