"Cyclic dependency check skipped" in release()

[krlmlr]

When I call devtools::release(), at some point during the check process the following message appears:

Package has help file(s) containing install/render-stage \Sexpr{} expresssons but no prebuilt PDF manual.
* checking package namespace information ... OK
* checking package dependencies ... NOTE
  No repository set, so cyclic dependency check skipped
* checking if this is a source package ... OK
* checking if there is a namespace ... OK

I'm not sure if the NOTE about package dependencies is related to the note about the \Sexpr-s. With check(cran = TRUE) these notes are not shown.

[hadley]

We could resolve this by setting a CRAN options somewhere, but I'm not sure where given that we're running with --vanilla. Is there an env var?

[krlmlr]

I have to take a closer look. This might be related to #603.

[hadley]

I don't think it's related.

[krlmlr]

The note also occurs with devtools::check(check_version = TRUE). It is related to an unset repos option.

From the description of R startup, I guess we'll have to:

• fabricate a one-line .Rprofile
• set the R_PROFILE_USER environment variable to that file
• use --no-site-file --no-environ instead of --vanilla

How about adding a new argument with_repos = FALSE to the internal R function?

[hadley]

How does this work on travis? You can set a CRAN env var there.

[hadley]

Related to #678

[krlmlr]

We seem to need all of the three above -- our own .Rprofile, setting the env var and changing command-line arguments. The .Rprofile would look like this:

options(repos=c(CRAN="http://cran.rstudio.com"))

[hadley]

Seems like we should modify R() and RCMD() to do that?

It might be possible to just do it via env vars, by setting R_ENVIRON, R_ENVIRON_USER, R_PROFILE, R_PROFILE_USER etc. I think it requires a close reading of ?Startup to figure out what the best process is.

Maybe we can drop --vanilla in favour of ignoring user files, and overriding the location of R_PROFILE to something we create?

[lock]

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/