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

[BUG] The checksums files published are not usable #2236

Open
rbauduin opened this issue Oct 24, 2024 · 0 comments
Open

[BUG] The checksums files published are not usable #2236

rbauduin opened this issue Oct 24, 2024 · 0 comments
Labels
area/runtime-proxy kind/bug Create a report to help us improve

Comments

@rbauduin
Copy link

What happened:
I want to validated the integrity of the downloaded file using the published checksums file, but the filename in the checksums file is incorrect as it doesn't correspond to the name of the downloaded file.
What you expected to happen:
Both names should be identical so I can run sha256sum -c checksums.txt
How to reproduce it (as minimally and precisely as possible):
Download both
https://github.com/koordinator-sh/koordinator/releases/download/v1.5.0/koord-runtime-proxy_.1.5.0_.linux_x86_64
https://github.com/koordinator-sh/koordinator/releases/download/v1.5.0/checksums.txt

and run sha256sum -c checksums.txt to get the error

$ sha256sum -c checksums.txt 
sha256sum: koord-runtime-proxy_1.5.0_linux_x86_64: No such file or directory
koord-runtime-proxy_1.5.0_linux_x86_64: FAILED open or read
sha256sum: WARNING: 1 listed file could not be read

Seems the published file has additional underscores in its name
Anything else we need to know?:
This inconsistency also prevents automated checksums checking with https://github.com/asfaload/asfald, a tool I'm working on.

@rbauduin rbauduin added the kind/bug Create a report to help us improve label Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/runtime-proxy kind/bug Create a report to help us improve
Projects
None yet
Development

No branches or pull requests

2 participants