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

go-build: definition not found: 1.13.6 , when trying to install goenv install 1.13.6 #123

Closed
amanpatel6991 opened this issue May 13, 2020 · 8 comments

Comments

@amanpatel6991
Copy link

goenv install --list shows 1.12beta1 as the last go version available to install in goenv

How do i install go version >= 1.13.x in goenv ?

@carlows
Copy link

carlows commented May 18, 2020

+1

1 similar comment
@georgettica
Copy link

+1

@carlows
Copy link

carlows commented May 21, 2020

There are workarounds for this here if you used homebrew: #80

brew install jq
if [ -n "$(brew info --json goenv | jq -r '.[0].installed[] | select(.version | test("^HEAD-") | not)')" ]; then
  brew uninstall goenv
fi
brew install --HEAD goenv 

@joshua-rutherford
Copy link

Out of curiosity, why is this repository no longer maintaining tagged releases? While the above work around is not difficult, it is not generally how homebrew users upgrade thier packages.

If homebrew is not longer intended to be a supported delivery mechanism that is fine too but providing instructions on how to install using homebrew and not supporting any version of Go that has not stopped receiving security updates is a bit of a problem.

@georgettica
Copy link

Agreed, I guess there is no maintainer for that updates homebrew tap.
Anyways, is there a fix in goenv?

@yads
Copy link

yads commented Dec 3, 2020

For upgrading I've done

brew upgrade --fetch-HEAD goenv

@brightredchilli
Copy link

To hammer it home again, in case anyone runs into it...you need to do the --fetch-HEAD if you had already previously done the brew install --HEAD goenv, otherwise brew will use a local copy...thanks @yads

@aconstanti
Copy link

I ran into this today. It was very unexpected that this would be a problem.

Can someone ether fix this or change the readme page, to make it super clear that the installation is not default?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants