Devtools: Dependence on R version '3.3.3' not with patchlevel 0

Created on 22 Mar 2018  路  3Comments  路  Source: r-lib/devtools

Hi,

I am using the development version of devtools and ran devtools::check(), which produced 0 errors, 0 warnings, and 0 notes for my package. So I submitted the package to CRAN, but their R CMD CHECK threw the following warning and the submission was rejected (full check.log provided below).

* checking DESCRIPTION meta-information ... WARNING
Dependence on R version '3.3.3' not with patchlevel 0

I was wondering if this is something devtools is supposed to catch and failed to or it's truly an error on my part?

* using log directory 'd:/RCompile/CRANincoming/R-devel/ggstatsplot.Rcheck'
* using R Under development (unstable) (2018-03-21 r74436)
* using platform: x86_64-w64-mingw32 (64-bit)
* using session charset: ISO8859-1
* checking for file 'ggstatsplot/DESCRIPTION' ... OK
* checking extension type ... Package
* this is package 'ggstatsplot' version '0.0.1'
* package encoding: UTF-8
* checking CRAN incoming feasibility ... NOTE
Maintainer: 'Indrajeet Patil <[email protected]>'

New submission

Possibly mis-spelled words in DESCRIPTION:
  ggplot (3:8, 10:28)
  ggstatsplot (10:38)
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... OK
* checking serialization versions ... OK
* checking whether package 'ggstatsplot' can be installed ... OK
* checking installed package size ... OK
* checking package directory ... OK
* checking DESCRIPTION meta-information ... WARNING
Dependence on R version '3.3.3' not with patchlevel 0
* checking top-level files ... OK
* checking for left-over files ... OK
* checking index information ... OK
* checking package subdirectories ... OK
* checking R files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* loading checks for arch 'i386'
** checking whether the package can be loaded ... OK
** checking whether the package can be loaded with stated dependencies ... OK
** checking whether the package can be unloaded cleanly ... OK
** checking whether the namespace can be loaded with stated dependencies ... OK
** checking whether the namespace can be unloaded cleanly ... OK
** checking loading without being on the library search path ... OK
** checking use of S3 registration ... OK
* loading checks for arch 'x64'
** checking whether the package can be loaded ... OK
** checking whether the package can be loaded with stated dependencies ... OK
** checking whether the package can be unloaded cleanly ... OK
** checking whether the namespace can be loaded with stated dependencies ... OK
** checking whether the namespace can be unloaded cleanly ... OK
** checking loading without being on the library search path ... OK
** checking use of S3 registration ... OK
* checking dependencies in R code ... OK
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... [26s] OK
* checking Rd files ... OK
* checking Rd metadata ... OK
* checking Rd line widths ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking examples ...
** running examples for arch 'i386' ... [17s] OK
** running examples for arch 'x64' ... [19s] OK
* checking PDF version of manual ... OK
* DONE
Status: 1 WARNING, 1 NOTE

Most helpful comment

The check you cite was recently added to R-devel, which is why you did not see it when running devtools::check() locally. This is also why it is recommended to check your package in R-devel before submission, using devtools::check_win_devel() or devtools::check_rhub(), both of which will check your package against the latest R-devel.

To get your package to pass the check you need to change the Depends: R (>= 3.3.3) to either Depends: R (>= 3.3) or Depends: R (>= 3.3.0).

All 3 comments

The check you cite was recently added to R-devel, which is why you did not see it when running devtools::check() locally. This is also why it is recommended to check your package in R-devel before submission, using devtools::check_win_devel() or devtools::check_rhub(), both of which will check your package against the latest R-devel.

To get your package to pass the check you need to change the Depends: R (>= 3.3.3) to either Depends: R (>= 3.3) or Depends: R (>= 3.3.0).

Cool, thanks! Didn't know about devtools::check_win_devel() or devtools::check_rhub(). Will make it a habit to run these checks as well.

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/

Was this page helpful?
0 / 5 - 0 ratings