As far as I know these are all harmless.
* the first NOTE is for CRAN consumption
* the rest are false positives
<CRAN_peeving>
The spell-checking machinery used in package checking is
under-documented. There are some useful references here
https://github.com/r-lib/usethis/issues/1466
https://ropensci.org/blog/2022/01/21/ropensci-news-digest-january-2022/#to-quote-or-not-to-quote-non-existing-words-in-description
https://stat.ethz.ch/pipermail/r-package-devel/2016q3/000943.html
https://stat.ethz.ch/pipermail/r-package-devel/2017q3/001764.html
I've been meaning to submit a patch to "Writing R Extensions" that
would describe this, but so far I haven't. However, I also think that
win-builder does *not* pay attention to the .aspell/ stuff documented
above ...
</CRAN_peeving>
On 2024-06-12 2:12 p.m., Lucas Godoy wrote:
Hello everyone,
Recently, my R package {smile} was archived due to NOTES. At the time, I
was in the final stages of my PhD and unfortunately, I couldn't address the
issue in time to prevent the package from being archived.
Long story short, I fixed the issues, and now the `R CMD check --as-cran`
returns no notes (I'm on a Mac. However, when I submit the package to
"win-builder" to get it checked on Windows, I get the following NOTES:
"* checking CRAN incoming feasibility ... NOTE
Maintainer: 'Lucas da Cunha Godoy <lcgo...@duck.com>'
New submission
Package was archived on CRAN
Possibly misspelled words in DESCRIPTION:
ISSN (17:54)
Moraga (13:60)
al (14:9)
et (13:67)
CRAN repository db overrides:
X-CRAN-Comment: Archived on 2024-04-09 as issues were not corrected
in time."
The "misspelled" words are author names included in the DESCRIPTION file as
references. Also, there is a note that the package is being archived.
I used GitHub workflows to get the package checked on Linux as well (see
here
<https://github.com/lcgodoy/smile/actions/runs/9486462259/job/26140848384>),
and there I got a note about sub-directories with more than 1Mb. To this
point, I don't believe I can further shrink those directories.
Does anyone have any suggestions on how to fix those issues to get the
package on CRAN?
My session info is below, just in case.
R version 4.3.2 (2023-10-31)
Platform: aarch64-apple-darwin20 (64-bit)
Running under: macOS Sonoma 14.5
Matrix products: default
BLAS:
/Library/Frameworks/R.framework/Versions/4.3-arm64/Resources/lib/libRblas.0.dylib
LAPACK:
/Library/Frameworks/R.framework/Versions/4.3-arm64/Resources/lib/libRlapack.dylib;
LAPACK version 3.11.0
Thanks a lot,
Lucas.
[[alternative HTML version deleted]]
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
--
Dr. Benjamin Bolker
Professor, Mathematics & Statistics and Biology, McMaster University
Director, School of Computational Science and Engineering
(Acting) Graduate chair, Mathematics & Statistics
> E-mail is sent at my convenience; I don't expect replies outside of
working hours.
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel