Hi, Regarding Solaris, while the criteria is unknown, it seems Solaris can be excluded from the CRAN check targets when there's a good reason not to support Solaris. My package got a failure on Solaris check and I resubmitted with the following comment, then Solaris disappeared from the check results [1].
> I would like to request to exclude Solaris from the build targets because > Solaris is not a supported platform by Rust. This should be in line with the > treatments of other CRAN packages that use Rust; gifski, baseflow, and salso > are not built on Solaris. I'm sorry that I didn't write this in the first > submission. Again, I'm not sure on what criteria they decided to accept my suggestion. It's unclear if your package is the case. Some months ago, I asked "How can I avoid Solaris build on CRAN?" on this mailing list [2], but I got no reply. So, probably no one knows the right answer... Best, Hiroaki Yutani [1]: https://cran.r-project.org/web/checks/check_results_string2path.html [2]: https://stat.ethz.ch/pipermail/r-package-devel/2021q3/007262.html 2021年9月24日(金) 23:50 Roy Mendelssohn - NOAA Federal via R-package-devel <r-package-devel@r-project.org>: > > Hi All: > > I am getting dinged again on CRAN (just Solaris for some reason), and the > problem is how to exit if there is a failure of accessing the resource, I > know it has been discussed here before, but I just am not understanding what > is desired to end properly. As I have been reminded: > > 'Packages which use Internet resources should fail gracefully with an > informative message > if the resource is not available or has changed (and not give a check warning > nor error).' > > All internet calls are wrapped in 'try()'. If that shows an error, I write > a message to the screen about the error, and call stop(), perhaps with a > further message in that call. Somehow this does not appear to meet the > standard. Can someone then please tell me what I should do instead. The > point is I have checked that the access to the internet resources has worked, > i have seen that it hasn't, now what should be the steps to take to exit > gracefully. > > I also want to add to what others have said about the frustrations of dealing > with Solaris. I have spent a fair amount of time getting things to work > with Solaris which no one uses. In this instance the package test is only > failing on Solaris. Not a good use of limited time IMO. > > Thanks for any advice. > > -Roy > > > > ********************** > "The contents of this message do not reflect any position of the U.S. > Government or NOAA." > ********************** > Roy Mendelssohn > Supervisory Operations Research Analyst > NOAA/NMFS > Environmental Research Division > Southwest Fisheries Science Center > ***Note new street address*** > 110 McAllister Way > Santa Cruz, CA 95060 > Phone: (831)-420-3666 > Fax: (831) 420-3980 > e-mail: roy.mendelss...@noaa.gov www: https://www.pfeg.noaa.gov/ > > "Old age and treachery will overcome youth and skill." > "From those who have been given much, much will be expected" > "the arc of the moral universe is long, but it bends toward justice" -MLK Jr. > > ______________________________________________ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel