http:// vs https:// in hardcoded repositories #1059
Milestone
Comments
|
Want to do a PR? |
|
OK, although does it need to be/should it be conditional on R >= 3.3.0? (I thought there were other uses of hard-coded http://, but I think I was wrong) |
hadley
added a commit
that referenced
this issue
Jun 3, 2016
hadley
added a commit
that referenced
this issue
Jun 3, 2016
hadley
added a commit
that referenced
this issue
Jun 3, 2016
* Pick https mirror if possible. Fixes #1059 * Add NEWS bullet * Check for libcurl * Remove RStudio license block * Correct issue number * Merge conflict?
|
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/ |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There are a few places where the RStudio CRAN mirror (
cran.studio.com) is hard-coded, for convenience (e.g. functions that will get used non-interactively, where user may not have set repo in their .Rprofile). Right now these are hard-coded ashttp://..., which causes various difficulties when using R-devel (which insists onhttps://in many important contexts) - specifically, dependencies may fail to be found when installing packages. In particular, changinghttp://tohttps://in line 56 ofdeps.Rfixes a lot of problems ...The text was updated successfully, but these errors were encountered: