How often should one update a package on CRAN? I noticed NOTEs in the CRAN checks that I have since solved.
However, I just discovered that the("my"(disclosure)) package now fails to install on one of the Linux flavors. How can I best know what is causing the error as the logs simply show:
installing to library ‘/home/hornik/tmp/R.check/r-devel-gcc/Work/build/Packages’
Error: ERROR: no permission to install to directory ‘/home/hornik/tmp/R.check/r-devel-gcc/Work/build/Packages’
Secondly, if I fix this problem, how long should I wait before submitting to CRAN? I was ideally thinking of taking a month or so as I read somewhere.
Thanks in advance.
CRAN checks for reference.
EDIT:: I discovered that there are some issues with dplyr as per its CRAN checks, could this be causing the problem?!
One of the most used guidelines for releasing R packages on CRAN says
Do not submit updates too frequently. The policy suggests a new
version once every 1-2 months at most.
Related
I have troubles with installing the package fwildclusterboot. It says that it is no longer available in CRAN. Also didn't succeed even when I exploited it from the archive. I was searching for some new version but could not find it.
Can you please help me how to do it?
I am the author of fwildclusterboot.
Due to issues with a broken dependency I did not manage to fix on time, fwildclusterboot is temporarily not available on CRAN. The long story is that a dependencies' dependency failed a test, then the dependency was not fixed, therefore archived on CRAN, and I did not manage to a) drop the dependency on time and pass all CRAN notes within the given two-three week time limit. Now I am trying to bring the package back, but CRAN is not very responsive towards me.
In the meantime, you can download the package from R universe (a CRAN alternative, set up by rOpensci) by running install.packages('fwildclusterboot', repos ='https://s3alfisc.r-universe.dev'). I hope the package will be back on CRAN soon!
I'm looking for an updated version of this:
https://cran.r-project.org/web/packages/lfe/index.html
package. It seems to have been removed from CRAN. How could I find out about the history of this process to maybe find out if it was migrated to a new package or just isn't maintained anymore?
The package was back on CRAN on 11 January 2021. It has been updated several times since.
The page you linked provides some information:
Package ‘lfe’ was removed from the CRAN repository.
Formerly available versions can be obtained from the archive.
Archived on 2020-12-04 as check problems were not corrected in time.
My conclusions:
as of today (11 Dec 2020), it was removed only a week ago (Dec 4)
it appears to have been archived by CRAN maintainers, not withdrawn by package authors/maintainers.
if we go to the page and retrieve the most recent version (2.8-5.1, 2020-07-08) and open the DESCRIPTION file in the archive, we can find the URL for the package on github: https://github.com/sgaure/lfe (we could also get there by googling "lfe package github"). You can also go to the issues list on that repo to find this discussion. It's long, but it looks like the maintainers are hard at work trying to get the package back on CRAN.
Not all packages have their source code/issue-tracking lists on a public site, bot those that do will generally have it listed in the URL: field of the DESCRIPTION file.
You can probably install the latest archived version via remotes::install_version("lfe", version="2.8-5.1") (you might need development tools [compilers etc.] installed)
As Ben noted, the package has been resubmitted (I am one of the contributors) and should hopefully be back on CRAN soon.
But, FWIW and in the interim, I've created a simple package that takes existing lfe::felm scripts and converts them to the fixest::feols equivalent. I expect most people will move to the latter over time anyway, given its advantages. https://github.com/grantmcdermott/lfe2fixest
I submitted a package to CRAN recently, which was a great achievement for me.
Within 48 hours, I found that the Windows binary didn't build correctly due to a mistake on my part. Using rhub, I corrected this and would like the corrected version on CRAN.
I've been reading through the policies:
https://cran.r-project.org/web/packages/policies.html
I upped the version of the package, and re-submitted last month. However, I never heard back from the CRAN volunteers.
What is the procedure for correcting a package with binary build failures? Am I misunderstanding how to correct the package with CRAN?
Any help appreciated
I was building a package that I wanted to submit to CRAN. I completed R CMD checks (using devtools::check()) and ensured that I fix all errors, warnings and notes before I build my package (devtools::build) and then submit the resulting tar.gz file to CRAN.
However, apparently, the package failed the R CMD checks at CRAN (There was one note and one error, as per their mail).
Now my question was, why wasn't this picked up when I ran the checks at my end?
To provide some specifics - One of the notes was regarding the usage of a few functions from stats package. I hadn't specifically imported these functions in my namespace.
While this seems to be an easy enough fix, it's mildly irritating (I would have ideally expected to find this while I was running my checks)
How can I avoid such situations in the future?
Thanks!
I would like to submit a package (DLMtool) to the CRAN repository. When I check the package with R CMD check --as-cran I receive only 1 note regarding the new submission.
However when I submit the package I am receiving feedback from the R core team regarding errors that I do not receive. For example:
Quitting from lines 261-262 (DLMtool.Rnw)
Error: processing vignette 'DLMtool.Rnw' failed with diagnostics:
one node produced an error: NAs are not allowed in subscripted assignments
I cannot recreate this error by running the code myself. But that isn't the point of this post: I'm not worried about specific errors, rather my inability to detect these myself. To this point Prof. Ripley has been very patient. I desperately don't want to waste any more of his time or any of the R core team by using them as a step-by-step checking process.
How can I recreate the CRAN package check process if --as-cran is insufficient?
A similar question has been asked regarding a previous version of R that was not answered satisfactorily as far as I can tell:
CRAN package check finds warning that R CMD check --as-cran doesn't
Cheers,
Tom
I'm using Windows 7 x64, RStudio 0.98.507 and R 3.1.1 x64.
Submitting a package to CRAN still fills me a with a sense of uneasiness, despite having been successful on a number of occasions.
Some things to check:
Ensure you are using the correct process
Specifically, use:
R CMD build pkg
R CMD check pkg_version.tar.gz
Make sure you check using the current version of R, as well as the development branch, R-devel (http://cran.r-project.org/bin/windows/base/rdevel.html)
Submit your package to the windows builder (http://win-builder.r-project.org/)
Make sure you have read, and completely understood, every single sentence of the CRAN submission policy (http://cran.r-project.org/web/packages/policies.html)
Submit your package using the online submission form (http://cran.r-project.org/submit.html)
Then hope for the best.
To be honest, every individual I have dealt with on the CRAN build team have been very patient and helpful.