r-lib / revdepcheck

R package reverse dependency checking
https://revdepcheck.r-lib.org
Other
99 stars 31 forks source link

cran.md reporting 0 packages from CRAN #342

Open eliocamp opened 1 year ago

eliocamp commented 1 year ago

I'm running revdepcheck and after seemingly checking all packages correctly, the file cran.md states:

## revdepcheck results

We checked 36 reverse dependencies (0 from CRAN + 36 from Bioconductor), comparing R CMD check results across CRAN and dev versions of this package.

 * We saw 0 new problems
 * We failed to check 0 packages

However I'm pretty certain that most if not all the packages I checked are on CRAN. The package is ggnewscale.

For example, one of the reverse dependencies is cmcR, which is on CRAN and not in Bioconductor.

gaborcsardi commented 1 year ago

I think you are using RSPM, and repdevcheck does not know that that is CRAN. It could try to guess it. What's the output of

getOption("repos")
eliocamp commented 1 year ago

Yes, I'm using RSPM: "https://packagemanager.rstudio.com/all/__linux__/focal/latest"

gaborcsardi commented 1 year ago

Can you please run

getOption("repos")

and show the complete output? Details might matter. Thanks!

eliocamp commented 1 year ago

Yep, no problem.

> getOption("repos")
                                                           RSPM 
"https://packagemanager.rstudio.com/all/__linux__/focal/latest
gaborcsardi commented 1 year ago

Yeah, so if you name that repo CRAN instead of RSPM, then revdepcheck will probably know that they are CRAN packages. (I haven't tested, though.)

eliocamp commented 1 year ago

I've just renamed the repo and ran it again. I still get the same message.

gavinsimpson commented 5 months ago

I'm also using RSPM. I see the same behaviour if the revdep check process times out as per #355; solution there is to make timeout a very large number (it's in seconds). Increasing the timeout allows the revdep checks to complete, but do note the second comment in #355 as this timeout applies to the entire revdep checking process (at the time of writing) and if your package's reverse dependencies themselves have a lot of dependencies, just installing those dependencies can take a very long time indeed