Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add issues from CRAN on packages with deadlines #19

Open
45 tasks
llrs opened this issue Sep 13, 2024 · 0 comments
Open
45 tasks

Add issues from CRAN on packages with deadlines #19

llrs opened this issue Sep 13, 2024 · 0 comments

Comments

@llrs
Copy link
Member

llrs commented Sep 13, 2024

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 🤷 ).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant