Hi Andreas, $ rmadison r-base r-base | 2.15.1-4 | oldstable | source, all r-base | 3.1.1-1 | stable-kfreebsd | source, all r-base | 3.1.1-1+deb8u1 | stable | source, all r-base | 3.3.3-1~bpo8+1 | jessie-backports | source, all r-base | 3.3.3-1 | testing | source, all r-base | 3.4.0-1 | unstable | source, all
At least for bioconductor packages, we have a problem: for some at the core of the dependency chain, when compiled against R 3.1.1 in Jessie they will not work with R 3.3.3 backported for Jessie. I have not tested whether the converse is true or false. For CRAN packages the situation is easier, although a few of them might be affected (most likely when declaring a S4 method for the c() generic). I am trying to set up a debci system at home to mass-run autopkg tests in jessie-backports, but could not find time to complete this task. Anyway for the sake of consistency I think that we/you need to make a general decision (unless it is already covered by the contribution policy of Debian backports, but I could not find anything): do we support the use of newer CRAN / BioC packages on Jessie's 3.3.1, or do we support their use together with the backported R 3.3.3, in which case we must force them to depend on it. Have a nice day Charles -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan
