Last updated on 2022-04-24 03:52:55 CEST.
| Package | WARN | NOTE | OK |
|---|---|---|---|
| Deducer | 12 | ||
| DeducerText | 12 | ||
| ipc | 12 | ||
| lolog | 6 | 5 | 1 |
| OpenStreetMap | 12 | ||
| shinyrecap | 12 | ||
| wordcloud | 6 | 6 |
Current CRAN status: OK: 12
Current CRAN status: NOTE: 12
Version: 0.1-2
Check: DESCRIPTION meta-information
Result: NOTE
Malformed Description field: should contain one or more complete sentences.
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-ix86+x86_64
Version: 0.1-2
Check: R code for possible problems
Result: NOTE
.makeQuickWordcloud: no visible global function definition for 'J'
.makeQuickWordcloud: no visible global function definition for 'new'
.makeQuickWordcloud: no visible global function definition for '.jnull'
.makeTextPlot: no visible global function definition for 'J'
.makeTextPlot: no visible global function definition for 'new'
.makeTextPlot: no visible global function definition for '.jnull'
.onLoad: no visible global function definition for '.jpackage'
.onLoad: no visible global function definition for '.jnew'
.onLoad: no visible global function definition for 'J'
make.color.scale: no visible global function definition for 'rgb'
Undefined global functions or variables:
.jnew .jnull .jpackage J new rgb
Consider adding
importFrom("grDevices", "rgb")
importFrom("methods", "new")
to your NAMESPACE file (and ensure that your DESCRIPTION Imports field
contains 'methods').
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-ix86+x86_64
Current CRAN status: NOTE: 12
Version: 0.1.3
Check: LazyData
Result: NOTE
'LazyData' is specified without a 'data' directory
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-ix86+x86_64
Current CRAN status: WARN: 6, NOTE: 5, OK: 1
Version: 1.3
Flags: --no-vignettes
Check: whether package can be installed
Result: WARN
Found the following significant warnings:
/home/hornik/tmp/R.check/r-devel-gcc/Work/build/Packages/BH/include/boost/container/detail/copy_move_algo.hpp:184:19: warning: ‘void* memmove(void*, const void*, size_t)’ writing to an object of type ‘value_type’ {aka ‘struct boost::container::dtl::pair<int, int>’} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
/home/hornik/tmp/R.check/r-devel-gcc/Work/build/Packages/BH/include/boost/container/detail/copy_move_algo.hpp:199:19: warning: ‘void* memmove(void*, const void*, size_t)’ writing to an object of type ‘boost::movelib::detail::iterator_to_element_ptr<boost::container::dtl::pair<int, int>*>::element_type’ {aka ‘struct boost::container::dtl::pair<int, int>’} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
/home/hornik/tmp/R.check/r-devel-gcc/Work/build/Packages/BH/include/boost/container/detail/copy_move_algo.hpp:912:19: warning: ‘void* memmove(void*, const void*, size_t)’ writing to an object of type ‘boost::movelib::detail::iterator_to_element_ptr<boost::container::dtl::pair<int, int>*>::element_type’ {aka ‘struct boost::container::dtl::pair<int, int>’} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
Flavor: r-devel-linux-x86_64-debian-gcc
Version: 1.3
Flags: --no-vignettes
Check: installed package size
Result: NOTE
installed size is 17.3Mb
sub-directories of 1Mb or more:
libs 15.6Mb
Flavors: r-devel-linux-x86_64-fedora-clang, r-oldrel-windows-ix86+x86_64
Version: 1.3
Flags: --no-vignettes
Check: whether package can be installed
Result: WARN
Found the following significant warnings:
/data/gannet/ripley/R/test-dev/BH/include/boost/container/detail/copy_move_algo.hpp:184:19: warning: ‘void* memmove(void*, const void*, size_t)’ writing to an object of type ‘value_type’ {aka ‘struct boost::container::dtl::pair<int, int>’} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
/data/gannet/ripley/R/test-dev/BH/include/boost/container/detail/copy_move_algo.hpp:199:19: warning: ‘void* memmove(void*, const void*, size_t)’ writing to an object of type ‘boost::movelib::detail::iterator_to_element_ptr<boost::container::dtl::pair<int, int>*>::element_type’ {aka ‘struct boost::container::dtl::pair<int, int>’} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
/data/gannet/ripley/R/test-dev/BH/include/boost/container/detail/copy_move_algo.hpp:912:19: warning: ‘void* memmove(void*, const void*, size_t)’ writing to an object of type ‘boost::movelib::detail::iterator_to_element_ptr<boost::container::dtl::pair<int, int>*>::element_type’ {aka ‘struct boost::container::dtl::pair<int, int>’} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
Flavor: r-devel-linux-x86_64-fedora-gcc
Version: 1.3
Flags: --no-vignettes
Check: whether package can be installed
Result: WARN
Found the following significant warnings:
/home/hornik/tmp/R.check/r-patched-gcc/Work/build/Packages/BH/include/boost/container/detail/copy_move_algo.hpp:184:19: warning: ‘void* memmove(void*, const void*, size_t)’ writing to an object of type ‘value_type’ {aka ‘struct boost::container::dtl::pair<int, int>’} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
/home/hornik/tmp/R.check/r-patched-gcc/Work/build/Packages/BH/include/boost/container/detail/copy_move_algo.hpp:199:19: warning: ‘void* memmove(void*, const void*, size_t)’ writing to an object of type ‘boost::movelib::detail::iterator_to_element_ptr<boost::container::dtl::pair<int, int>*>::element_type’ {aka ‘struct boost::container::dtl::pair<int, int>’} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
/home/hornik/tmp/R.check/r-patched-gcc/Work/build/Packages/BH/include/boost/container/detail/copy_move_algo.hpp:912:19: warning: ‘void* memmove(void*, const void*, size_t)’ writing to an object of type ‘boost::movelib::detail::iterator_to_element_ptr<boost::container::dtl::pair<int, int>*>::element_type’ {aka ‘struct boost::container::dtl::pair<int, int>’} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
Flavor: r-patched-linux-x86_64
Version: 1.3
Flags: --no-vignettes
Check: whether package can be installed
Result: WARN
Found the following significant warnings:
/home/hornik/tmp/R.check/r-release-gcc/Work/build/Packages/BH/include/boost/container/detail/copy_move_algo.hpp:184:19: warning: ‘void* memmove(void*, const void*, size_t)’ writing to an object of type ‘value_type’ {aka ‘struct boost::container::dtl::pair<int, int>’} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
/home/hornik/tmp/R.check/r-release-gcc/Work/build/Packages/BH/include/boost/container/detail/copy_move_algo.hpp:199:19: warning: ‘void* memmove(void*, const void*, size_t)’ writing to an object of type ‘boost::movelib::detail::iterator_to_element_ptr<boost::container::dtl::pair<int, int>*>::element_type’ {aka ‘struct boost::container::dtl::pair<int, int>’} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
/home/hornik/tmp/R.check/r-release-gcc/Work/build/Packages/BH/include/boost/container/detail/copy_move_algo.hpp:912:19: warning: ‘void* memmove(void*, const void*, size_t)’ writing to an object of type ‘boost::movelib::detail::iterator_to_element_ptr<boost::container::dtl::pair<int, int>*>::element_type’ {aka ‘struct boost::container::dtl::pair<int, int>’} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
Flavor: r-release-linux-x86_64
Version: 1.3
Check: installed package size
Result: NOTE
installed size is 25.6Mb
sub-directories of 1Mb or more:
libs 24.0Mb
Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64
Version: 1.3
Flags: --no-vignettes
Check: whether package can be installed
Result: WARN
Found the following significant warnings:
D:/RCompile/CRANpkg/lib/4.2/BH/include/boost/container/detail/copy_move_algo.hpp:184:19: warning: 'void* memmove(void*, const void*, size_t)' writing to an object of type 'value_type' {aka 'struct boost::container::dtl::pair<int, int>'} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
D:/RCompile/CRANpkg/lib/4.2/BH/include/boost/container/detail/copy_move_algo.hpp:199:19: warning: 'void* memmove(void*, const void*, size_t)' writing to an object of type 'boost::movelib::detail::iterator_to_element_ptr<boost::container::dtl::pair<int, int>*>::element_type' {aka 'struct boost::container::dtl::pair<int, int>'} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
D:/RCompile/CRANpkg/lib/4.2/BH/include/boost/container/detail/copy_move_algo.hpp:912:19: warning: 'void* memmove(void*, const void*, size_t)' writing to an object of type 'boost::movelib::detail::iterator_to_element_ptr<boost::container::dtl::pair<int, int>*>::element_type' {aka 'struct boost::container::dtl::pair<int, int>'} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
Flavor: r-release-windows-x86_64
Version: 1.3
Flags: --no-vignettes
Check: whether package can be installed
Result: WARN
Found the following significant warnings:
d:/RCompile/CRANpkg/lib/4.1/BH/include/boost/container/detail/copy_move_algo.hpp:184:19: warning: 'void* memmove(void*, const void*, size_t)' writing to an object of type 'value_type' {aka 'struct boost::container::dtl::pair<int, int>'} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
d:/RCompile/CRANpkg/lib/4.1/BH/include/boost/container/detail/copy_move_algo.hpp:199:19: warning: 'void* memmove(void*, const void*, size_t)' writing to an object of type 'boost::movelib::detail::iterator_to_element_ptr<boost::container::dtl::pair<int, int>*>::element_type' {aka 'struct boost::container::dtl::pair<int, int>'} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
d:/RCompile/CRANpkg/lib/4.1/BH/include/boost/container/detail/copy_move_algo.hpp:912:19: warning: 'void* memmove(void*, const void*, size_t)' writing to an object of type 'boost::movelib::detail::iterator_to_element_ptr<boost::container::dtl::pair<int, int>*>::element_type' {aka 'struct boost::container::dtl::pair<int, int>'} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
Flavor: r-oldrel-windows-ix86+x86_64
Current CRAN status: OK: 12
Current CRAN status: NOTE: 12
Version: 0.1.0
Check: LazyData
Result: NOTE
'LazyData' is specified without a 'data' directory
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-ix86+x86_64
Version: 0.1.0
Check: dependencies in R code
Result: NOTE
Namespaces in Imports field not imported from:
‘CARE1’ ‘LCMCR’ ‘coda’ ‘conting’ ‘dga’ ‘future’ ‘ggplot2’ ‘ipc’
‘promises’ ‘reshape’ ‘shinycssloaders’ ‘testthat’
All declared Imports should be used.
Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64
Current CRAN status: NOTE: 6, OK: 6
Version: 2.6
Check: data for non-ASCII characters
Result: NOTE
Note: found 2 marked UTF-8 strings
Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64