go.sum: Fix checksum mismatch #131
No reviewers
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#131
Loading…
Reference in New Issue
No description provided.
Delete Branch "fix-hash"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
It produced an error for me:
Checklist
go mod vendor
make do-the-swag
)I'm a bit confused where the mismatch comes from. Do we have both file trees of that dependency and can do a diff check?
This seems to be an issue with the module itself, it also fails when creating a new project and
go get
inggithub.com/go-xorm/tests
. I'll try to check this with the creator of the package.If you only want to build the api, you should be able to use the committed dependencies in the
vendor/
folder with the-mod=vendor
flag. Alternatively, you can use the Makefile, take a look at the makefile docs@shilch Yes, they are located in
vendor/
.I do not see
github.com/go-xorm/tests
in the vendor directory so I am not sure with what I should diff it.I am trying to package Vikunja for NixOS distro and using vendored dependencies is discouraged in our policies.
It seems like the original repo has been archived since, but we don't even have that in vendor... i wonder why it even appears in the
go.sum
file.Yeah, I can see all the disatavanteges it brings, and it most certainly is not a solution. The committed dependencies are back from when there was no such thing as
GOPROXY
to backup dependencies.Packaging Vikunja for nixos is great! I'm also using nix as my main distro, you can ping me once you have the pr ready and I'll take a look :)
It seems like the xorm path has been moved and updated since the version I've put in Vikunja has been released. I'll update xorm in a seperate PR, maybe that also fixes the issue here.
I've updated xorm, can you pull and try again?
Fixed by vikunja/api#133
Pull request closed