R Development Page

rseg log file (check_x86_64_linux)

Fri Aug 24 16:12:06 2018: Checking package rseg (SVN revision 26) ...
* using log directory ‘/srv/rf/building/build_2018-08-24-17-08/RF_PKG_CHECK/PKGS/rseg.Rcheck’
* using R version 3.5.1 Patched (2018-08-22 r75177)
* using platform: x86_64-pc-linux-gnu (64-bit)
* using session charset: UTF-8
* using option ‘--as-cran’
* checking for file ‘rseg/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘rseg’ version ‘0.2.2’
* checking CRAN incoming feasibility ... NOTE
Maintainer: ‘Alexander Hapfelmeier ’

New submission

The Title field should be in title case, current version then in title case:
‘recursive segmentation (rseg)’
‘Recursive Segmentation (Rseg)’
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for executable files ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... OK
* checking for sufficient/correct file permissions ... OK
* checking serialization versions ... OK
* checking whether package ‘rseg’ can be installed ... [4s/4s] OK
* checking installed package size ... OK
* checking package directory ... OK
* checking DESCRIPTION meta-information ... OK
* checking top-level files ... OK
* checking for left-over files ... OK
* checking index information ... OK
* checking package subdirectories ... OK
* checking R files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... OK
* checking whether the package can be loaded with stated dependencies ... OK
* checking whether the package can be unloaded cleanly ... OK
* checking whether the namespace can be loaded with stated dependencies ... OK
* checking whether the namespace can be unloaded cleanly ... OK
* checking loading without being on the library search path ... OK
* checking use of S3 registration ... OK
* checking dependencies in R code ... NOTE
Unexported object imported by a ':::' call: ‘partykit:::.list.rules.party’
  See the note in ?`:::` about the use of this operator.
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... [8s/8s] NOTE
Found the following assignments to the global environment:
File ‘rseg/R/rseg.R’:
  assign("rSegdat", rSegdat, .GlobalEnv)
  assign("rSegdat", rSegdat, .GlobalEnv)
* checking Rd files ... OK
* checking Rd metadata ... OK
* checking Rd line widths ... OK
* checking Rd cross-references ... WARNING
Missing link or links in documentation object 'aic.Rd':
  ‘cseg’ ‘eseg’ ‘rseg’

Missing link or links in documentation object 'gettree.Rd':
  ‘cseg’ ‘eseg’ ‘rseg’

Missing link or links in documentation object 'plot.rseg.Rd':
  ‘cseg’ ‘eseg’ ‘rseg’

Missing link or links in documentation object 'predict.rseg.Rd':
  ‘cseg’ ‘eseg’ ‘rseg’

Missing link or links in documentation object 'print.rseg.Rd':
  ‘cseg’ ‘eseg’ ‘rseg’

Missing link or links in documentation object 'summary.rseg.Rd':
  ‘cseg’ ‘eseg’ ‘rseg’

See section 'Cross-references' in the 'Writing R Extensions' manual.

* checking for missing documentation entries ... WARNING
Undocumented code objects:
  ‘cseg’ ‘eseg’ ‘rseg’ ‘segmob’
All user-level objects in a package should have documentation entries.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking examples ... [4s/4s] OK
* checking PDF version of manual ... OK
* DONE

Status: 2 WARNINGs, 3 NOTEs
See
  ‘/srv/rf/building/build_2018-08-24-17-08/RF_PKG_CHECK/PKGS/rseg.Rcheck/00check.log’
for details.


Run time: 63.21 seconds.