===============================
R CMD BUILD
===============================
* checking for file ‘TENxXeniumData/DESCRIPTION’ ... OK
* preparing ‘TENxXeniumData’:
* 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 ‘TENxXeniumData_0.99.0.tar.gz’
===============================
BiocCheckGitClone('TENxXeniumData')
===============================
─ BiocCheckVersion: 1.39.5
─ BiocVersion: 3.19
─ Package: TENxXeniumData
─ PackageVersion: 0.99.0
─ sourceDir: /home/pkgbuild/packagebuilder/workers/jobs/3255/TENxXeniumData_20231227170917/TENxXeniumData
─ platform: unix
─ isTarBall: FALSE
* Checking valid files...
* Checking for stray BiocCheck output folders...
* Checking for inst/doc folders...
* Checking DESCRIPTION...
* Checking if DESCRIPTION is well formatted...
* Checking for valid maintainer...
* Checking CITATION...
─ BiocCheck results ──
0 ERRORS | 0 WARNINGS | 0 NOTES
For more details, run
browseVignettes(package = 'BiocCheck')
===============================
R CMD CHECK
===============================
* using log directory ‘/home/pkgbuild/packagebuilder/workers/jobs/3255/TENxXeniumData_20231227170917/TENxXeniumData.Rcheck’
* using R Under development (unstable) (2023-11-11 r85510)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
GNU Fortran (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
* running under: Ubuntu 22.04.3 LTS
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘TENxXeniumData/DESCRIPTION’ ... OK
* this is package ‘TENxXeniumData’ version ‘0.99.0’
* 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 ‘TENxXeniumData’ 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 R files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... [17s/18s] OK
* checking whether the package can be loaded with stated dependencies ... [17s/18s] OK
* checking whether the package can be unloaded cleanly ... [17s/17s] OK
* checking whether the namespace can be loaded with stated dependencies ... [16s/17s] OK
* checking whether the namespace can be unloaded cleanly ... [17s/17s] OK
* checking loading without being on the library search path ... [17s/18s] OK
* checking whether startup messages can be suppressed ... [17s/18s] 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 ... [49s/50s] 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 ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... [20s/21s] OK
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes in ‘inst/doc’ ... 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: OK
===============================
BiocCheck('TENxXeniumData_0.99.0.tar.gz')
===============================
─ BiocCheckVersion: 1.39.5
─ BiocVersion: 3.19
─ Package: TENxXeniumData
─ PackageVersion: 0.99.0
─ sourceDir: /tmp/RtmpbnkH9A/file1011b6135c8113/TENxXeniumData
─ installDir: /tmp/RtmpbnkH9A/file1011b6842b179
─ BiocCheckDir: /home/pkgbuild/packagebuilder/workers/jobs/3255/TENxXeniumData_20231227170917/TENxXeniumData.BiocCheck
─ platform: unix
─ isTarBall: TRUE
* Installing package...
* 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...
ExperimentData
* Checking for non-trivial biocViews...
* Checking that biocViews come from the same category...
* Checking biocViews validity...
* Checking for recommended biocViews...
* Checking build system compatibility...
* Checking for blank lines in DESCRIPTION...
* Checking if DESCRIPTION is well formatted...
* Checking for proper Description: field...
* NOTE: The Description field in the DESCRIPTION is made up by less
than 3 sentences. Please consider expanding this field, and
structure it as a full paragraph
* Checking for whitespace in DESCRIPTION field names...
* Checking that Package field matches directory/tarball name...
* Checking for Version field...
* Checking for valid maintainer...
* NOTE: Consider adding the maintainer's ORCID iD in 'Authors@R'
with 'comment=c(ORCID="...")'
* Checking License: for restrictive use...
* Checking for recommeded fields in DESCRIPTION...
* Checking for pinned package versions...
* Checking DESCRIPTION/NAMESPACE consistency...
* WARNING: Import utils in DESCRIPTION as well as NAMESPACE.
* 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 TENxXeniumData...
* Checking coding practice...
* Checking parsed R code in R directory, examples, vignettes...
* Checking function lengths...
* Checking man page documentation...
* Checking package NEWS...
* NOTE: Consider adding a NEWS file, so your package news will be
included in Bioconductor release announcements.
* Checking unit tests...
* 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...
* NOTE: Consider shorter lines; 4 lines (2%) are > 80 characters
long.
* NOTE: Consider multiples of 4 spaces for line indents; 53 lines
(23%) are not.
See https://contributions.bioconductor.org/r-code.html
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...
* ERROR: Maintainer must subscribe to the bioc-devel mailing list.
Subscribe here: https://stat.ethz.ch/mailman/listinfo/bioc-devel
* Checking for support site registration...
* ERROR: Maintainer must register at the support site; visit
https://support.bioconductor.org/accounts/signup/
─ BiocCheck results ──
2 ERRORS | 1 WARNINGS | 6 NOTES
See the TENxXeniumData.BiocCheck folder and run
browseVignettes(package = 'BiocCheck')
for details.