-
Notifications
You must be signed in to change notification settings - Fork 83
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
deployments using older versions of foreign package produce spurious warnings #436
Comments
Does #432 address this? |
Yes, I believe so! |
Fixed by #432 |
@jmcphers and/or @kevinushey I'm trying to reproduce this in the current CRAN version of |
This is specifically for any R package for which the latest-available source package requires R (>= 4.0.0); XML is another example: https://cran.r-project.org/web/packages/XML/index.html |
@kevinushey Thanks! I'll try out these packages with R 3.6.3 first. |
Verified by using [All thanks to @kevinushey for walking me through the reprex, etc.] |
When rsconnect checks to see whether a package is available on CRAN, it does so by checking whether the latest-available version of that package is available on CRAN:
rsconnect/R/dependencies.R
Line 83 in 40c162b
However, the default filters (which define an inclusion / exclusion criteria for the packages returned by
available.packages()
) are left on. From?available.packages
:The current source version of
foreign
requires R 4.0.0:which implies that the aforementioned check would fail to see that
foreign
is a package available on CRAN, if the current version of R were older than 4.0.0.Since this is ultimately just a warning, we could relax this check by removing the filters used by
available.packages()
.The text was updated successfully, but these errors were encountered: