;Dalgleish, James (NIH/NCI) [F]"
mailto:james.dalgle...@nih.gov>>,
"r-package-devel@r-project.org<mailto:r-package-devel@r-project.org>"
mailto:r-package-devel@r-project.org>>
Subject: Re: [R-pkg-devel] Old version of rtracklayer on a single check server
I stand co
ct: Re: [R-pkg-devel] Old version of rtracklayer on a single check server
I stand corrected about the R-devel version (and now R 4.1.0) on CRAN.
However, isn't it the case that it will never be solved for R 4.0.0 (to become
R-oldrel on CRAN) and CRAN will keep reporting an error on MS Win
I stand corrected about the R-devel version (and now R 4.1.0) on CRAN.
However, isn't it the case that it will never be solved for R 4.0.0 (to
become R-oldrel on CRAN) and CRAN will keep reporting an error on MS
Windows there because
https://bioconductor.org/packages/3.12/bioc/html/rtracklayer.htm
That’s not correct Henrik.
CRAN follows CRAN rules for installing packages, so uses
tools:::BioC_version_for_R_version(). For R-devel we have
> R.version.string
[1] "R Under development (unstable) (2021-05-18 r80323)"
> tools:::.BioC_version_associated_with_R_version()
[1] '3.13'
For this versi
It's a problem with Bioconductor and a broken release history of
'rtracklayer' on MS Windows (e.g.
https://bioconductor.org/packages/3.12/bioc/html/rtracklayer.html)
plus how each Bioconductor version is tied to a specific R version.
In other words, even if they fix it in Bioconductor 3.13 (for R
4
To any who might have an idea:
I've been reading several posts in the digest about dependency version issues
on the check servers and I'm having my own issue, which I can't solve because I
can't upgrade the check server's package version:
* installing *source* package 'CNVScope' ...
** using sta
