Closed stardiviner closed 7 years ago
Yes, this is normal. If a Go package can't be updated because its repository can't do a fast-forward git pull, then Go Package Store will print that message to stderr and not actually update the package successfully.
It behaves just like go get
does.
When this happens, you'll need to carefully resolve the problem yourself and return the repo to a state where it can be fast-forwarded. Either do that by reseting it's master to origin/master, or remove the repo and go get
it again.
One possible enhancement to Go Package Store is to display these errors in the frontend rather than stderr in console. That is an enhancement that may come later.
I see, thanks.
Here is the output:
This invalid fast-forward caused package update failed.