Exactly what errors do you think you found? It is not an error for a package to be compatible with a range of versions of R.
On September 6, 2021 4:02:08 AM PDT, Colin Gillespie <csgilles...@gmail.com> wrote: >Dear All, > >Sorry if this is the wrong mailing address. > >I was doing a little investigation of R versions in packages and >discovered a number of errors: > >https://cran.r-project.org/web/packages/bartCause/index.html - R (≥ 3.1-0) >https://cran.r-project.org/web/packages/activityGCMM/index.html - R (3.00) >https://cran.r-project.org/web/packages/deTestSet/index.html - R (≥ 2.01) > >and also > >https://cran.r-project.org/web/packages/NGSSEML/ - R (≥ 1.9.0), R (≥ >3.5.0), R (≥ 3.5.0), R (≥ 3.5.0), R (≥ 3.5.0), R (≥ 3.5.0), R (≥ >3.5.0) > >Overall I detected ~40 packages with issues: > >c("activityGCMM", "behavr", "bioassays", "bvpSolve", "celestial", >"chest", "CRTSize", "csppData", "damr", "deTestSet", "diagram", >"directPA", "DiscreteFDR", "ecolMod", "ecp", "epibasix", "europepmc", >"fabisearch", "FDX", "ggetho", "hyper.fit", "MedSurvey", "NBPSeq", >"NetIndices", "NFWdist", "OmegaG", "primer", "RATest", "refund", >"RmarineHeatWaves", "rmcfs", "rootSolve", "RPPASPACE", "scopr", >"scoringRules", "seqDesign", "shape", "sleepr", "SMPracticals", >"text", "tggd", "zeitgebr") > >It seems like this would be a useful check to implement on the R CMD check. > >Thanks > >Colin > > >Dr Colin Gillespie >https://twitter.com/csgillespie > >______________________________________________ >R-package-devel@r-project.org mailing list >https://stat.ethz.ch/mailman/listinfo/r-package-devel -- Sent from my phone. Please excuse my brevity. ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
