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
Bug Description
Installation failure message under mage installation
What did you do?
Install go in my home directory
Try to install mage
What did you expect to happen?
I expected the install to work.
What actually happened?
mage doesn't install
Environment
Mage Version: 1.15.0
OS: Ubuntu 22.04
Additional context
Erro message after go run bootstrap.go:
warning: GOPATH set to GOROOT (/home/user/go-1.22.4) has no effect
warning: GOPATH set to GOROOT (/home/user/go-1.22.4) has no effect
Running target: Install
exec: go "env" "GOBIN"
warning: GOPATH set to GOROOT (/home/user/go-1.22.4) has no effect
exec: git "rev-parse" "--short" "HEAD"
exec: git "describe" "--tags"
exec: go "build" "-o" "/home/user/go-1.22.4/mage" "-ldflags=-X \"github.com/magefile/mage/mage.timestamp=2024-06-13T14:45:35+03:00\" -X \"github.com/magefile/mage/mage.commitHash=2385abb\" -X \"github.com/magefile/mage/mage.gitTag=v1.15.0-5-g2385abb\"" "github.com/magefile/mage"
After second approach to instal via command go get -u -d github.com/magefile/mage:
go: go.mod file not found in current directory or any parent directory.
'go get' is no longer supported outside a module.
To build and install a command, use 'go install' with a version,
like 'go install example.com/cmd@latest'
For more information, see https://golang.org/doc/go-get-install-deprecation
or run 'go help get' or 'go help install'.
The text was updated successfully, but these errors were encountered:
Bug Description
Installation failure message under mage installation
What did you do?
What did you expect to happen?
I expected the install to work.
What actually happened?
mage doesn't install
Environment
Additional context
Erro message after go run bootstrap.go:
After second approach to instal via command go get -u -d github.com/magefile/mage:
The text was updated successfully, but these errors were encountered: