===============================
R CMD BUILD
===============================
* checking for file HiSpaR/DESCRIPTION ... OK
* preparing HiSpaR:
* checking DESCRIPTION meta-information ... OK
* cleaning src
* running cleanup
* installing the package (it is needed to build vignettes)
* creating vignettes ... OK
* cleaning src
* running cleanup
* checking for LF line-endings in source and make files and shell scripts
* checking for empty or unneeded directories
* looking to see if a data/datalist file should be added
* building HiSpaR_0.99.1.tar.gz
===============================
BiocCheckGitClone('HiSpaR')
===============================
sourceDir: /home/pkgbuild/packagebuilder/workers/jobs/4079/b2c79798ff83a41ce24f2d5d015d463dc9db03ec/HiSpaR
BiocVersion: 3.23
Package: HiSpaR
PackageVersion: 0.99.1
BiocCheckDir: /home/pkgbuild/packagebuilder/workers/jobs/4079/b2c79798ff83a41ce24f2d5d015d463dc9db03ec/HiSpaR.BiocCheck
BiocCheckVersion: 1.47.18
sourceDir: /home/pkgbuild/packagebuilder/workers/jobs/4079/b2c79798ff83a41ce24f2d5d015d463dc9db03ec/HiSpaR
installDir: NULL
isTarBall: FALSE
platform: unix
* Checking valid files...
* Checking individual file sizes...
* Checking for stray BiocCheck output folders...
* Checking for inst/doc folders...
* Checking if DESCRIPTION is well formatted...
* Checking NAMESPACE...
* 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.47.18 results
0 ERRORS | 0 WARNINGS | i 1 NOTES
i For more details, run
browseVignettes(package = 'BiocCheck')
===============================
R CMD CHECK
===============================
* using log directory /home/pkgbuild/packagebuilder/workers/jobs/4079/b2c79798ff83a41ce24f2d5d015d463dc9db03ec/HiSpaR.Rcheck
* using R Under development (unstable) (2026-01-15 r89304)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
GNU Fortran (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
* running under: Ubuntu 24.04.3 LTS
* using session charset: UTF-8
* using option --no-vignettes
* checking for file HiSpaR/DESCRIPTION ... OK
* checking extension type ... Package
* this is package HiSpaR 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 whether package HiSpaR can be installed ... OK
* used C++ compiler: g++ (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
* checking C++ specification ... INFO
specified C++17
* checking installed package size ... OK
* checking package directory ... OK
* checking for future file timestamps ... OK
* checking build directory ... OK
* checking DESCRIPTION meta-information ... NOTE
License stub is invalid DCF.
Package listed in more than one of Depends, Imports, Suggests, Enhances:
Matrix
A package should be listed in only one of these fields.
* 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 ... [7s/7s] OK
* checking whether the package can be loaded with stated dependencies ... [7s/7s] OK
* checking whether the package can be unloaded cleanly ... [7s/7s] OK
* checking whether the namespace can be loaded with stated dependencies ... [7s/7s] OK
* checking whether the namespace can be unloaded cleanly ... [7s/7s] OK
* checking loading without being on the library search path ... [7s/7s] 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 ... [22s/22s] 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 contents of data directory ... OK
* checking data for non-ASCII characters ... [0s/0s] OK
* checking data for ASCII and uncompressed saves ... OK
* checking line endings in shell scripts ... OK
* checking line endings in C/C++/Fortran sources/headers ... OK
* checking line endings in Makefiles ... OK
* checking compilation flags in Makevars ... OK
* checking for GNU extensions in Makefiles ... OK
* checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
* checking use of PKG_*FLAGS in Makefiles ... OK
* checking use of SHLIB_OPENMP_*FLAGS in Makefiles ... NOTE
src/Makevars.win: SHLIB_OPENMP_CXXFLAGS is included in PKG_CXXFLAGS but not in PKG_LIBS
Use of these macros is discussed in sect 1.2.1.1 of Writing R
Extensions. The macros for different languages may differ so the
matching macro must be used in PKG_CXXFLAGS (etc) and match that used
in PKG_LIBS (except for Fortran: see the manual).
* checking pragmas in C/C++ headers and code ... OK
* checking compilation flags used ... NOTE
Compilation used the following non-portable flag(s):
-Werror=format-security
* checking compiled code ... NOTE
Note: information on .o files is not available
File /home/pkgbuild/packagebuilder/workers/jobs/4079/R-libs/HiSpaR/libs/HiSpaR.so:
Found _ZSt4cerr, possibly from std::cerr (C++)
Found _ZSt4cout, possibly from std::cout (C++)
Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor use Fortran I/O
nor system RNGs nor [v]sprintf. The detected symbols are linked into
the code but might come from libraries and not actually be called.
See Writing portable packages in the Writing R Extensions manual.
* checking files in vignettes ... OK
* checking examples ... [9s/9s] OK
* checking for unstated dependencies in tests ... OK
* checking tests ...
Running testthat.R [7s/7s]
[8s/8s] 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 ... [3s/3s] OK
* DONE
Status: 4 NOTEs
See
/home/pkgbuild/packagebuilder/workers/jobs/4079/b2c79798ff83a41ce24f2d5d015d463dc9db03ec/HiSpaR.Rcheck/00check.log
for details.
===============================
BiocCheck('HiSpaR_0.99.1.tar.gz')
===============================
Installing HiSpaR
Package installed successfully
HiSpaR session metadata
sourceDir: /tmp/Rtmp8iigpJ/file1c9ee71e36af7d/HiSpaR
BiocVersion: 3.23
Package: HiSpaR
PackageVersion: 0.99.1
BiocCheckDir: /home/pkgbuild/packagebuilder/workers/jobs/4079/b2c79798ff83a41ce24f2d5d015d463dc9db03ec/HiSpaR.BiocCheck
BiocCheckVersion: 1.47.18
sourceDir: /tmp/Rtmp8iigpJ/file1c9ee71e36af7d/HiSpaR
installDir: /tmp/Rtmp8iigpJ/file1c9ee7684a94f4
isTarBall: TRUE
platform: unix
Running BiocCheck on HiSpaR
* 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...
i NOTE: Update R version dependency from 4.5.0 to 4.6.0
* 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 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...
i 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...
i Bioconductor dependencies found in Imports & Depends (20%).
* Checking for pinned package versions in DESCRIPTION...
* Checking for 'fnd' role in Authors@R...
i NOTE: No 'fnd' role found in Authors@R. If the work is supported by a grant,
consider adding the 'fnd' role to the list of authors.
* Checking NAMESPACE...
* Checking .Rbuildignore...
* Checking for stray BiocCheck output folders...
* Checking vignette directory...
i NOTE: Vignette(s) found with missing chunk labels
Found in files:
getting-started.Rmd
* Checking whether vignette is built with 'R CMD build'...
* Checking package installation calls in R code...
* Checking for library/require of HiSpaR...
* Checking coding practice...
* Checking parsed R code in R directory, examples, vignettes...
* Checking function lengths...
i NOTE: The recommended function length is 50 lines or less. There is 1
function greater than 50 lines.
The longest 5 functions are:
hispa_analyze() (R/hispa_functions.R): 163 lines
* Checking man page documentation...
Consider using the `HiContacts` package to perform advanced genomic operations
on `HiCExperiment` objects.
Read "Orchestrating Hi-C analysis with Bioconductor" online book to learn more:
https://js2264.github.io/OHCA/
i NOTE: Usage of dontrun / donttest tags found in man page examples. 67% of man
pages use at least one of these tags.
Found in files:
hispa_analyze.Rd
su1_contact_mat.Rd
* Checking package NEWS...
* Checking unit tests...
* Checking skip_on_bioc() in tests...
* Checking formatting of DESCRIPTION, NAMESPACE, man pages, R source, and
vignette source...
i NOTE: Consider shorter lines; 56 lines (10%) are > 80 characters long.
First few lines:
R/data.R#L4 #' Hi-C contact matrix of Human Chromoso ...
...
vignettes/getting-started.Rmd#L145 marker = list(size = 5, color = ~seq_l ...
i NOTE: Consider multiples of 4 spaces for line indents; 107 lines (19%) are
not.
First few lines:
R/hispa_functions.R#L120 # Handle both matrix and HiCExperiment ...
...
vignettes/getting-started.Rmd#L174 ) ...
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.47.18 results
0 ERRORS | 0 WARNINGS | i 8 NOTES
i See the HiSpaR.BiocCheck folder and run
browseVignettes(package = 'BiocCheck')
for details.