Dear List - What’s the latest best practice on trying to reproduce warnings raised on CRAN checks?
I updated my epanet2toolkit package earlier this week. R CMD check —as-cran was clean on RHUB and Winbuilder and my local machines. But on CRAN a few variations are causing warnings. For example R-devel-debian-gcc is ok on rhub https://builder.r-hub.io/status/epanet2toolkit_0.6.1.tar.gz-58c1ce1e316317307679f58450a5e17a But not on CRAN: https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-gcc/epanet2toolkit-00check.html Thanks in advance for any suggestions. Brad [[alternative HTML version deleted]] ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
