-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Vulnerability to absence of retiring r-spatial packages #70
Comments
Please also see https://r-spatial.org/r/2023/04/10/evolution3.html, fix best by June, latest October 2023. |
Please fix urgently: test with maptools 1.1-7 at https://r-forge.r-project.org/R/?group_id=943 is being submitted, and your package refers to
|
With CRAN With CRAN Wait until |
|
Thanks for the updates! I'm working on the changes now, I'll have the update released shortly (also received a warning from CRAN). |
|
00check.log
is a recent check log from running under
_SP_EVOLUTION_STATUS_=2
without retiring r-spatial packages (suggested in this package) on the library path. The minimal correction is to check that the package namespaces can be loaded, and if not, do not run those parts of the examples. It would be safer in the longer term to replace retiring r-spatial packages with active r-spatial/rspatial packages (see https://r-spatial.org/r/2022/04/12/evolution.html, https://r-spatial.org/r/2022/12/14/evolution2.html).The text was updated successfully, but these errors were encountered: