Running R CMD check on a local package, I get
* checking Rd files ... OK
* checking Rd cross-references ... WARNING
Error in .find.package(package, lib.loc) :
there is no package called 'boot'
Execution halted
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
The output is spurious -- I do not use boot, but do have it installed.
This is with R-patched as of Nov 25 as well as Nov 03. Am I overlooking
something, or is this a buglet?
Regards, Dirk
Hell, there are no rules here - we're trying to accomplish something.
-- Thomas A. Edison
Running R CMD check on a local package, I get
* checking Rd files ... OK
* checking Rd cross-references ... WARNING
Error in .find.package(package, lib.loc) :
there is no package called 'boot'
Probably the boot installation in one of your libraries is corrupted.
Uwe
Execution halted
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
The output is spurious -- I do not use boot, but do have it installed.
This is with R-patched as of Nov 25 as well as Nov 03. Am I overlooking
something, or is this a buglet?
Regards, Dirk
Running R CMD check on a local package, I get
* checking Rd files ... OK
* checking Rd cross-references ... WARNING
Error in .find.package(package, lib.loc) :
there is no package called 'boot'
Probably the boot installation in one of your libraries is corrupted.
Actually, the question is where boot is installed. The code does
aliases <-
lapply(unlist(.get_standard_package_names()[c("base",
"recommended")],
use.names = FALSE),
Rd_aliases, lib.loc = .Library)
********
-k
Uwe
Execution halted
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
The output is spurious -- I do not use boot, but do have it installed.
This is with R-patched as of Nov 25 as well as Nov 03. Am I overlooking
something, or is this a buglet?
Regards, Dirk
| >> Running R CMD check on a local package, I get
| >>
| >> * checking Rd files ... OK
| >> * checking Rd cross-references ... WARNING
| >> Error in .find.package(package, lib.loc) :
| >> there is no package called 'boot'
|
| > Probably the boot installation in one of your libraries is corrupted.
|
| Actually, the question is where boot is installed. The code does
|
| aliases <-
| lapply(unlist(.get_standard_package_names()[c("base",
| "recommended")],
| use.names = FALSE),
| Rd_aliases, lib.loc = .Library)
| ********
LL <- library()
Warning message:
library %G,Ab??(B%@/usr/lib/R/site-library%G,Ab??(B%@ contains no packages in: library()
The boot package loads fine, and is current. Why does R CMD check think it
is an error that boot happens to live in a particular directory, for as long
as that directory is known to .libPaths() ?
Dirk
Hell, there are no rules here - we're trying to accomplish something.
-- Thomas A. Edison