CRAN Package Check Results for Maintainer ‘Danielle Navarro <djnavarro at protonmail.com>’

Last updated on 2025-07-13 09:50:08 CEST.

Package FAIL NOTE OK
bs4cards 13
flametree 1 12
lsr 2 11
quartose 8

Package bs4cards

Current CRAN status: OK: 13

Package flametree

Current CRAN status: FAIL: 1, OK: 12

Version: 0.1.3
Check: PDF version of manual
Result: FAIL Check process probably crashed or hung up for 20 minutes ... killed Most likely this happened in the example checks (?), if not, ignore the following last lines of example output: > > # returns a function that always produces > # a vector of zeros > spark_nothing() function (coord_x, coord_y, id_tree, id_time) { n <- length(coord_x) return(rep(0, n)) } <bytecode: 0x00000213538309d0> <environment: 0x000002135641fd80> > > > > > ### * <FOOTER> > ### > cleanEx() > options(digits = 7L) > base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n") Time elapsed: 4.88 0.43 5.31 NA NA > grDevices::dev.off() null device 1 > ### > ### Local variables: *** > ### mode: outline-minor *** > ### outline-regexp: "\\(> \\)?### [*]+" *** > ### End: *** > quit('no') ======== End of example output (where/before crash/hang up occured ?) ======== Flavor: r-release-windows-x86_64

Package lsr

Current CRAN status: NOTE: 2, OK: 11

Version: 0.5.2
Check: CRAN incoming feasibility
Result: NOTE Maintainer: ‘Danielle Navarro <djnavarro@protonmail.com>’ Package CITATION file contains call(s) to old-style citEntry(). Please use bibentry() instead. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc

Package quartose

Current CRAN status: OK: 8