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

x/pkgsite: #41661

dgoffredo opened this issue Sep 27, 2020 · 2 comments

x/pkgsite: #41661

dgoffredo opened this issue Sep 27, 2020 · 2 comments


Copy link

@dgoffredo dgoffredo commented Sep 27, 2020

What is the URL of the page with the issue?

What is your user agent?

Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0


Screenshot from 2020-09-27 15-42-09

What did you do?

I searched for my recently-created Go package, and the website says that my project does not have one of the whitelisted licenses. I then changed the license (from SQLite to Unlicense), and waited a while (caches, I figure) before refreshing on multiple browsers. still doesn't like the license. You can see that my project uses the Unlicense here:

What did you expect to see?

I expected to see a rendering of my projects documentation, as is currently shown on the older website

What did you see instead?

I saw the aforementioned license restriction message.

@gopherbot gopherbot added the pkgsite label Sep 27, 2020
@gopherbot gopherbot added this to the Unreleased milestone Sep 27, 2020
Copy link

@jamalc jamalc commented Sep 28, 2020

Your module is not valid because its path is incorrectly declared in your go.mod file. The about page has more information on adding a package to You can see details when you attempt to download your module from the module proxy with the steps listed.

❯ GOPROXY= GO111MODULE=on go get
go: upgrade => v0.0.0-20200927192038-4d50eff3369e
go get: parsing go.mod:
	module declares its path as:
	        but was required as:

Once you've updated the go.mod file go get the new version through the module proxy. After a few minutes the documentation should be visible on

@jamalc jamalc closed this Sep 28, 2020
Copy link

@dgoffredo dgoffredo commented Sep 29, 2020

Following your instructions resolved the issue, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.