* using log directory ‘/srv/hornik/tmp/CRAN_pretest/birdnetR.Rcheck’
* using R Under development (unstable) (2025-04-08 r88126)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
    Debian clang version 19.1.7 (1+b1)
    Debian flang-new version 19.1.7 (1+b1)
* running under: Debian GNU/Linux trixie/sid
* using session charset: UTF-8
* checking for file ‘birdnetR/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘birdnetR’ version ‘0.2.3’
* package encoding: UTF-8
* checking CRAN incoming feasibility ... [4s/5s] NOTE
Maintainer: ‘Felix Günther <felix.guenther@informatik.tu-chemnitz.de>’

New submission

Possibly misspelled words in DESCRIPTION:
  Eibl (13:28)
  Kahl (13:5)
  Klinck (13:40)
  bioacoustic (11:13)
  pre (11:82)
* 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 executable files ... 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 ‘birdnetR’ can be installed ... [4s/4s] 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] NOTE
/tmp/check-CRAN-incoming-hornik/.virtualenvs/r-reticulate/bin/python: No module named pip
Warning in system2(python, args, stdout = TRUE) :
  running command ''/tmp/check-CRAN-incoming-hornik/.virtualenvs/r-reticulate/bin/python' -m pip freeze' had status 1

A namespace must be able to be loaded with just the base namespace
loaded: otherwise if the namespace gets loaded by a saved object, the
session will be unable to start.

Probably some imports need to be declared in the NAMESPACE file.
* 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] NOTE
/tmp/check-CRAN-incoming-hornik/.virtualenvs/r-reticulate/bin/python: No module named pip

It looks like this package (or a package it requires) has a startup
message which cannot be suppressed: see ?packageStartupMessage.
* checking use of S3 registration ... OK
* checking dependencies in R code ... NOTE
/tmp/check-CRAN-incoming-hornik/.virtualenvs/r-reticulate/bin/python: No module named pip
* checking S3 generic/method consistency ... WARNING
/tmp/check-CRAN-incoming-hornik/.virtualenvs/r-reticulate/bin/python: No module named pip
See section ‘Generic functions and methods’ in the ‘Writing R
Extensions’ manual.
* checking replacement functions ... WARNING
/tmp/check-CRAN-incoming-hornik/.virtualenvs/r-reticulate/bin/python: No module named pip
The argument of a replacement function which corresponds to the right
hand side must be named ‘value’.
* checking foreign function calls ... NOTE
/tmp/check-CRAN-incoming-hornik/.virtualenvs/r-reticulate/bin/python: No module named pip
See chapter ‘System and foreign language interfaces’ in the ‘Writing R
Extensions’ manual.
* checking R code for possible problems ... [6s/6s] NOTE
/tmp/check-CRAN-incoming-hornik/.virtualenvs/r-reticulate/bin/python: No module named pip
/tmp/check-CRAN-incoming-hornik/.virtualenvs/r-reticulate/bin/python: No module named pip

/tmp/check-CRAN-incoming-hornik/.virtualenvs/r-reticulate/bin/python: No module named pip
* 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 ... WARNING
/tmp/check-CRAN-incoming-hornik/.virtualenvs/r-reticulate/bin/python: No module named pip
All user-level objects in a package should have documentation entries.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
* checking for code/documentation mismatches ... WARNING
/tmp/check-CRAN-incoming-hornik/.virtualenvs/r-reticulate/bin/python: No module named pip
/tmp/check-CRAN-incoming-hornik/.virtualenvs/r-reticulate/bin/python: No module named pip
/tmp/check-CRAN-incoming-hornik/.virtualenvs/r-reticulate/bin/python: No module named pip
* checking Rd \usage sections ... NOTE
/tmp/check-CRAN-incoming-hornik/.virtualenvs/r-reticulate/bin/python: No module named pip
The \usage entries for S3 methods should use the \method markup and not
their full name.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* 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 ... [2s/2s] OK
  Running ‘testthat.R’ [2s/2s]
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes ... OK
* checking re-building of vignette outputs ... [2s/2s] OK
* checking PDF version of manual ... [3s/3s] OK
* checking HTML version of manual ... [0s/0s] OK
* checking for non-standard things in the check directory ... OK
* checking for detritus in the temp directory ... OK
* DONE
Status: 4 WARNINGs, 7 NOTEs