Re: Bug#955211: release.debian.org: Transition r-base for 4.0.0
On 25 May 2020 at 09:32, Graham Inggs wrote:
| Hi All
|
| Thanks everyone for doing all the hundreds of uploads that were needed
| for this combined transition.
| All rebuilds for r-api-bioc3.11 are done [1] and there's one
| outstanding FTBFS on a release architecture for r-api-4.0 [2].
The r-cran-treescape build bug has been there for several days, hopefully
someone can take care of this. Also, the package is archived at CRAN, we
could look into retiring it. And as the issue is on ppc64el, it may be long
double related: we now configure without long double support there after
consultation with upstream.
| Now there are a handful of autopkgtest regressions [3] that need to be
| resolved before migration can happen.
These issues are likely self-imposed: looking at r-cran-etm and r-cran-sp we
see clean sheets at CRAN for a variety of releases:
https://cloud.r-project.org/web/checks/check_results_etm.html # etm
https://cloud.r-project.org/web/checks/check_results_sp.html # sp
The simplest may be to fix the apparent false positive on the package side.
We're almost there. Nice work everyone!
| As usual, please avoid uploads unrelated to this transition, they
| would likely delay it and require supplementary work from the release
| managers.
Updates and package changes pile up. Eventually packages need to be built and
updated again.
Best, Dirk
| Regards
| Graham
|
|
| [1] https://release.debian.org/transitions/html/r-api-bioc-3.11.html
| [2] https://release.debian.org/transitions/html/r-api-4.0.html
| [3] https://qa.debian.org/excuses.php?package=r-base
--
http://dirk.eddelbuettel.com | @eddelbuettel | edd@debian.org
Reply to: