-
Notifications
You must be signed in to change notification settings - Fork 6
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
Action needed before 2023-01-25: update refsplitr's dependencies as it cannot be built #90
Comments
I was made aware of planned updates in a separate conversation πΈ |
@embruna I see all builds are failing on https://ropensci.r-universe.dev/builds, any update, any help needed? cc @ropensci/admin |
Hi, I have just started my sabbatical, and Item #2 on the list is to deal with the issues with dependencies etc for refsplitr - with some luck I will start on this coming Monday. I'll be sure to ask for help if - errr, when - I need it! |
Awesome! I'll be off for the next three weeks. https://devguide.ropensci.org/maintenance_cheatsheet.html |
I removed the line of code related to maptools, the builds are no long failing. The R-CMD-check is still failing, but this appears to be due to a few warnings (1 deprecated command, one non-ASCII character). |
UPDATE: all cmd-checks are now passing and addressed issue of non-ascii character. |
π π |
π @embruna!
Your refsplitr package cannot be built on R-universe as it depends on the deprecated spatial package maptools. See for instance this write up by Jakub Nowosad to understand the changes in the R spatial ecosystem. πΊοΈ
Please indicate us before January, the 25th whether you intend to update your package. If not, we will archive refsplitr* and remove it from rOpenSci registry. You do not need to make changes before January, the 25th; but you do need to drop us a line before then.
You can find help, among other places, in our Slack's workspace "spatial" and "package-maintenance" channels.
Thank you! π
*: We can unarchive the repository and transfer it to your own account, at your request. We won't shred it. πΈ
@ropensci/admin
The text was updated successfully, but these errors were encountered: