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!
Related
I need to install R package fOpitons for a learning module required by society of actuaries. This package seems to be no longer available on CRAN. It was taken down in April 2022 for misrepresentation of authorship and ownership of copyright. None of the links to former versions of the package works. How can I install this package?
https://cran.r-project.org/web/packages/fOptions/index.html
None of the links in this site works.
https://cran-archive.r-project.org/web/checks/2022/2022-04-29_check_results_fOptions.html
(Note for eager "close as duplicate": the Archive/ link for this package is (currently?) broken which is very unusual for CRAN so I spelled out alternative approaches below. That part is likely not a duplicate. Cheers. -D.)
CRAN packages are open source, and even when removed from the current CRAN index for reasons deemed necessary by the CRAN team will always remain available in the Archive/ section of the package.
So the link you provide has as its second line
Formerly available versions can be obtained from the archive.
where the archive link should provide you access to various versions.
However, it is not working, which looks like an error. So I just alerted CRAN to that.
I happen to have maintained fOptions in Debian for a number of years. So you still get the Debian binary packages -- and sources. Most recent versions are at https://packages.debian.org/sid/r-cran-foptions point for example to the source archive: http://deb.debian.org/debian/pool/main/f/foptions/foptions_3042.86.orig.tar.gz
If you can install from source this should do.
Otherwise, there is also a CRAN mirror at GitHub so
https://github.com/cran/fOptions is another choice.
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
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.
I was about to send updated package to CRAN. Then I am asked to agree that I fixed following issues found in previous package (which was added to CRAN anyway).
But how to fix this? How to make package installable on r-oldrel-osx-x86_64
Google doesn't give any hints :-(