• using R Under development (unstable) (2025-09-14 r88831)
• using platform: x86_64-pc-linux-gnu
• R was compiled by     Debian clang version 19.1.7 (3+b2)     Debian flang-new version 19.1.7 (3+b2)
• running under: Debian GNU/Linux forky/sid
• using session charset: UTF-8
• checking for file ‘dplyr/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘dplyr’ version ‘1.1.4’
• package encoding: UTF-8
• checking CRAN incoming feasibility ... [4s/5s] OK
• 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 whether package ‘dplyr’ can be installed ... OK See the install log for details.
• used C++ compiler: ‘Debian clang version 19.1.7 (3+b2)’
• checking package directory ... OK
• checking for future file timestamps ... OK
• checking ‘build’ 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 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/2s] OK
• checking loading without being on the library search path ... [1s/1s] OK
• checking whether startup messages can be suppressed ... [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 ... [33s/42s] OK
• checking Rd files ... [3s/3s] 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 ... [0s/0s] OK
• checking LazyData ... 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 ... NOTE File ‘dplyr/libs/dplyr.so’:   Found non-API calls to R: ‘LEVELS’, ‘OBJECT’, ‘PRVALUE’,     ‘R_shallow_duplicate_attr’, ‘Rf_allocSExp’, ‘SET_PRCODE’,     ‘SET_PRENV’, ‘SET_PRVALUE’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points.
• checking installed files from ‘inst/doc’ ... OK
• checking files in ‘vignettes’ ... OK
• checking examples ... [23s/32s] OK Examples with CPU (user + system) or elapsed time > 5s         user system elapsed storms 4.155 0.031 5.57
• checking for unstated dependencies in ‘tests’ ... OK
• checking tests ... [126s/174s] OK   Running ‘testthat.R’ [126s/173s]
• checking for unstated dependencies in vignettes ... OK
• checking package vignettes ... OK
• checking re-building of vignette outputs ... [48s/78s] OK
• checking PDF version of manual ... [16s/19s] OK
• checking HTML version of manual ... [7s/13s] OK
• checking for non-standard things in the check directory ... OK
• DONE

Status: 1 NOTE