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

Error installing version 1.2.0 #75

Closed
everflux opened this issue Sep 19, 2022 · 3 comments
Closed

Error installing version 1.2.0 #75

everflux opened this issue Sep 19, 2022 · 3 comments
Labels
bug Confirmed bug or issue done Implemented or fixed

Comments

@everflux
Copy link

Installing version v1.2.0 results in the following error, version v1.1.0 works as expected

$ go install github.com/darklynx/request-baskets@latest
go: downloading github.com/darklynx/request-baskets v1.2.0
go: github.com/darklynx/request-baskets@latest: github.com/darklynx/[email protected]: parsing go.mod:
	module declares its path as: darklynx/request-baskets
	        but was required as: github.com/darklynx/request-baskets
@darklynx
Copy link
Owner

darklynx commented Sep 19, 2022

Hi @everflux ,

Thank you for reporting the issue!

I think you are right, it seems to be an error in go.mod declaration.

I believe it should be 🤔 :

module github.com/darklynx/request-baskets

@darklynx darklynx mentioned this issue Sep 19, 2022
@darklynx
Copy link
Owner

it should be fixed now, please check
I get the following output:

# go install github.com/darklynx/request-baskets@latest
go: downloading github.com/darklynx/request-baskets v1.2.1
go: downloading github.com/go-sql-driver/mysql v1.6.0
go: downloading github.com/julienschmidt/httprouter v1.3.0
go: downloading github.com/lib/pq v1.10.7
go: downloading go.etcd.io/bbolt v1.3.6
go: downloading golang.org/x/sys v0.0.0-20220919091848-fb04ddd9f9c8

@darklynx darklynx added bug Confirmed bug or issue done Implemented or fixed labels Sep 19, 2022
@everflux
Copy link
Author

Yes, the issue is indeed solved with 1.2.1. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bug or issue done Implemented or fixed
Projects
None yet
Development

No branches or pull requests

2 participants