Am Montag, 18. September 2017, 10:39:02 CEST schrieb Dirk Eddelbuettel: > On 18 September 2017 at 22:41, Charles Plessy wrote: > | Hello everybody, > | > | I just wanted to relay the information that some R packages will need a > | rebuild after the next upgrade of R. (see the email forwarded below.) > > Common knowledge. I referenced it half-a-dozen times in the damned thread > about the binNMUs.
This (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868558) had escaped my attention, maybe others on this list had not seen it either? > The ALTREP branch for R was announced as coming earlier > in the year, and is now in the r-devel master branch (ie R upstream). > > We will switch to r-api-4 then which will finally break the effing block For what it's worth (not much, my github commit history is not too impressive), I really have a lot of respect for this effort of the release team to avoid known breakage. > posed upon by the release team in response to the 'R 3.4.0 has a change' bug > report by Johannes. The R 3.4.0 you uploaded to unstable broke packages from existing installations (unstable). If you now say that I reported a change, not a bug, I could be tempted to find this offensive. But I do prefer to thank you and Andreas for fixing the issue. As a backport maintainer for CRAN, I would have preferred an upload to experimental (if you wanted to upload right away), and then an ABI change or a list of Breaks before the upload to unstable. But now I am really glad that it seems we will have everything sorted out in April! It would be cool if we then could continue establishing r-base in debian-backports. Cheers, Johannes