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
CRAN complain for non-standard things in the check directory ... NOTE #6
Comments
As far as I can see this is a problem with rhub/cran, not the package itself... They might just ignore it on a submission. |
Is this when you check locally, or with winbuilder? If you get such a message on incoming, you will nearly certainly be asked to fix this. |
From my discussion with Oskar these files don't show up when building and checking locally on windows (with --as-cran) |
they still appear! I will reopen the issue until it's fixed |
Ok, when this doesn't show up when checked with https://win-builder.r-project.org/upload.aspx, it should be fine |
So, for me, the CRAN checks break already with the vignette, at
are you sure that this is running through? Regardless, to fix this, first thing I would do is to get the CI running (see #9), this will give you a good hint how things look on a clean system, and then we can take it from there. |
I will update the vignette. Never did CI, so happy to support you as you tell me. |
Vignette should be working now. I changed the output system but still had the old sgen3sis object on my package folder! Thanks for spotting this out. Should work now regarding the vignette. Let me know what I should do regarding the CI |
So, I don't get any of these non-standard files in my tests. Are you still getting this? |
I think this is something from your local computers - do you actually see these files? Have you tried just erasing them? |
I don't get this, but I'm on Ubuntu. Initially those files only showed up when checking with R-devel iirc... |
So, who exactly can reproduce this problem, and if someone can reproduce it, could you describe exactly the circumstances under which this occurs? If no one can reproduce it, I guess we should close this! |
Oskar, check again if #25 is solved, I expect that this will be gone |
#25 is fixed. Thanks! Can we close this? What do you get on mac when checking on -as --CRAN? |
In never got a problem. Will close, you can re-open if this is showing up in any of the tests |
The above happens when checking the package.
The text was updated successfully, but these errors were encountered: