===============================
R CMD BUILD
===============================
* checking for file UCSC.utils/DESCRIPTION ... OK
* preparing UCSC.utils:
* 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 UCSC.utils_0.99.1.tar.gz
===============================
BiocCheckGitClone('UCSC.utils')
===============================
BiocCheckVersion: 1.39.26
BiocVersion: 3.19
Package: UCSC.utils
PackageVersion: 0.99.1
sourceDir: /home/pkgbuild/packagebuilder/workers/jobs/3343/UCSC.utils_20240321132714/UCSC.utils
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...
* 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 results
0 ERRORS | 0 WARNINGS | 1 NOTES
For more details, run
browseVignettes(package = 'BiocCheck')
===============================
R CMD CHECK
===============================
* using log directory /home/pkgbuild/packagebuilder/workers/jobs/3343/UCSC.utils_20240321132714/UCSC.utils.Rcheck
* using R Under development (unstable) (2024-03-18 r86148)
* 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.4 LTS
* using session charset: UTF-8
* using option --no-vignettes
* checking for file UCSC.utils/DESCRIPTION ... OK
* this is package UCSC.utils version 0.99.1
* 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 UCSC.utils 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 ... [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 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 ... [5s/5s] 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 ... [4s/20s] OK
Examples with CPU (user + system) or elapsed time > 5s
user system elapsed
UCSC_dbselect 1.109 0.120 7.971
UCSC.api.url 0.258 0.004 7.187
* checking for unstated dependencies in tests ... OK
* checking tests ...
Running testthat.R [3s/10s]
[3s/10s] OK
* 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: OK
===============================
BiocCheck('UCSC.utils_0.99.1.tar.gz')
===============================
BiocCheckVersion: 1.39.26
BiocVersion: 3.19
Package: UCSC.utils
PackageVersion: 0.99.1
sourceDir: /tmp/Rtmpe5C8sK/filef1872f0546a0/UCSC.utils
installDir: /tmp/Rtmpe5C8sK/filef1872200f3741
BiocCheckDir: /home/pkgbuild/packagebuilder/workers/jobs/3343/UCSC.utils_20240321132714/UCSC.utils.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...
Software
* 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...
* 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 recommended DESCRIPTION fields...
* Checking for Bioconductor software dependencies...
Bioconductor dependencies found in Imports & Depends (20%).
* Checking for pinned package versions in DESCRIPTION...
* Checking DESCRIPTION/NAMESPACE consistency...
* 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 UCSC.utils...
* Checking coding practice...
* NOTE: Avoid sapply(); use vapply()
* Checking parsed R code in R directory, examples, vignettes...
* Checking function lengths...
* NOTE: The recommended function length is 50 lines or less. There
is 1 function greater than 50 lines.
* Checking man page documentation...
* NOTE: Usage of dontrun{} / donttest{} tags found in man page
examples. 17% of man pages use at least one of these tags.
* NOTE: Use donttest{} instead of dontrun{}.
* Checking package NEWS...
* Checking unit tests...
* Checking skip_on_bioc() in tests...
* Checking formatting of DESCRIPTION, NAMESPACE, man pages, R source,
and vignette source...
* NOTE: Consider multiples of 4 spaces for line indents; 157 lines
(13%) 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...
Maintainer is subscribed to bioc-devel.
* Checking for support site registration...
Maintainer is registered at support site.
Package is in the Support Site Watched Tags.
BiocCheck results
0 ERRORS | 0 WARNINGS | 6 NOTES
See the UCSC.utils.BiocCheck folder and run
browseVignettes(package = 'BiocCheck')
for details.