• using R version 2.10.0 Under development (unstable) (2009-07-02 r48890)
• using session charset: UTF-8
• checking for file 'geometry/DESCRIPTION' ... OK
• this is package 'geometry' version '0.1-4'
• checking package name space information ... OK
• checking package dependencies ... OK
• checking if this is a source package ... OK
• checking for executable files ... OK
• checking whether package 'geometry' can be installed ... WARNING
  Found the following significant warnings:
  Warning: invalid whitespace before brace in file 'entry.value.Rd' at ' \item{value} { An array of length this-is-escaped-codenormal-bracket17bracket-normal. }'
  See http://www.r-project.org/nosvn/R.check/r-devel-linux-ix86/geometry-00install.html for details.
• checking package directory ... OK
• checking for portable file names ... OK
• checking for sufficient/correct file permissions ... 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 whether the name space 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 files against version 2 parser ... WARNING
  Warning in parse_Rd("./man/entry.value.Rd", encoding = "unknown") :
  bad markup (extra space?) at entry.value.Rd:19:15
  Warning: ./man/entry.value.Rd:19: Unnecessary braces at ‘{ An array of length \code{nrow(idx)}. }’
• checking Rd cross-references ... OK
• checking for missing documentation entries ... OK
• 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 PDF version of manual ... OK