On 22 February 2024 at 04:01, Duncan Murdoch wrote:
| For you to deal with this, you should make arrow into a suggested
| package,
For what it is worth, that is exactly what package tiledb does.
Yet the Suggests: still lead to a NOTE requiring a human to override which
did not happen until I
FWIW the arrow maintainers are aware of this and we submitted a fix to CRAN
a couple of weeks ago, which is currently in the review queue at
https://cran.r-project.org/incoming/pending/
Nic
On Thu, 22 Feb 2024 at 09:22, Park, Sung Jae wrote:
> Thank you so much for all of you! I haven’t
Thank you so much for all of you! I haven’t thought that ‘arrow’ package itself
will have an error.
Since ‘arrow’ package isn’t a crucial component of our package, I made ‘arrow’
package into ‘Suggests’ and update cran-comment.md accordingly.
I appreciate your advice once again.
Best,
--Sungjae
Depending on your use case you can also take a look at the nanoarrow
package (https://cran.r-project.org/package=nanoarrow). Maybe it
provides all the features you need and has a much smaller footprint than
'arrow'.
Best,
Denes
On 2/22/24 10:01, Duncan Murdoch wrote:
If you look on the CRAN
This error indicates that the arrow package is unavailable on the system
where your package is checked. At
https://cran.r-project.org/web/checks/check_results_arrow.html you can
see that the arrow package is currently not working with clang on fedora
an debian. This is not something that you
If you look on the CRAN check results for arrow, you'll see it has
errors on the Linux platforms that use clang, and can't be installed there.
For you to deal with this, you should make arrow into a suggested
package, and if it is missing, work around that without generating an
error.
Hi,
I’m writing to seek assistance regarding an issue we’re encountering during the
submission process of our new package to CRAN.
The package in question is currently working smoothly on R CMD check on
Windows; however, we are facing a specific error when running R CMD check on
Debian. The
