===============================
R CMD BUILD
===============================
* checking for file ‘gutenTAG/DESCRIPTION’ ... OK
* preparing ‘gutenTAG’:
* checking DESCRIPTION meta-information ... OK
* installing the package (it is needed 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 ‘gutenTAG_0.99.15.tar.gz’
===============================
BiocCheckGitClone('gutenTAG')
===============================
── Running Git clone checks on gutenTAG ────────────────────────────────────────
* Checking valid files...
* Checking for inst/doc folders...
* Checking DESCRIPTION readability...
* Checking for valid use of maintainer fields...
===============================
R CMD CHECK
===============================
* using log directory ‘/home/pkgbuild/packagebuilder/workers/jobs/4210/76fa448544d8e0a05d15da9268413fba74edeba6/gutenTAG.Rcheck’
* using R version 4.6.1 (2026-06-24)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
gcc (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0
GNU Fortran (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0
* running under: Ubuntu 24.04.4 LTS
* using session charset: UTF-8
* current time: 2026-07-17 15:47:46 UTC
* using option ‘--no-vignettes’
* checking for file ‘gutenTAG/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘gutenTAG’ 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 ... NOTE
Found the following hidden files and directories:
.github
These were most likely included in error. See section ‘Package
structure’ in the ‘Writing R Extensions’ manual.
* checking for portable file names ... OK
* checking for sufficient/correct file permissions ... OK
* checking whether package ‘gutenTAG’ 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 ... [19s/19s] OK
* checking whether the package can be loaded with stated dependencies ... [19s/19s] OK
* checking whether the package can be unloaded cleanly ... [19s/19s] OK
* checking whether the namespace can be loaded with stated dependencies ... [19s/19s] OK
* checking whether the namespace can be unloaded cleanly ... [19s/19s] OK
* checking loading without being on the library search path ... [19s/19s] 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 ... [60s/60s] NOTE
.finaliseCorrespondence: no visible binding for global variable
‘expected_mz_location’
.knn_weight_matrix: no visible global function definition for ‘dist’
imageChannel: no visible binding for global variable ‘y’
Undefined global functions or variables:
dist expected_mz_location y
Consider adding
importFrom("stats", "dist")
to your NAMESPACE file.
* 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 ... [118s/111s] OK
Examples with CPU (user + system) or elapsed time > 5s
user system elapsed
asAnnData 11.269 2.954 11.731
* checking for unstated dependencies in ‘tests’ ... OK
* checking tests ...
Running ‘testthat.R’ [96s/85s]
[96s/86s] 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 ... [4s/3s] OK
* DONE
Status: 2 NOTEs
See
‘/home/pkgbuild/packagebuilder/workers/jobs/4210/76fa448544d8e0a05d15da9268413fba74edeba6/gutenTAG.Rcheck/00check.log’
for details.
===============================
BiocCheck('gutenTAG_0.99.15.tar.gz')
===============================
── Installing gutenTAG ─────────────────────────────────────────────────────────
✔ Package installed successfully
── gutenTAG session metadata ───────────────────────────────────────────────────
→ sourceDir: /tmp/RtmpwQfvs4/file12af0827a5e87d/gutenTAG
→ BiocVersion: 3.23
→ Package: gutenTAG
→ PackageVersion: 0.99.15
→ BiocCheckDir: /home/pkgbuild/packagebuilder/workers/jobs/4210/76fa448544d8e0a05d15da9268413fba74edeba6/gutenTAG.BiocCheck
→ BiocCheckVersion: 1.49.29
→ sourceDir: /tmp/RtmpwQfvs4/file12af0827a5e87d/gutenTAG
→ installDir: /tmp/RtmpwQfvs4/file12af085b3567d6/lib
→ isTarBall: TRUE
→ platform: unix
── Running BiocCheck on gutenTAG ───────────────────────────────────────────────
* 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.3.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...
i NOTE: Consider adding these automatically suggested biocViews: Lipidomics,
Classification, Regression, ImmunoOncology
i Search 'biocViews' at https://contributions.bioconductor.org
* Checking build system compatibility...
* Checking if 'Package:' field matches directory / tarball...
* Checking for Version: field...
* Checking DESCRIPTION readability...
* Checking validity of DESCRIPTION fields...
* Checking License: for restrictive use...
* Checking for recommended DESCRIPTION fields...
i NOTE: Provide 'URL', 'BugReports' field(s) in DESCRIPTION
* Checking for whitespace in DESCRIPTION field names...
* Checking for proper Description: field...
* Checking for Bioconductor software dependencies...
i Bioconductor dependencies found in Imports & Depends (35%).
* Checking for pinned package versions in DESCRIPTION...
* Checking for 'fnd' role in Authors@R...
i 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 CITATION...
i (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()'.
* Checking 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 gutenTAG...
* Checking coding practice...
i NOTE: Avoid using '=' for assignment and use '<-' instead
Found in files:
• R/utils.R (line 103, column 20)
• R/utils.R (line 105, column 12)
* Checking parsed R code in R directory, examples, vignettes...
i NOTE: Avoid 'suppressWarnings'/'*Messages' if possible (found 6 times)
• suppressWarnings() in R/plotQC.R (line 158, column 8)
• ...
• suppressWarnings() in R/plotQC.R (line 1106, column 8)
* Checking function lengths...
i NOTE: The recommended function length is 50 lines or less. There are 9
functions greater than 50 lines.
The longest 5 functions are:
• plotMetapeaks() (R/plotQC.R): 142 lines
• ...
• plotMeanVarianceResiduals() (R/plotQC.R): 78 lines
* 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...
i NOTE: Consider shorter lines; 200 lines (6%) are > 80 characters long.
First few lines:
• R/asAnnData.R#L11 #' path <- system.file("extdata/Example_ ...
• ...
• vignettes/gutenTAG.Rmd#L423 developing the initial architecture of t ...
i NOTE: Consider multiples of 4 spaces for line indents; 1078 lines (30%) are
not.
First few lines:
• R/asAnnData.R#L23 # extract data from object ...
• ...
• vignettes/gutenTAG.Rmd#L380 interpolate = FALSE) ...
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 'gutentag' is already in your 'Watched Tags' on the Support Site.
── BiocCheck v1.49.29 results ──────────────────────────────────────────────────
✖ 0 ERRORS | ⚠ 0 WARNINGS | i 8 NOTES
i See the gutenTAG.BiocCheck folder and run
`browseVignettes(package = 'BiocCheck')`
for details.