===============================
R CMD BUILD
===============================
* checking for file ‘chevreuldata/DESCRIPTION’ ... OK
* preparing ‘chevreuldata’:
* checking DESCRIPTION meta-information ... OK
* installing the package to build vignettes
* creating vignettes ... OK
* checking for LF line-endings in source and make files and shell scripts
* checking for empty or unneeded directories
* building ‘chevreuldata_0.99.15.tar.gz’
===============================
BiocCheckGitClone('chevreuldata')
===============================
→ sourceDir: /media/volume/teran2_disk/pkgbuild/packagebuilder/workers/jobs/3332/9c45adfe663d5a0e3071313f62b94fc79e030c40/chevreuldata
→ BiocVersion: 3.20
→ Package: chevreuldata
→ PackageVersion: 0.99.15
→ BiocCheckDir: /media/volume/teran2_disk/pkgbuild/packagebuilder/workers/jobs/3332/9c45adfe663d5a0e3071313f62b94fc79e030c40/chevreuldata.BiocCheck
→ BiocCheckVersion: 1.41.17
→ sourceDir: /media/volume/teran2_disk/pkgbuild/packagebuilder/workers/jobs/3332/9c45adfe663d5a0e3071313f62b94fc79e030c40/chevreuldata
→ installDir: NULL
→ isTarBall: FALSE
→ platform: unix
* Checking valid files...
* Checking for stray BiocCheck output folders...
* Checking for inst/doc folders...
* Checking if DESCRIPTION is well formatted...
* Checking for valid maintainer...
* Checking CITATION...
i NOTE: (Optional) CITATION file not found. Only include a CITATION file if
there is a preprint or publication for this Bioconductor package. Note that
Bioconductor packages are not required to have a CITATION file but it is useful
both for users and for tracking Bioconductor project-wide metrics. When
including a CITATION file, add the publication using the 'doi' argument of
'bibentry()'.
── BiocCheck v1.41.17 results ──────────────────────────────────────────────────
✖ 0 ERRORS | ⚠ 0 WARNINGS | • 1 NOTES
i For more details, run
browseVignettes(package = 'BiocCheck')
===============================
R CMD CHECK
===============================
* using log directory ‘/media/volume/teran2_disk/pkgbuild/packagebuilder/workers/jobs/3332/9c45adfe663d5a0e3071313f62b94fc79e030c40/chevreuldata.Rcheck’
* using R version 4.4.1 (2024-06-14)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
GNU Fortran (Ubuntu 13.2.0-23ubuntu4) 13.2.0
* running under: Ubuntu 24.04.1 LTS
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘chevreuldata/DESCRIPTION’ ... OK
* this is package ‘chevreuldata’ version ‘0.99.15’
* package encoding: UTF-8
* 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 for sufficient/correct file permissions ... OK
* checking serialization versions ... OK
* checking whether package ‘chevreuldata’ 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 ... 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 ... [3s/3s] OK
* checking whether the package can be loaded with stated dependencies ... [4s/4s] OK
* checking whether the package can be unloaded cleanly ... [4s/4s] OK
* checking whether the namespace can be loaded with stated dependencies ... [4s/4s] OK
* checking whether the namespace can be unloaded cleanly ... [4s/4s] OK
* checking loading without being on the library search path ... [4s/4s] OK
* checking whether startup messages can be suppressed ... [3s/3s] OK
* checking use of S3 registration ... OK
* checking dependencies in R code ... NOTE
Namespace in Imports field not imported from: ‘SingleCellExperiment’
All declared Imports should be used.
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... [13s/13s] 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 ... WARNING
Undocumented code objects:
‘shayler_developing_human_retina_sce’
All user-level objects in a package should have documentation entries.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... [9s/10s] OK
Examples with CPU (user + system) or elapsed time > 5s
user system elapsed
human_gene_transcript_sce 4.502 0.47 5.469
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes ... OK
* checking running R code from vignettes ... SKIPPED
* checking re-building of vignette outputs ... SKIPPED
* checking PDF version of manual ... [2s/2s] OK
* DONE
Status: 1 WARNING, 1 NOTE
See
‘/media/volume/teran2_disk/pkgbuild/packagebuilder/workers/jobs/3332/9c45adfe663d5a0e3071313f62b94fc79e030c40/chevreuldata.Rcheck/00check.log’
for details.
===============================
BiocCheck('chevreuldata_0.99.15.tar.gz')
===============================
── Installing chevreuldata ─────────────────────────────────────────────────────
✔ Package installed successfully
── chevreuldata session metadata ───────────────────────────────────────────────
→ sourceDir: /tmp/Rtmp57RAE8/file36dc0b2584a437/chevreuldata
→ BiocVersion: 3.20
→ Package: chevreuldata
→ PackageVersion: 0.99.15
→ BiocCheckDir: /media/volume/teran2_disk/pkgbuild/packagebuilder/workers/jobs/3332/9c45adfe663d5a0e3071313f62b94fc79e030c40/chevreuldata.BiocCheck
→ BiocCheckVersion: 1.41.17
→ sourceDir: /tmp/Rtmp57RAE8/file36dc0b2584a437/chevreuldata
→ installDir: /tmp/Rtmp57RAE8/file36dc0b20596294
→ isTarBall: TRUE
→ platform: unix
── Running BiocCheck on chevreuldata ───────────────────────────────────────────
* Checking for deprecated package usage...
* Checking for remote package usage...
* Checking for 'LazyData: true' usage...
* Checking version number...
* Checking for version number mismatch...
* Checking new package version number...
* Checking R version dependency...
* Checking package size...
* Checking individual file sizes...
* Checking biocViews...
* Checking that biocViews are present...
* Checking package type based on biocViews...
→ Software
* Checking for non-trivial biocViews...
* Checking that biocViews come from the same category...
* Checking biocViews validity...
* Checking for recommended biocViews...
i NOTE: Consider adding these automatically suggested biocViews:
ThirdPartyClient, DataImport, GUI
i Search 'biocViews' at https://contributions.bioconductor.org
* Checking build system compatibility...
* Checking for proper Description: field...
* Checking if DESCRIPTION is well formatted...
* Checking for whitespace in DESCRIPTION field names...
* Checking that Package field matches directory/tarball name...
* Checking for Version: field...
* Checking License: for restrictive use...
* Checking for recommended DESCRIPTION fields...
* Checking for Bioconductor software dependencies...
i Bioconductor dependencies found in Imports & Depends (67%).
* Checking for pinned package versions in DESCRIPTION...
* Checking .Rbuildignore...
* Checking for stray BiocCheck output folders...
* Checking vignette directory...
* Checking whether vignette is built with 'R CMD build'...
* Checking package installation calls in R code...
* Checking for library/require of chevreuldata...
* Checking coding practice...
* Checking parsed R code in R directory, examples, vignettes...
* Checking function lengths...
* Checking man page documentation...
* Checking package NEWS...
* Checking unit tests...
i NOTE: Consider adding unit tests. We strongly encourage them. See
https://contributions.bioconductor.org/tests.html
* Checking skip_on_bioc() in tests...
* Checking formatting of DESCRIPTION, NAMESPACE, man pages, R source, and
vignette source...
i NOTE: Consider shorter lines; 12 lines (5%) are > 80 characters long.
First few lines:
• R/globals.R#L1 utils::globalVariables(c("human_gene_tra ...
• ...
• vignettes/human_gene_transcript_sce.Rmd#L177 ```{r vignetteBiblio, results =
"asis", ...
i NOTE: Consider multiples of 4 spaces for line indents; 2 lines (1%) are not.
First few lines:
• vignettes/human_gene_transcript_sce.Rmd#L65 install.packages("BiocManager")
...
• vignettes/human_gene_transcript_sce.Rmd#L66 } ...
i See https://contributions.bioconductor.org/r-code.html
i See styler package: https://cran.r-project.org/package=styler as described in
the BiocCheck vignette.
* Checking if package already exists in CRAN...
* Checking if new package already exists in Bioconductor...
* Checking for bioc-devel mailing list subscription...
i Maintainer is subscribed to bioc-devel.
* Checking for support site registration...
i Maintainer is registered at support site.
i Package is in the Support Site Watched Tags.
── BiocCheck v1.41.17 results ──────────────────────────────────────────────────
✖ 0 ERRORS | ⚠ 0 WARNINGS | • 4 NOTES
i See the chevreuldata.BiocCheck folder and run
browseVignettes(package = 'BiocCheck')
for details.