Package fRegression_2100.76.tar.gz has been built for Windows - with a WARNING

[Uwe.Ligges at R-Project.org]

Dear package maintainer,
 
this notification has been generated automatically.
Your package fRegression_2100.76.tar.gz did pass 'R CMD check' only with WARNING(s).
It has been built for Windows and
will be published within 24 hours in the corresponding CRAN directory
(CRAN/bin/windows/contrib/2.10/).

Please consider to submit a fixed version without any WARNING until January 15.
For details (and for results on other platforms) see
http://cran.r-project.org/web/checks/check_summary.html
R version 2.10.1 (2009-12-14)
 
All the best,
Uwe Ligges
(Maintainer of binary packages for Windows)
-------------- next part --------------
* using log directory 'd:/Rcompile/CRANpkg/local/2.10/fRegression.Rcheck'
* using R version 2.10.1 (2009-12-14)
* using session charset: ISO8859-1
* checking for file 'fRegression/DESCRIPTION' ... OK
* this is package 'fRegression' version '2100.76'
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking whether package 'fRegression' can be installed ... OK
* checking package directory ... OK
* checking for portable file names ... OK
* checking DESCRIPTION meta-information ... OK
* checking top-level 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 for unstated 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 ... OK
* checking Rd files ... OK
* checking Rd metadata ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... WARNING
Undocumented S4 methods:
  generic 'summary' and siglist 'sparseMatrix'
All user-level objects in a package (including S4 classes and methods)
should have documentation entries.
See the chapter 'Writing R documentation files' in manual 'Writing R
Extensions'.
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... OK
* checking line endings in C/C++/Fortran sources/headers ... OK
* checking line endings in Makefiles ... OK
* checking for portable compilation flags in Makevars ... OK
* checking for portable use of $BLAS_LIBS ... OK
* checking examples ... OK
* checking tests ... OK
* checking PDF version of manual ... OK