-
-
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
Failing CRAN checks for recent submission (0.11.0) #511
Comments
We could probably have all vignettes only on our website, not on CRAN. |
Seems to me that this is a spurious error, and I didn't get any email from CRAN about this. I'd say let's wait to see if it's solved automatically or if I get some message before making vignettes less available? |
I think this can be closed? |
Yes, I'll reopen if I get some message from CRAN |
We could still continue with #513 and replace the magrittr pipe with the native pipe (which I personally would prefer). |
This is still present with the latest release: https://cloud.r-project.org/web/checks/check_results_datawizard.html |
Which latest release? datawizard didn't get an update since this issue was open |
I wonder why the CRAN issues aren't resolved yet. It's still the two failing checks due to the pipe. I'm still pro #513 :-) |
* Failing CRAN checks for recent submission (0.11.0) Fixes #511 * 4.1 * Add note
Should I resubmit? I doubt this is urgent since I didn't get any notice from CRAN, so I think we have time if you want to add more things before the next release |
Yes, I too think that this is not urgent. It's just a bit "annoying" that we have the CRAN failures across all our packages that depend on datawizard. And related to this, we don't have binaries for Mac OS X old-rel on CRAN - but... I don't care about OS X anyway, so I leave the decision up to you ;-) |
I didn't notice that this prevented the distribution of binaries for 0.11.0, that's annoying. I'll release 0.12.0 this week |
For old-rel: https://cran.r-project.org/web/checks/check_results_datawizard.html
Not sure, why.
The text was updated successfully, but these errors were encountered: