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

Git --depth failed installs #1046

nparley opened this issue Jan 25, 2016 · 2 comments

Git --depth failed installs #1046

nparley opened this issue Jan 25, 2016 · 2 comments


Copy link

@nparley nparley commented Jan 25, 2016

If a repo is cloned with git --depth e.g.

git clone --depth=50 /tmp/devtools/


> sha <- git2r::commits(r, n = 1)
> sha

is returning an empty list hence:

> r <- git2r::repository('.', discover = TRUE)
> sha <- git2r::commits(r, n = 1)[[1]]@sha
Error in git2r::commits(r, n = 1)[[1]] : subscript out of bounds

I have added this as an issue for git2r (ropensci/git2r#219) but maybe it is worth catching this and not failing an install on a metadata problem? E.g.:

> install()
** R
** inst
** tests
** preparing package for lazy loading
** help
*** installing help indices
** building package indices
** installing vignettes
** testing if installed package can be loaded
* DONE (devtools)
Error in git2r::commits(r, n = 1)[[1]] : subscript out of bounds
> traceback()
4: git_sha1(path = x$path)
3: remote_metadata.package(as.package(pkg))
2: remote_metadata(as.package(pkg))
1: install()
Copy link
Contributor Author

@nparley nparley commented Jan 26, 2016

Created #1048 to fix this problem

nparley added a commit to nparley/devtools that referenced this issue Feb 8, 2016
shallow git clones, i.e. git clones which make use of depth. (r-lib#1048, r-lib#1046, @nparley)
@hadley hadley closed this in #1048 Apr 11, 2016
Copy link

@lock lock bot commented Sep 18, 2018

This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue.

@lock lock bot locked and limited conversation to collaborators Sep 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant