devtools::install_deps() needs remotes > 2.0.2

[bastistician]

The default upgrade argument of devtools::install_deps() and devtools::install_dev_deps()
https://github.com/r-lib/devtools/blob/55f982c6f7a9bef22c659954318a824381d9fdab/R/install.R#L113
has been changed in https://github.com/r-lib/devtools/commit/55f982c6f7a9bef22c659954318a824381d9fdab to accommodate the development version of remotes.

However, this changed also needs to increase the minimum required version of remotes in the DESCRIPTION of devtools to remotes > 2.0.2.

Using in-development devtools::install_deps() with released remotes 2.0.2 fails with

Error in match.arg(upgrade, c("ask", "always", "never")) : 
  'arg' must be of length 1

because at some point, remotes 2.0.2 calls

match.arg(upgrade, c("ask", "always", "never"))

[itcarroll]

I think this bug has now made it in to the released devtools 2.0.2 (#2014) and is causing the Travis r environment builds to fail.

Exhibit A.

[yihui]

I guess @jimhester must be busy with releasing a new version of remotes to CRAN now. Anyway, I have suggested a while back that we use remotes::install_deps instead of devtools::install_deps on Travis to install dependencies because devtools is too heavy due to the large number of dependencies that are actually not used by install_deps(). Even though all these dependencies are maintained by the same team, we can still fall into the dependency hell (like this case, which eventually blew up https://github.com/r-lib/devtools/issues/2020). Update: he has done it https://github.com/travis-ci/travis-build/pull/1682! Thanks, Jim!

[bastistician]

Sounds good! Thanks for linking the new bug report. My report from over two months ago unfortunately remained unnoticed until the recent CRAN release. A quick change in the devtools-devel DESCRIPTION to force remotes (> 2.0.2) would probably have prevented this "hell".

[itcarroll]

@bastistician Do you get why they closed this? I don't see any indication that the DESCRIPTION has been updated to reflect devtool's dependency on remotes >= 2.0.3.

[bastistician]

@itcarroll: I have no idea why this issue has been closed with no apparent fix. Time will tell. Maybe this has been fixed in some local devtools repository awaiting sync with the GitHub remote.

[lock[bot]]

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. https://reprex.tidyverse.org/