[R-pkg-devel] Package in 'sugests' archived

[Ben Bolker]

  I would ask the CRAN maintainers (cran using r-project.org).  I would guess
they will want a new submission.  The full text of the repository policy is

> Submitting updates should be done responsibly and with respect for the
volunteers’ time. Once a package is established (which may take several
rounds), “no more than every 1–2 months” seems appropriate.

  which IMO clearly leaves wiggle room for this kind of special situation.

  General advice for that the future is that you should make sure that
all package machinery that uses Suggested package should run
*conditionally* ("if requireNamespace(prospectr) { ... }") so that it
will work correctly even if the package is missing/unavailable: see
https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Suggested-packages

  Ben Bolker

On 2020-03-09 5:43 a.m., Fabio Corradini Santander wrote:
> Hi,
> I recently submitted my frist package to CRAN (
> https://CRAN.R-project.org/package=uFTIR). It was accepted last friday. I
> was super happy about it. However, today I check the results and there are
> several error flags in the package status. What happened?
> 
> I included a package called prospectr within the suggested packages. I only
> use it to run two examples. The idea was to show potential users that they
> can pass functions from other packages in one of the processing steps.
> 
> I did not notice that the package was old. It was updated in 2014 for the
> last time. Funny enough, the prospectr package was archived on saturday.
> Yes, one day after my package was accepted. (
> https://CRAN.R-project.org/package=prospectr)
> 
> Now I have to deal with the errors. As I mentioned, fixing the problems
> should be easy as I only included the package in two examples. My question
> is, then, what should I do? Should I fix the problem and submit a new
> 'version' to CRAN right away or should I wait? I read in the repository
> policy that one should wait between versions at least '1–2 months'.
>