##############################################################################
##############################################################################
###
### Running command:
###
###   /home/biocbuild/bbs-3.19-bioc/R/bin/Rscript -e "BiocCheck::BiocCheck('dir.expiry_1.13.0.tar.gz')"
###
##############################################################################
##############################################################################


─ BiocCheckVersion: 1.41.3
─ BiocVersion: 3.20
─ Package: dir.expiry
─ PackageVersion: 1.13.0
─ sourceDir: /tmp/RtmpwlDJnk/file3aedd11f7cce53/dir.expiry
─ installDir: /tmp/RtmpwlDJnk/file3aedd1284caad
─ BiocCheckDir: /home/biocbuild/bbs-3.19-bioc-testing/meat/dir.expiry.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 version number validity...
* 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...
    * NOTE: Provide 'URL', 'BugReports' field(s) in DESCRIPTION
* Checking for Bioconductor software dependencies...
    * NOTE: No Bioconductor dependencies detected. Note that some
      infrastructure packages may not have Bioconductor dependencies.
      For more information, reach out to the Bioconductor community
      and/or consider a CRAN submission.
* Checking for pinned package versions in DESCRIPTION...
* Checking .Rbuildignore...
* Checking for stray BiocCheck output folders...
* Checking vignette directory...
* Checking package installation calls in R code...
* Checking for library/require of dir.expiry...
* Checking coding practice...
* Checking parsed R code in R directory, examples, vignettes...
* Checking function lengths...
* Checking man page documentation...
* Checking package NEWS...
    * NOTE: Consider adding a NEWS file, so your package news will be
      included in Bioconductor release announcements.
* 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; 82 lines (16%) are > 80 characters
      long.
    * NOTE: Consider multiples of 4 spaces for line indents; 1 lines
      (0%) 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 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.
    * ERROR: Add package to Watched Tags in your Support Site profile;
      visit https://support.bioconductor.org/accounts/edit/profile

─ BiocCheck results ──
1 ERRORS | 0 WARNINGS | 7 NOTES

See the dir.expiry.BiocCheck folder and run
    browseVignettes(package = 'BiocCheck')
for details.