We submitted our package to CRAN and got a rejection because the windows side cited packages not in mainstream repositories. These are all tidyverse packages. Debian built fine and didn't have the same warnings.
Could this be because the windows build was done using R under development? If so - do we change something in how we do the submission?
Here are the warnings we encountered in the CRAN incoming feasibility check:
* using log directory 'd:/RCompile/CRANincoming/R-devel/Tplyr.Rcheck' * using R Under development (unstable) (2020-08-31 r79098) * using platform: x86_64-w64-mingw32 (64-bit) * using session charset: ISO8859-1 * checking for file 'Tplyr/DESCRIPTION' ... OK * this is package 'Tplyr' version '0.1.1' * package encoding: UTF-8 * checking CRAN incoming feasibility ... WARNING Maintainer: 'Mike Stackhouse <firstname.lastname@example.org>' New submission Strong dependencies not in mainstream repositories: rlang, magrittr, dplyr, purrr, stringr, tidyr, tidyselect, tibble, lifecycle, forcats Suggests or Enhances not in mainstream repositories: testthat, haven, knitr, rmarkdown, huxtable, tidyverse, readr, kableExtra, pharmaRTF Found the following (possibly) invalid URLs: URL: https://codecov.io/gh/atorus-research/tplyr From: README.md Status: Error Message: libcurl error code 35: schannel: next InitializeSecurityContext failed: SEC_E_ILLEGAL_MESSAGE (0x80090326) - This error usually occurs when a fatal SSL/TLS alert is received (e.g. handshake failed).