Hi,
I'd like to transfer a Go repository to another Github organization but
somehow make the "go install" still able to install the old releases using
the new import path. Is this possible?
I did the transfer using the Github UI, and updated the go.mod and all
imports to use the new project path, but now I'm unable to install the
existing releases using the new import path.
Example:
works: go install github.com/old/project/cmd@v1.0.0
The "github.com/old/project" repository now automatically redirects to
"github.com/new/project" (Github Feature).
But this fails: go install github.com/new/project/cmd@v1.0.0
error below:
go: github.com/new/project/cmd@v1.0.0: github.com/new/project@v1.0.0:
parsing go.mod:
module declares its path as: github.com/old/project
but was required as: github.com/new/project
If I clone the "github.com/new/project" repository then everything works
fine (go build, go test, etc) but only "go install" fails...
Is there a solution?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/982b04de-5f8d-41ca-a8b0-7760f65218dfn%40googlegroups.com.
