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: Help remove the package #41844

viney-shih opened this issue Oct 7, 2020 · 4 comments

x/pkgsite: Help remove the package #41844

viney-shih opened this issue Oct 7, 2020 · 4 comments


Copy link

@viney-shih viney-shih commented Oct 7, 2020

What is the URL of the page with the issue?

What is your user agent?

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.102 Safari/537.36



What did you do?

I am the author of pachage goroutines. Please help remove I am going to register another package name for it.

What did you expect to see?

page and it's related data in DB are removed

What did you see instead?

I am going to register goroutines but failed. I type the following command and returns as below.

❯ GOPROXY= GO111MODULE=on go get
go: downloading v1.0.0
go get: parsing go.mod:
        module declares its path as:
                but was required as:

@gopherbot gopherbot added the pkgsite label Oct 7, 2020
@gopherbot gopherbot added this to the Unreleased milestone Oct 7, 2020
Copy link

@jba jba commented Oct 7, 2020

Unfortunately our exclusion code will block if we exclude (it just looks for a prefix).

If you just change the go.mod of to have the same module path, that should fix your problem.

@jba jba self-assigned this Oct 7, 2020
@jba jba modified the milestones: Unreleased, pkgsite/unplanned Oct 7, 2020
Copy link

@viney-shih viney-shih commented Oct 8, 2020

@jba I have got your point and fixed go.mod issue.

However, I got two docs now. and

I want to keep goroutines version. Could you please remove for me?


Copy link

@jba jba commented Oct 8, 2020

This requires changing our exclusion logic, so it's not a simple fix. I'll start working on it shortly.

@jba jba added NeedsFix and removed NeedsInvestigation labels Oct 8, 2020
Copy link

@gopherbot gopherbot commented Oct 14, 2020

Change mentions this issue: internal/postgres: make exclusions work componentwise

gopherbot pushed a commit to golang/pkgsite that referenced this issue Oct 14, 2020
Change the way excluded prefixes match paths to work by path component.

Previously prefix "bad" would exclude "bad", "badness" and "bad/ness".
This CL makes it exclude "bad" (an exact match) and "bad/ness"
(component suffix), but not "badness".

For golang/go#41844

Change-Id: I021d8a7ba8816e3d356f883313ffe3eb53ec717d
Trust: Jonathan Amsterdam <>
Run-TryBot: Jonathan Amsterdam <>
TryBot-Result: kokoro <>
Reviewed-by: Julie Qiu <>
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.