Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / pyenv/pyenv-update issues and pull requests
#25 - "pyenv update" not fetching latest versions supplied by pyenv
Issue -
State: closed - Opened by nickeldan 10 months ago
- 4 comments
#24 - pyenv is not being updated
Issue -
State: closed - Opened by BeyondEvil about 1 year ago
- 2 comments
#23 - Add help text
Pull Request -
State: closed - Opened by toramanlis over 1 year ago
#22 - Fail to merge: "merge: origin - not something we can merge"
Issue -
State: closed - Opened by bkbncn almost 2 years ago
- 1 comment
#21 - "fatal: Could not read from remote repository" for git://github.com
Issue -
State: closed - Opened by hongyi-zhao almost 2 years ago
- 3 comments
#20 - This does not appear to work.
Issue -
State: closed - Opened by Stokestack about 2 years ago
- 4 comments
#19 - Don't use git pull --no-rebase/--ff so we work with old git
Pull Request -
State: closed - Opened by kroeschl over 2 years ago
- 2 comments
#18 - pyenv update fails - pyenv-update with connection timed out
Issue -
State: closed - Opened by fenchu over 2 years ago
- 1 comment
#17 - support to change the code source of pyenv and all its plugins
Issue -
State: closed - Opened by JohnHerry over 2 years ago
- 4 comments
#16 - fatal: could not create leading directories of '/plugins/pyenv-update': Read-only file system
Issue -
State: closed - Opened by ssbarnea about 3 years ago
- 1 comment
#15 - RFE: pyenv update should regenerate shims unconditionally
Issue -
State: closed - Opened by PAStheLoD almost 7 years ago
- 12 comments
#14 - `pyenv update` no longer works on CentOS 7
Issue -
State: closed - Opened by mdklatt about 3 years ago
- 1 comment
#13 - error: unknown option `no-rebase'
Issue -
State: closed - Opened by shimamizu over 3 years ago
- 4 comments
#12 - Feature request: provide a way for "pyenv update" to consider only (stable) releases
Issue -
State: open - Opened by bersbersbers over 3 years ago
- 4 comments
#11 - Feature request: prominent notification of breaking changes when updating
Issue -
State: open - Opened by jrial over 3 years ago
#10 - Add '--tags' to 'git pull' command to pull in tags for repos as well
Pull Request -
State: closed - Opened by minddrive over 3 years ago
- 8 comments
#9 - Also allow update on 'main' branch
Pull Request -
State: closed - Opened by alefpereira over 3 years ago
- 3 comments
#8 - Fix repo address in clone command
Pull Request -
State: closed - Opened by paw-lu almost 5 years ago
- 4 comments
#7 - Update install snippet to use pyenv root
Pull Request -
State: closed - Opened by cewood about 6 years ago
#6 - older git versions support when verifying branch name
Pull Request -
State: closed - Opened by guyarad over 6 years ago
- 2 comments
#5 - Add placeholder for tests on travis-ci.org
Pull Request -
State: closed - Opened by yyuu over 6 years ago
#4 - Only use actual branch names when verifying branch
Pull Request -
State: closed - Opened by wjv over 6 years ago
- 5 comments
#3 - Update README.md
Pull Request -
State: closed - Opened by jimmywan over 7 years ago
- 1 comment
#2 - Ensure update is a fast-forward merge
Pull Request -
State: closed - Opened by jawshooah over 9 years ago
- 1 comment
#1 - Update git status to use porcelain
Pull Request -
State: closed - Opened by jimmywan over 9 years ago
- 2 comments