SCM

R Development Page

Funclustering log file (check_x86_64_linux)

Tue Feb 18 18:10:11 2020: Checking package Funclustering (SVN revision 61) ...
* using log directory ‘/srv/rf/building/build_2020-02-18-18-07/RF_PKG_CHECK/PKGS/Funclustering.Rcheck’
* using R version 3.6.2 Patched (2020-02-17 r77820)
* using platform: x86_64-pc-linux-gnu (64-bit)
* using session charset: UTF-8
* using option ‘--as-cran’
* checking for file ‘Funclustering/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘Funclustering’ version ‘1.0.3’
* package encoding: UTF-8
* checking CRAN incoming feasibility ... NOTE
Maintainer: ‘Cristian Preda ’

New submission

Package was archived on CRAN

CRAN repository db overrides:
  X-CRAN-Comment: Archived on 2018-12-03 as no maintainer to correct
    check problems.
  Maintainer: ORPHANED
CRAN repository db conflicts: ‘Maintainer’

The Description field should not start with the package name,
  'This package' or similar.

The Date field is over a month old.
* 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 ‘Funclustering’ can be installed ... [71s/74s] OK
* checking installed package size ... NOTE
  installed size is 23.4Mb
  sub-directories of 1Mb or more:
    libs  23.3Mb
* checking package directory ... OK
* checking for future file timestamps ... 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 ... OK
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... [8s/8s] OK
* checking Rd files ... OK
* checking Rd metadata ... OK
* checking Rd line widths ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking line endings in C/C++/Fortran sources/headers ... OK
* checking line endings in Makefiles ... OK
* checking compilation flags in Makevars ... OK
* checking for GNU extensions in Makefiles ... OK
* checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
* checking use of SHLIB_OPENMP_*FLAGS in Makefiles ... OK
* checking include directives in Makefiles ... NOTE
Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/Funclustering/makefile
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'.
* checking pragmas in C/C++ headers and code ... OK
* checking compilation flags used ... OK
* checking compiled code ... OK
* checking examples ... [8s/8s] OK
** found \donttest examples: check also with --run-donttest
* checking PDF version of manual ... OK
* checking for detritus in the temp directory ... OK
* DONE

Status: 3 NOTEs
See
  ‘/srv/rf/building/build_2020-02-18-18-07/RF_PKG_CHECK/PKGS/Funclustering.Rcheck/00check.log’
for details.


Run time: 136.96 seconds.

Additional Logs:   00install.out
Thanks to:
Vienna University of Economics and Business Powered By FusionForge