• using R version 3.5.0 (2018-04-23)
• using platform: x86_64-pc-linux-gnu (64-bit)
• using session charset: UTF-8
• checking for file ‘goalprog/DESCRIPTION’ ... OK
• this is package ‘goalprog’ version ‘1.0-2’
• 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 ‘goalprog’ can be installed ... 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
  Package in Depends field not imported from: ‘lpSolve’
    These packages need to be imported from (in the NAMESPACE file)
    for when this namespace is loaded but not attached.
• checking S3 generic/method consistency ... NOTE
  Found the following apparent S3 methods exported but not registered:
    print.llgpcptab print.llgpout print.llgptab
  See section ‘Registering S3 methods’ in the ‘Writing R Extensions’
  manual.
• checking replacement functions ... OK
• checking foreign function calls ... OK
• checking R code for possible problems ... [5s/8s] OK
• checking Rd files ... NOTE
  prepare_Rd: llgpcp.Rd:45-46: Dropping empty section \examples
• checking Rd metadata ... OK
• checking Rd line widths ... NOTE
  Rd file 'llgpcp.Rd':
    \usage lines wider than 90 characters:
       llgpcp(coefficients, targets, achievements, variable.classes, maxiter = 1000, verbose = FALSE)
  
  These lines will be truncated in the PDF manual.
• checking Rd cross-references ... OK
• checking for missing documentation entries ... OK
• checking for code/documentation mismatches ... OK
• checking Rd \usage sections ... NOTE
  S3 methods shown with full name in documentation object 'print.llgpcptab':
    ‘print.llgpcptab’
  
  S3 methods shown with full name in documentation object 'print.llgpout':
    ‘print.llgpout’
  
  S3 methods shown with full name in documentation object 'print.llgptab':
    ‘print.llgptab’
  
  The \usage entries for S3 methods should use the \method markup and not
  their full name.
  See chapter ‘Writing R documentation files’ in the ‘Writing R
  Extensions’ manual.
• checking Rd contents ... OK
• checking for unstated dependencies in examples ... OK
• checking contents of ‘data’ directory ... OK
• checking data for non-ASCII characters ... OK
• checking data for ASCII and uncompressed saves ... OK
• checking examples ... [1s/1s] OK
• checking PDF version of manual ... OK
• DONE

Status: 5 NOTEs