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
error message in first install #45
Comments
How did you install it? |
tried with:
and
with both ones the problem happens again and again :) |
o.k. that is strange as the first method is the recommended way and if this would be a common problem we would hear more about it here, I guess. So is there anything special about your system? Can you give a few more details? |
@ysolis would be great if you could nail down exactly with which change the problem was introduced. |
ok, previously I install pyenv in two laptops, with Archlinux and Ubuntu 14.04 LTS one and half year ago. Now this is a new laptop, With Ubuntu 16.04 LTS. I copy first .pyenv from a previous backup from $HOME from my older laptop and works well. I did must reinstall Ubuntu 16.04.1 LTS and I try the install, not deploy from my backup, and this present this problem. |
I just tested it in the vagrant image that is part of this project (based on 14.04 LTS) and all looks well. Will repeat it with 16.04 LTS next ...
|
Same with xenial:
|
'pyenv update' will give up pulling the latest revision if the local repo isn't on master branch. If you want to update pyenv and plugins by the command, you meed to checkout master branch on all your local repos. Anyway that's all implemented in https://github.com/yyuu/pyenv-update, not this project. |
ok, noted, resolved by me. Maybe this will be need to be an update in the documentation or for pyenv-update ? |
@ysolis i'm now getting this error too. How'd you resolve it? |
I was installing pyenv in a new laptop, and do a new install with pyenv-installer.
all was good, but I have an error message that didn't appear in previous installs.
you can view the error message
pyenv-update: /home/yonsy/.pyenv is not on master branch.
debugging this, i find that in
verify_repo_branch
function for base~/.pyenv
directory (the pyenv repo, not plugins),git name-rev --name-only HEAD
returnstags/v1.0.5
, notmaster
and this causes the problem.The text was updated successfully, but these errors were encountered: