-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Dependency checksum mismatch #2468
Comments
I'm running into the same issue, using the steps described above allows to make build I see another difference in the go.sum
|
@csvoisard @tsgit Hum... |
go version go1.21.5 linux/amd64 I ran
which didn't help |
I can
|
clean finish with k9s executable in ./execs/k9s
|
I think this is due to git-lfs resolving/not resolving large file references in the repos being downloaded When I set the build succeeds and the checked out zip module files have lfs references seems related golang/go#41708 e.g. github.com/anchore/[email protected]/test-fixtures/assets/linux_amd64
while
gives
and
gives
where the files in test-fixtures/assets have been dereferenced |
so I wonder if golang or k9s could avoid lfs dereferencing by default to avoid this kind of confusion ? |
Apologies for the delayed response. I was running |
I use
Anyhow, avoiding git-lfs dereferencing of files via |
Describe the bug
Is a dependency checksum mismatch a bug? Or should I just rebuild the
go.sum
file?To Reproduce
Steps to reproduce the behavior:
I worked around the problem by rebuilding the
go.sum
file so that the new checksum does not fail the build:Expected behavior
make build
on fresh checkout ofmaster
branch completes without a dependency checksum failure.Versions (please complete the following information):
CentOS Linux release 7.4.1708
master branch as of 12 Jan 2024
v1.27.4+k3s1
The text was updated successfully, but these errors were encountered: