You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, while trying to install Topaz using the setup instructions, I encountered an issue with go install:
$ go install github.com/aserto-dev/topaz/cmd/topaz@latest
go: github.com/aserto-dev/[email protected] requires go >= 1.23.4; switching to go1.23.5
go: github.com/aserto-dev/topaz/cmd/topaz@latest (in github.com/aserto-dev/[email protected]):
The go.mod file for the module providing named packages contains one or
more replace directives. It must not contain directives that would cause
it to be interpreted differently than if it were the main module.
This prevented the Topaz binary from building. As a workaround, I had to first bring Topaz (and its dependencies) into a temporary Go module, then do a versionless install:
$ cd ~
$ mkdir topaz
$ cd topaz
$ go mod init topaz
$ go get github.com/aserto-dev/topaz/cmd/topaz@latest
$ export GOBIN=$HOME/topaz
$ go install github.com/aserto-dev/topaz/cmd/topaz
$ ~/topaz/topaz # successfully executes
Would it be possible to make the necessary adjustments so that go install ... topaz@latest works as expected?
The text was updated successfully, but these errors were encountered:
If you have a local clone, you should be able to use go install ./cmd/topaz/
I will look at removing the redirect; I am not sure how long-lasting this will be, as we will be moving to a mono-repo at some point in the near future, which will require redirects as well.
Hello, while trying to install Topaz using the setup instructions, I encountered an issue with
go install
:This prevented the Topaz binary from building. As a workaround, I had to first bring Topaz (and its dependencies) into a temporary Go module, then do a versionless install:
Would it be possible to make the necessary adjustments so that
go install ... topaz@latest
works as expected?The text was updated successfully, but these errors were encountered: