You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
R has tools::CRAN_check_details() which provides information about what is failing according to checks, it would be nice to show that to people checking the dashboard to see if the issue is complex or not (and see if the issue is across the packages or a single package).
For example current messages are:
C++ specification
compilation flags used
compiled code
data for ASCII and uncompressed saves
data for non-ASCII characters
dependencies in R code
DESCRIPTION meta-information
differences from ‘pkg-Ex.Rout’ to ‘pkg-Ex.Rout.save’
examples
files in ‘vignettes’
for code/documentation mismatches
for detritus in the temp directory
for GNU extensions in Makefiles
for missing documentation entries
for non-standard things in the check directory
for unstated dependencies in vignettes
foreign function calls
HTML version of manual
include directives in Makefiles
installed files from ‘inst/doc’
installed package size
LazyData
loading without being on the library search path
package dependencies
package subdirectories
package vignettes
PDF version of manual
PDF version of manual without index
R code for possible problems
Rd \usage sections
Rd contents
Rd cross-references
Rd files
re-building of vignette outputs
replacement functions
running R code from vignettes
Rust compilation
S3 generic/method consistency
startup messages can be suppressed
tests
top-level files
whether package can be installed
whether startup messages can be suppressed
whether the namespace can be loaded with stated dependencies
whether the namespace can be unloaded cleanly
Some of these are easier to fix than other and it could drive interested people to help the maintainer (or avoid the package 🤷 ).
The text was updated successfully, but these errors were encountered:
R has tools::CRAN_check_details() which provides information about what is failing according to checks, it would be nice to show that to people checking the dashboard to see if the issue is complex or not (and see if the issue is across the packages or a single package).
For example current messages are:
Some of these are easier to fix than other and it could drive interested people to help the maintainer (or avoid the package 🤷 ).
The text was updated successfully, but these errors were encountered: