* using log directory 'd:/RCompile/CRANincoming/R-devel/sspse.Rcheck'
* using R Under development (unstable) (2024-09-06 r87103 ucrt)
* using platform: x86_64-w64-mingw32
* R was compiled by
    gcc.exe (GCC) 13.2.0
    GNU Fortran (GCC) 13.2.0
* running under: Windows Server 2022 x64 (build 20348)
* using session charset: UTF-8
* checking for file 'sspse/DESCRIPTION' ... OK
* checking extension type ... Package
* this is package 'sspse' version '1.1.0-2'
* package encoding: UTF-8
* checking CRAN incoming feasibility ... NOTE
Maintainer: 'Mark S. Handcock <handcock@stat.ucla.edu>'

License components with restrictions and base license permitting such:
  GPL-3 + file LICENSE
File 'LICENSE':
  -------------------------------------------------------
  License for the 'RDS Analyst' component package 'sspse'
  -------------------------------------------------------
  
  This software is distributed under the GPL-3 license.  It is free,
  open source, and has the following attribution requirements
  (GPL Section 7):
  
  (a) you agree to retain in 'sspse' and any modifications to 'sspse'
      the copyright, author attribution and URL information as
      provided at https://hpmrg.org/attribution/
  (b) you agree that 'sspse' and any modifications to 'sspse' will,
      when used, display the attribution:
       Based on HPMRG project software (https://hpmrg.org).
       For license and citation information see https://hpmrg.org/attribution/
  --------------------------------------------------
  
  What does this mean?
  ====================
  
  If you are modifying 'sspse' or adopting any source code from
  'sspse' for use in another application, you must ensure that the
  copyright and attributions mentioned in the license above appear
  in the code of your modified version or application. These 
  attributions must also appear when the package is loaded
  (e.g., via 'library' or 'require').
  
  Enjoy!
  
  Mark S. Handcock, University of California - Los Angeles
  Krista J. Gile , University of Massachusetts - Amherst
  
  Copyright 2015
* 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 hidden files and directories ... OK
* checking for portable file names ... OK
* checking whether package 'sspse' can be installed ... OK
* used C compiler: 'gcc.exe (GCC) 13.2.0'
* checking installed package size ... OK
* 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 code 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 whether startup messages can be suppressed ... 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 ... [17s] 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 contents of 'data' directory ... OK
* checking data for non-ASCII characters ... OK
* checking data for ASCII and uncompressed saves ... OK
* checking line endings in C/C++/Fortran sources/headers ... OK
* checking pragmas in C/C++ headers and code ... OK
* checking compilation flags used ... OK
* checking compiled code ... OK
* checking examples ... [26s] OK
* checking PDF version of manual ... [13s] OK
* checking HTML version of manual ... OK
* DONE
Status: 1 NOTE