Last updated on 2025-03-11 14:55:54 CET.
| Package | ERROR | NOTE | OK |
|---|---|---|---|
| BRugs | 3 | 6 | |
| fftw | 15 | ||
| klaR | 15 | ||
| nortest | 15 | ||
| R2WinBUGS | 10 | 5 | |
| scatterplot3d | 15 | ||
| signal | 2 | 13 | |
| tuneR | 15 |
Current CRAN status: ERROR: 3, NOTE: 6
Version: 0.9-2.1
Check: top-level files
Result: NOTE
possible bashism in configure.ac line 30 (test -a/-o):
if test [ `echo ${VERSION} |cut -d. -f1` -eq 3 -a `echo ${VERSION} |cut -d. -f2` -lt 2 ]; then
possible bashism in configure.ac line 33 (test -a/-o):
if test [ `echo ${VERSION} |cut -d. -f1` -eq 3 -a `echo ${VERSION} |cut -d. -f2` -eq 2 -a `echo ${VERSION} |cut -d. -f3` -lt 2 ]; then
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
Version: 0.9-2.1
Check: include directives in Makefiles
Result: NOTE
Found the following Makefile(s) with an include directive with a pathname using R_HOME:
src/Makefile.win
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives. However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME. This option can be specified
multiple times to include multiple Makefiles. Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.
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
Version: 0.9-2.1
Check: tests
Result: NOTE
Running ‘BRugs.R’ [3s/5s]
Comparing ‘BRugs.Rout’ to ‘BRugs.Rout.save’ ...65c65
< Welcome to BRugs connected to OpenBUGS version 3.2.2
---
> Welcome to BRugs connected to OpenBUGS version 3.2.3
Running ‘examples.R’ [20s/27s]
Comparing ‘examples.Rout’ to ‘examples.Rout.save’ ...55c55
< Welcome to BRugs connected to OpenBUGS version 3.2.2
---
> Welcome to BRugs connected to OpenBUGS version 3.2.3
106c106
< 20000 updates took 1 s
---
> 20000 updates took 2 s
205c205
< 20000 updates took 1 s
---
> 20000 updates took 3 s
218c218
< 20000 updates took 1 s
---
> 20000 updates took 2 s
258c258
< 20000 updates took 0 s
---
> 20000 updates took 1 s
Running ‘examples.stats.R’ [0s/0s]
Running ‘functions.R’ [9s/17s]
Comparing ‘functions.Rout’ to ‘functions.Rout.save’ ...138c138
< Welcome to BRugs connected to OpenBUGS version 3.2.2
---
> Welcome to BRugs connected to OpenBUGS version 3.2.3
Running ‘local.R’ [0s/0s]
Flavor: r-devel-linux-x86_64-debian-clang
Version: 0.9-2.1
Check: tests
Result: NOTE
Running ‘BRugs.R’ [3s/4s]
Comparing ‘BRugs.Rout’ to ‘BRugs.Rout.save’ ...65c65
< Welcome to BRugs connected to OpenBUGS version 3.2.2
---
> Welcome to BRugs connected to OpenBUGS version 3.2.3
Running ‘examples.R’ [18s/26s]
Comparing ‘examples.Rout’ to ‘examples.Rout.save’ ...55c55
< Welcome to BRugs connected to OpenBUGS version 3.2.2
---
> Welcome to BRugs connected to OpenBUGS version 3.2.3
106c106
< 20000 updates took 1 s
---
> 20000 updates took 2 s
205c205
< 20000 updates took 1 s
---
> 20000 updates took 3 s
218c218
< 20000 updates took 1 s
---
> 20000 updates took 2 s
Running ‘examples.stats.R’ [0s/1s]
Running ‘functions.R’ [8s/14s]
Comparing ‘functions.Rout’ to ‘functions.Rout.save’ ...138c138
< Welcome to BRugs connected to OpenBUGS version 3.2.2
---
> Welcome to BRugs connected to OpenBUGS version 3.2.3
Running ‘local.R’ [0s/0s]
Flavor: r-devel-linux-x86_64-debian-gcc
Version: 0.9-2.1
Check: tests
Result: NOTE
Running ‘BRugs.R’ [5s/11s]
Comparing ‘BRugs.Rout’ to ‘BRugs.Rout.save’ ... OK
Running ‘examples.R’ [32s/94s]
Comparing ‘examples.Rout’ to ‘examples.Rout.save’ ...165c165
< 20000 updates took 1 s
---
> 20000 updates took 0 s
218c218
< 20000 updates took 1 s
---
> 20000 updates took 2 s
Running ‘examples.stats.R’
Running ‘functions.R’ [15s/40s]
Comparing ‘functions.Rout’ to ‘functions.Rout.save’ ... OK
Running ‘local.R’
Flavor: r-devel-linux-x86_64-fedora-clang
Version: 0.9-2.1
Check: tests
Result: NOTE
Running ‘BRugs.R’
Comparing ‘BRugs.Rout’ to ‘BRugs.Rout.save’ ... OK
Running ‘examples.R’ [31s/41s]
Comparing ‘examples.Rout’ to ‘examples.Rout.save’ ...165c165
< 20000 updates took 1 s
---
> 20000 updates took 0 s
218c218
< 20000 updates took 1 s
---
> 20000 updates took 2 s
Running ‘examples.stats.R’
Running ‘functions.R’ [15s/23s]
Comparing ‘functions.Rout’ to ‘functions.Rout.save’ ... OK
Running ‘local.R’
Flavor: r-devel-linux-x86_64-fedora-gcc
Version: 0.9-2.1
Check: whether package can be installed
Result: ERROR
Installation failed.
Flavors: r-devel-windows-x86_64, r-release-windows-x86_64, r-oldrel-windows-x86_64
Current CRAN status: OK: 15
Current CRAN status: OK: 15
Current CRAN status: OK: 15
Current CRAN status: NOTE: 10, OK: 5
Version: 2.1-22.1
Check: R code for possible problems
Result: NOTE
Found the following calls to attach():
File ‘R2WinBUGS/R/attach.all.R’:
attach(x, name = name)
See section ‘Good practice’ in ‘?attach’.
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-patched-linux-x86_64, r-release-linux-x86_64
Version: 2.1-22.1
Check: package dependencies
Result: NOTE
Package suggested but not available for checking: ‘BRugs’
Flavors: 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-x86_64
Version: 2.1-22.1
Check: Rd cross-references
Result: NOTE
Package unavailable to check Rd xrefs: ‘BRugs’
Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64
Current CRAN status: OK: 15
Current CRAN status: NOTE: 2, OK: 13
Version: 1.8-1
Check: compiled code
Result: NOTE
File ‘signal/libs/signal.so’:
Found no calls to: ‘R_registerRoutines’, ‘R_useDynamicSymbols’
It is good practice to register native routines and to disable symbol
search.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc
Current CRAN status: OK: 15
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.