* using log directory 'd:/RCompile/CRANincoming/R-devel/ezTrack.Rcheck' * using R Under development (unstable) (2025-09-09 r88803 ucrt) * using platform: x86_64-w64-mingw32 * R was compiled by gcc.exe (GCC) 14.2.0 GNU Fortran (GCC) 14.2.0 * running under: Windows Server 2022 x64 (build 20348) * using session charset: UTF-8 * checking for file 'ezTrack/DESCRIPTION' ... OK * checking extension type ... Package * this is package 'ezTrack' version '0.1.0' * package encoding: UTF-8 * checking CRAN incoming feasibility ... NOTE Maintainer: 'Taylor Craft ' New submission * 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 ... NOTE Found the following hidden files and directories: .github These were most likely included in error. See section 'Package structure' in the 'Writing R Extensions' manual. CRAN-pack does not know about .github * checking for portable file names ... WARNING Found the following files with non-portable file names: docs/articles/getting-started_files/Proj4Leaflet-1.0.1/proj4leaflet 2.js docs/articles/getting-started_files/htmltools-fill-0.5.8.1/fill 2.css docs/articles/getting-started_files/htmlwidgets-1.6.4/htmlwidgets 2.js docs/articles/getting-started_files/leaflet-1.3.1/leaflet 2.css docs/articles/getting-started_files/leaflet-1.3.1/leaflet 2.js docs/articles/getting-started_files/leaflet-binding-2.2.2/leaflet 2.js docs/articles/getting-started_files/leaflet-providers-2.0.0/leaflet-providers_2.0.0 2.js docs/articles/getting-started_files/leaflet-providers-plugin-2.2.2/leaflet-providers-plugin 2.js docs/articles/getting-started_files/leafletfix-1.0.0/leafletfix 2.css docs/articles/getting-started_files/proj4-2.6.2/proj4.min 2.js docs/articles/getting-started_files/rstudio_leaflet-1.3.1/rstudio_leaflet 2.css docs/articles/getting-started_files/leaflet-1.3.1/images 2 docs/articles/getting-started_files/rstudio_leaflet-1.3.1/images 2 These are not fully portable file names. See section 'Package structure' in the 'Writing R Extensions' manual. Found the following non-portable file paths: ezTrack/docs/articles/getting-started_files/leaflet-providers-plugin-2.2.2/leaflet-providers-plugin 2.js ezTrack/docs/articles/getting-started_files/leaflet-providers-plugin-2.2.2/leaflet-providers-plugin.js Tarballs are only required to store paths of up to 100 bytes and cannot store those of more than 256 bytes, with restrictions including to 100 bytes for the final component. See section 'Package structure' in the 'Writing R Extensions' manual. * checking whether package 'ezTrack' can be installed ... OK * checking installed package size ... OK * checking package directory ... OK * checking for future file timestamps ... OK * checking 'build' directory ... OK * checking DESCRIPTION meta-information ... NOTE Missing dependency on R >= 4.1.0 because package code uses the pipe |> or function shorthand \(...) syntax added in R 4.1.0. File(s) using such syntax: 'ez_fix_rate_plot.R' 'ez_summary.R' 'ez_track.R' * checking top-level files ... NOTE Non-standard files/directories found at top level: 'CRAN-SUBMISSION' 'LICENSE.md' '_pkgdown.yml' 'cran-comments.md' 'doc' 'docs' * 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 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 ... 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 LazyData ... OK * checking data for ASCII and uncompressed saves ... OK * checking installed files from 'inst/doc' ... OK * checking files in 'vignettes' ... OK * checking examples ... OK * checking for unstated dependencies in vignettes ... OK * checking package vignettes ... OK * checking re-building of vignette outputs ... OK * checking PDF version of manual ... [13s] OK * checking HTML version of manual ... OK * DONE Status: 1 WARNING, 4 NOTEs