* using log directory ‘/srv/hornik/tmp/CRAN/ergmclust.Rcheck’ * using R Under development (unstable) (2024-05-12 r86534) * using platform: x86_64-pc-linux-gnu * R was compiled by Debian clang version 18.1.4 (1) Debian flang-new version 18.1.4 (1) * running under: Debian GNU/Linux trixie/sid * using session charset: UTF-8 * checking for file ‘ergmclust/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘ergmclust’ version ‘1.0.0’ * package encoding: UTF-8 * checking CRAN incoming feasibility ... [3s/5s] WARNING Maintainer: ‘Amal Agarwal ’ New submission Package was archived on CRAN Insufficient package version (submitted: 1.0.0, existing: 1.0.0) Possibly misspelled words in DESCRIPTION: ERGM (3:8) ERGMs (11:104) Vu (11:169) al (11:176) et (11:172) CRAN repository db overrides: X-CRAN-Comment: Archived on 2022-12-05 as issues were not corrected despite reminders. Found the following (possibly) invalid URLs: URL: https://amstat.tandfonline.com/doi/abs/10.1080/00401706.2019.1623076 From: man/ergmclust-package.Rd man/ergmclust.Rd Status: 403 Message: Forbidden 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 ‘ergmclust’ can be installed ... [22s/22s] WARNING Found the following significant warnings: ergmclust.cpp:214:16: warning: use of bitwise '&' with boolean operands [-Wbitwise-instead-of-logical] See ‘/srv/hornik/tmp/CRAN/ergmclust.Rcheck/00install.out’ for details. * used C++ compiler: ‘Debian clang version 18.1.5 (2)’ * checking C++ specification ... NOTE Specified C++11: please drop specification unless essential * 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 ... [1s/1s] OK * checking whether the package can be loaded with stated dependencies ... [1s/1s] OK * checking whether the package can be unloaded cleanly ... [1s/1s] OK * checking whether the namespace can be loaded with stated dependencies ... [1s/1s] OK * checking whether the namespace can be unloaded cleanly ... [1s/1s] OK * checking loading without being on the library search path ... [1s/1s] 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 ... [6s/6s] OK * checking Rd files ... [0s/0s] 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 ... NOTE Documented arguments not in \usage in Rd file 'ELBO_conv_weighted_stat_undir_K1.Rd': ‘gamma’ Documented arguments not in \usage in Rd file 'wrapper_weighted_stat_undir.Rd': ‘theta_init’ Functions with \usage entries need to have the appropriate \alias entries, and all their arguments documented. The \usage entries must correspond to syntactically valid R code. 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 ... [0s/0s] OK * checking data for ASCII and uncompressed saves ... 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 PKG_*FLAGS in Makefiles ... OK * checking use of SHLIB_OPENMP_*FLAGS in Makefiles ... OK * checking pragmas in C/C++ headers and code ... OK * checking compilation flags used ... OK * checking compiled code ... OK * checking examples ... [5s/5s] OK * checking PDF version of manual ... [3s/3s] OK * checking HTML version of manual ... [1s/1s] OK * checking for non-standard things in the check directory ... OK * checking for detritus in the temp directory ... OK * DONE Status: 2 WARNINGs, 2 NOTEs