===============================
R CMD BUILD
===============================
* checking for file ‘mnmer/DESCRIPTION’ ... OK
* preparing ‘mnmer’:
* checking DESCRIPTION meta-information ... OK
* cleaning src
* installing the package to build vignettes
* creating vignettes ... OK
Warning: ‘inst/doc’ files
‘vignette.Rmd’, ‘vignette.pdf’, ‘vignette.R’
ignored as vignettes have been rebuilt.
Run R CMD build with --no-build-vignettes to prevent rebuilding.
* cleaning src
* checking for LF line-endings in source and make files and shell scripts
* checking for empty or unneeded directories
* building ‘mnmer_0.99.0.tar.gz’
===============================
BiocCheckGitClone('mnmer')
===============================
─ BiocCheckVersion: 1.35.4
─ BiocVersion: 3.17
─ Package: mnmer
─ PackageVersion: 0.99.0
─ sourceDir: /home/pkgbuild/packagebuilder/workers/jobs/2843/mnmer_20221201141745/mnmer
─ platform: unix
─ isTarBall: FALSE
* Checking valid files...
* ERROR: System files found that should not be Git tracked.
src/mnmer.so
src/mnmercpp.o
* Checking for stray BiocCheck output folders...
* Checking DESCRIPTION...
* Checking if DESCRIPTION is well formatted...
* Checking for valid maintainer...
* Checking CITATION...
* Checking that provided CITATION file is correctly formatted...
* NOTE: CITATION file might be not correctly formatted
─ BiocCheck results ──
1 ERRORS | 0 WARNINGS | 1 NOTES
For more details, run
browseVignettes(package = 'BiocCheck')
===============================
R CMD CHECK
===============================
* using log directory ‘/home/pkgbuild/packagebuilder/workers/jobs/2843/mnmer_20221201141745/mnmer.Rcheck’
* using R Under development (unstable) (2022-10-25 r83175)
* using platform: x86_64-pc-linux-gnu (64-bit)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘mnmer/DESCRIPTION’ ... OK
* this is package ‘mnmer’ 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 whether package ‘mnmer’ 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 ... NOTE
File
LICENSE
is not mentioned in the DESCRIPTION file.
* 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 ... [3s/3s] OK
* checking whether the package can be loaded with stated dependencies ... [2s/2s] OK
* checking whether the package can be unloaded cleanly ... [2s/2s] OK
* checking whether the namespace can be loaded with stated dependencies ... [2s/2s] OK
* checking whether the namespace can be unloaded cleanly ... [2s/2s] OK
* checking loading without being on the library search path ... [3s/3s] 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 ... [8s/8s] 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 ... WARNING
Undocumented arguments in documentation object 'mnmer'
‘pni’
Functions with \usage entries need to have the appropriate \alias
entries, and all their arguments documented.
The \usage entries must correspond to syntactically valid R code.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking line endings in C/C++/Fortran sources/headers ... OK
* checking pragmas in C/C++ headers and code ... OK
* checking compilation flags used ... OK
* checking compiled code ... NOTE
Note: information on .o files is not available
File ‘mnmer/libs/mnmer.so’:
Found no calls to: ‘R_registerRoutines’, ‘R_useDynamicSymbols’
It is good practice to register native routines and to disable symbol
search.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
* checking installed files from ‘inst/doc’ ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... [3s/3s] OK
* checking for unstated dependencies in ‘tests’ ... OK
* checking tests ...
Running ‘testthat.R’ [3s/3s]
[3s/3s] 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: 1 WARNING, 2 NOTEs
See
‘/home/pkgbuild/packagebuilder/workers/jobs/2843/mnmer_20221201141745/mnmer.Rcheck/00check.log’
for details.
===============================
BiocCheck('mnmer_0.99.0.tar.gz')
===============================
─ BiocCheckVersion: 1.35.4
─ BiocVersion: 3.17
─ Package: mnmer
─ PackageVersion: 0.99.0
─ sourceDir: /tmp/RtmpCZXbEC/file2fc8077984cc71/mnmer
─ installDir: /tmp/RtmpCZXbEC/file2fc8073baf77dd
─ BiocCheckDir: /home/pkgbuild/packagebuilder/workers/jobs/2843/mnmer_20221201141745/mnmer.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...
* NOTE: Update R version dependency from 4.2.0 to 4.3.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...
* NOTE: Consider adding these automatically suggested biocViews:
Sequencing, Alignment, SequenceMatching, DataImport
Search 'biocViews' at https://contributions.bioconductor.org
* 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 pinned package versions...
* 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 mnmer...
* Checking coding practice...
* NOTE: Avoid 1:...; use seq_len() or seq_along()
* NOTE: Avoid 'cat' and 'print' outside of 'show' methods
* Checking parsed R code in R directory, examples, vignettes...
* Checking function lengths...
* Checking man page documentation...
* 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 shorter lines; 41 lines (14%) are > 80 characters
long.
* NOTE: Consider multiples of 4 spaces for line indents; 11 lines
(4%) 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...
* NOTE: Cannot determine whether maintainer is subscribed to the
Bioc-Devel mailing list (requires admin credentials). Subscribe
here: https://stat.ethz.ch/mailman/listinfo/bioc-devel
* Checking for support site registration...
Maintainer is registered at support site.
Package name is in support site watched tags.
─ BiocCheck results ──
0 ERRORS | 0 WARNINGS | 8 NOTES
See the mnmer.BiocCheck folder and run
browseVignettes(package = 'BiocCheck')
for details.