Hi Dirk, On Thu, 18 Apr 2019 05:38:34 -0500 Dirk Eddelbuettel <[email protected]> wrote: > I have argues before that these need to be reassigned as these packages > generally build at CRAN -- and test in a wider (OS-wise speaking) setting > than we have. See eg > https://cloud.r-project.org/web/checks/check_results_permute.html > which gets OK on each of the 12 platforms -- across multiple releases and > OSs.
That check is for a version of r-cran-permute not yet in Debian, for reasons explained by Andreas. I can't keep track of all ecosystems, so I am just responding like I do to *all* autopkgtest regressions. We're in a freeze to release a new Debian version. Fixes need to go through unstable as much as possible, so new uploads there that don't target buster can be harmful. > I have in the past tried to argue and explain how our system of autopkgtest > was in my eyes not the right approach _as it ignores the system R itself has > and uses_ and these repeated bug reports are just repurcussions of it. I am > tired of rehashing it as it goes nowhere. Maybe r is different in Debian than other packages and/or ecosystems, maybe not. But I'll stop helping you with autopkgtest regressions in the r part of the archive from now on. > They must be fixed in the respective packages. R releases once a year with 3 > to 4 minor releases, and I tend to upload thoses. R 3.6.0 comes out April 26. > I plan to upload it. The Debian release can use the testing version as in the > past. Please avoid this next release cycle. Uploading new upstream releases during the freeze isn't making releasing Debian easier and quite often is harmful. Paul
signature.asc
Description: OpenPGP digital signature
