It is not obvious what it is that you are calling "R-patched", nor where there could be an entry for "3.6.2 patched". The prerelease/patched versions are snapshots of R-3-6-branch made at 00:20 so the current one will have been made before the release version run started at 09:00 this morning, and hence the nightly tarball will be of the release candidate. However it will not be called R-patched: lrwxr-xr-x 1 pd staff 29 Dec 12 00:20 R-latest.tar.gz -> R-rc_2019-12-06_r77555.tar.gz The current version in SVN differs only by the VERSION file. Its NEWS.Rd starts Peters-MacBook-Air:R pd$ more VERSION 3.6.2 Patched Peters-MacBook-Air:R pd$ more doc/NEWS.Rd % -*- coding: utf-8 -*- \newcommand{\Rlogo}{\if{html}{\figure{../../html/Rlogo.svg}{options: class="toplogo" alt="[R logo]"}}\if{latex}{\figure{Rlogo.pdf}{options: width=0.5in}}} \name{NEWS} \title{R News} \encoding{UTF-8} \section{\Rlogo CHANGES IN R 3.6.2}{ \subsection{NEW FEATURES}{ \itemize{ .... and any changes for 3.6.2 patched should go above the entries for 3.6.2. - pd> On 12 Dec 2019, at 16:34 , Avraham Adler <avraham.adler at gmail.com> wrote: > > Hi. > > Under R-news there is an entry for 3.6.2 patched regarding LAPACK. However, when uncompresding the current R-patched, it creates R-Rc directories. Is this a naming oversight or is the patched version actually the unadjusted release candidate? > > Thank you, > > Avi > > On Thu, Dec 12, 2019 at 4:58 AM Peter Dalgaard via R-devel <r-devel at r-project.org> wrote: > The build system rolled up R-3.6.2.tar.gz (codename "Dark and Stormy Night") this morning. > > The list below details the changes in this release. > > You can get the source code from > > http://cran.r-project.org/src/base/R-3/R-3.6.2.tar.gz > > or wait for it to be mirrored at a CRAN site nearer to you. > > Binaries for various platforms will appear in due course. > > > For the R Core Team, > > Peter Dalgaard > > These are the checksums (md5 and SHA-256) for the freshly created files, in case you wish > to check that they are uncorrupted: > > MD5 (AUTHORS) = b9c44f9f78cab3184ad9898bebc854b4 > MD5 (COPYING) = eb723b61539feef013de476e68b5c50a > MD5 (COPYING.LIB) = a6f89e2100d9b6cdffcea4f398e37343 > MD5 (FAQ) = 28a3942a7129877e9af1d5ea16202052 > MD5 (INSTALL) = 7893f754308ca31f1ccf62055090ad7b > MD5 (NEWS) = 45437b38c75e0248b527c00e6d42ee6a > MD5 (NEWS.0) = bfcd7c147251b5474d96848c6f57e5a8 > MD5 (NEWS.1) = eb78c4d053ec9c32b815cf0c2ebea801 > MD5 (NEWS.2) = 591dcf615162127f904e4e461f330ce9 > MD5 (R-latest.tar.gz) = 90d23d138cee26d275da14b58296e521 > MD5 (README) = f468f281c919665e276a1b691decbbe6 > MD5 (RESOURCES) = 529223fd3ffef95731d0a87353108435 > MD5 (THANKS) = bb45f89c01d509721c47fd41f147da60 > MD5 (VERSION-INFO.dcf) = 9c33701e25092aefc1d16beb5858f20f > MD5 (R-3/R-3.6.2.tar.gz) = 90d23d138cee26d275da14b58296e521 > > > 2cde824a7b18958e5f06b391c801c8288be0f84fa8934b7ddefef23c67e60c09 AUTHORS > e6d6a009505e345fe949e1310334fcb0747f28dae2856759de102ab66b722cb4 COPYING > 6095e9ffa777dd22839f7801aa845b31c9ed07f3d6bf8a26dc5d2dec8ccc0ef3 COPYING.LIB > 38219d9c6221ccfbf075ef03711b420a1aa8731f890c8f2337148b602a217c2d FAQ > f87461be6cbaecc4dce44ac58e5bd52364b0491ccdadaf846cb9b452e9550f31 INSTALL > 0ceb6fbab3e0e29bc374683fd5c2ccd0c9c62ce8eca2a394a4603775b3ef129c NEWS > 4e21b62f515b749f80997063fceab626d7258c7d650e81a662ba8e0640f12f62 NEWS.0 > 12b30c724117b1b2b11484673906a6dcd48a361f69fc420b36194f9218692d01 NEWS.1 > ca04f78ffe54afa326fe3ed40e7e1411aca0000ed2fa5ead97ddf51c6aa5b7bc NEWS.2 > bd65a45cddfb88f37370fbcee4ac8dd3f1aebeebe47c2f968fd9770ba2bbc954 R-latest.tar.gz > 2fdd3e90f23f32692d4b3a0c0452f2c219a10882033d1774f8cadf25886c3ddc README > 408737572ecc6e1135fdb2cf7a9dbb1a6cb27967c757f1771b8c39d1fd2f1ab9 RESOURCES > 2a8dca916cd92229ef9e328f3610ca204809c262823b860252b42072dac2473a THANKS > 40cc7cea5f0e67cf8f2f7b25a534ae6bc53f38eae2ab2c2649a952ed37f0654a VERSION-INFO.dcf > bd65a45cddfb88f37370fbcee4ac8dd3f1aebeebe47c2f968fd9770ba2bbc954 R-3/R-3.6.2.tar.gz > > This is the relevant part of the NEWS file > > CHANGES IN R 3.6.2: > > NEW FEATURES: > > * runmed(x, *) gains a new option na.action determining _how_ to > handle NaN or NA in x. > > * dotchart() gains new options ann, xaxt, frame.plot and log. > > INSTALLATION on a UNIX-ALIKE: > > * Detection of the C stack direction has been moved from run-time > to configure: this is safer with LTO builds and allows the > detection to be overridden - see file config.site. > > * Source-code changes enable installation on platforms using gcc > -fno-common (the expected default for gcc 10.x). > > C-LEVEL FACILITIES: > > * installTrChar (which is nowadays is wrapped by installChar) is > defined in Rinternals.h. (Neither are part of the API.) > > PACKAGE INSTALLATION: > > * Header Rconfig.h contains the value of FC_LEN_T deduced at > installation which is used by the prototypes in headers > R_ext/BLAS.h and R_ext/Lapack.h but to avoid extensive breakage > this is only exposed when USE_FC_LEN_T is defined. > > If a package's C/C++ calls to BLAS/LAPACK allow for the 'hidden' > arguments used by most Fortran compilers to pass the lengths of > Fortran character arguments, define USE_FC_LEN_T and include > Rconfig.h (possibly _via_ R.h) before including R_ext/BLAS.h or > R_ext/Lapack.h. > > * A package with Fortran source code and perhaps C (but not C++) > sources can request for its shared object/DLL to be linked by the > Fortran compiler by including a line USE_FC_TO_LINK= in > src/Makevars[.win] and using $(SHLIB_OPENMP_FFLAGS) as part of > PKG_LIBS. > > The known reason for doing so is a package which uses Fortran > (only) OpenMP on a platform where the Fortran OpenMP runtime is > incompatible with the C one (e.g. gfortran 9.x with clang). > > UTILITIES: > > * R CMD check has a new option to mitigate checks leaving > files/directories in /tmp. See the 'R Internals' manual - this > is part of --as-cran. > > Windows: > > * The default standard for C++ in package installation is C++11 (as > it has been on other platforms where available since R 3.6.0: the > default toolchain on Windows was defaulting to C++98). > > DEPRECATED AND DEFUNCT: > > * Support for specifying C++98 in package installation is > deprecated. > > * Support in R CMD config for F77, FCPIFCPLAGS, CPP, CXXCPP and > CXX98 and similar is deprecated. (CPP is found from the system > make and may well not be set.) > > Use $CC -E and $CXX -E instead of CPP and CXXCPP. > > BUG FIXES: > > * runmed(x, *) when x contains missing values now works > consistently for both algorithm="Stuetzle" and "Turlach", and no > longer segfaults for "Turlach", as reported by Hilmar Berger. > > * apply(diag(3), 2:3, mean) now gives a helpful error message. > > * dgamma(x, shape, log=TRUE) now longer overflows to Inf for shape > < 1 and very small x, fixing PR#17577, reported by Jonathan > Rougier. > > * Buffer overflow in building error messages fixed. Reported by > Benjamin Tremblay. > > * options(str = .) is correctly initialized at package utils load > time, now. A consequence is that str() in scripts now is more > consistent to interactive use, e.g., when displaying function(**) > argument lists. > > * as.numeric(<call>) now gives correct error message. > > * Printing ls.str() no longer wrongly shows "<missing>" in rare > cases. > > * Auto-printing S4 objects no longer duplicates the object, for > faster speed and reduced memory consumption. Reported by Aaron > Lun. > > * pchisq(<LRG>, <LRG>, ncp=100) no longer takes practically forever > in some cases. Hence ditto for corresponding qchisq() calls. > > * x %% L for finite x no longer returns NaN when L is infinite, nor > suffers from cancellation for large finite L, thanks to Long Qu's > PR#17611. > > Analogously, x %/% L and L %/% x suffer less from cancellation > and return values corresponding to limits for large L. > > * grepl(NA, *) now returns logical as documented. > > * options(warn=1e11) is an error now, instead of later leading to C > stack overflow because of infinite recursion. > > * R_tryCatch no longer transfers control for all conditions. > Reported and patch provided by Lionel Henry in PR#17617. > > * format(object.size(.), digits=NULL) now works, fixing PR#17628 > reported by Jonathan Carroll. > > * get_all_vars(f, d) now also works for cases, e.g. where d > contains a matrix. Reported by Simon Wood in 2009 and patch > provided by Ben Bolker in PR#13624. > > Additionally, it now also works when some variables are data > frames, fixing PR#14905, reported by Patrick Breheny. > > * barplot() could get spacings wrong if there were exactly two bars > PR#15522. Patch by Michael Chirico. > > * power.t.test() works in more cases when returning values of n > smaller than 2. > > * dotchart(*, pch=., groups=.) now works better. Reported by > Robert and confirmed by Nic Rochette in PR#16953. > > * canCoerce(obj, cl) no longer assumes length(class(obj)) == 1. > > * plot.formula(*, subset = *) now also works in a boundary case > reported by Robert Schlicht (TU Dresden). > > * readBin() and writeBin() of a rawConnection() now also work in > large cases, thanks to a report and proposal by Taeke Harkema in > PR#17665. > > -- > Peter Dalgaard, Professor, > Center for Statistics, Copenhagen Business School > Solbjerg Plads 3, 2000 Frederiksberg, Denmark > Phone: (+45)38153501 > Office: A 4.23 > Email: pd.mes at cbs.dk Priv: PDalgd at gmail.com > > ______________________________________________ > R-devel at r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel > -- > Sent from Gmail Mobile-- Peter Dalgaard, Professor, Center for Statistics, Copenhagen Business School Solbjerg Plads 3, 2000 Frederiksberg, Denmark Phone: (+45)38153501 Office: A 4.23 Email: pd.mes at cbs.dk Priv: PDalgd at gmail.com
Thank you. I apologize for not providing the link. [1] Under the news for R-revel there is a single entry for R 3.6.2-patched. The file I downloaded was [2] with a date of 2019-12-12 01:50. Is it safe to say that 3.6.2 has the LAPACK upgrades and fixes? Apologies in advance if iOS links the URL below. I cannot access gmail desktop from behind my corporate firewall. Thank you again, Avi [1] https://cran.r-project.org/doc/manuals/r-devel/NEWS.html [2] https://stat.ethz.ch/R/daily/R-patched.tar.gz On Thu, Dec 12, 2019 at 11:10 AM Peter Dalgaard <pd.mes at cbs.dk> wrote:> It is not obvious what it is that you are calling "R-patched", nor where > there could be an entry for "3.6.2 patched". > > The prerelease/patched versions are snapshots of R-3-6-branch made at > 00:20 so the current one will have been made before the release version run > started at 09:00 this morning, and hence the nightly tarball will be of the > release candidate. However it will not be called R-patched: > > lrwxr-xr-x 1 pd staff 29 Dec 12 00:20 R-latest.tar.gz -> > R-rc_2019-12-06_r77555.tar.gz > > The current version in SVN differs only by the VERSION file. Its NEWS.Rd > starts > > Peters-MacBook-Air:R pd$ more VERSION > 3.6.2 Patched > Peters-MacBook-Air:R pd$ more doc/NEWS.Rd > % -*- coding: utf-8 -*- > \newcommand{\Rlogo}{\if{html}{\figure{../../html/Rlogo.svg}{options: > class="toplogo" alt="[R logo]"}}\if{latex}{\figure{Rlogo.pdf}{options: > width=0.5in}}} > > \name{NEWS} > \title{R News} > \encoding{UTF-8} > > \section{\Rlogo CHANGES IN R 3.6.2}{ > > \subsection{NEW FEATURES}{ > \itemize{ > .... > > and any changes for 3.6.2 patched should go above the entries for 3.6.2. > > - pd > > > > On 12 Dec 2019, at 16:34 , Avraham Adler <avraham.adler at gmail.com> > wrote: > > > > Hi. > > > > Under R-news there is an entry for 3.6.2 patched regarding LAPACK. > However, when uncompresding the current R-patched, it creates R-Rc > directories. Is this a naming oversight or is the patched version actually > the unadjusted release candidate? > > > > Thank you, > > > > Avi > > > > On Thu, Dec 12, 2019 at 4:58 AM Peter Dalgaard via R-devel < > r-devel at r-project.org> wrote: > > The build system rolled up R-3.6.2.tar.gz (codename "Dark and Stormy > Night") this morning. > > > > The list below details the changes in this release. > > > > You can get the source code from > > > > http://cran.r-project.org/src/base/R-3/R-3.6.2.tar.gz > > > > or wait for it to be mirrored at a CRAN site nearer to you. > > > > Binaries for various platforms will appear in due course. > > > > > > For the R Core Team, > > > > Peter Dalgaard > > > > These are the checksums (md5 and SHA-256) for the freshly created files, > in case you wish > > to check that they are uncorrupted: > > > > MD5 (AUTHORS) = b9c44f9f78cab3184ad9898bebc854b4 > > MD5 (COPYING) = eb723b61539feef013de476e68b5c50a > > MD5 (COPYING.LIB) = a6f89e2100d9b6cdffcea4f398e37343 > > MD5 (FAQ) = 28a3942a7129877e9af1d5ea16202052 > > MD5 (INSTALL) = 7893f754308ca31f1ccf62055090ad7b > > MD5 (NEWS) = 45437b38c75e0248b527c00e6d42ee6a > > MD5 (NEWS.0) = bfcd7c147251b5474d96848c6f57e5a8 > > MD5 (NEWS.1) = eb78c4d053ec9c32b815cf0c2ebea801 > > MD5 (NEWS.2) = 591dcf615162127f904e4e461f330ce9 > > MD5 (R-latest.tar.gz) = 90d23d138cee26d275da14b58296e521 > > MD5 (README) = f468f281c919665e276a1b691decbbe6 > > MD5 (RESOURCES) = 529223fd3ffef95731d0a87353108435 > > MD5 (THANKS) = bb45f89c01d509721c47fd41f147da60 > > MD5 (VERSION-INFO.dcf) = 9c33701e25092aefc1d16beb5858f20f > > MD5 (R-3/R-3.6.2.tar.gz) = 90d23d138cee26d275da14b58296e521 > > > > > > 2cde824a7b18958e5f06b391c801c8288be0f84fa8934b7ddefef23c67e60c09 AUTHORS > > e6d6a009505e345fe949e1310334fcb0747f28dae2856759de102ab66b722cb4 COPYING > > 6095e9ffa777dd22839f7801aa845b31c9ed07f3d6bf8a26dc5d2dec8ccc0ef3 > COPYING.LIB > > 38219d9c6221ccfbf075ef03711b420a1aa8731f890c8f2337148b602a217c2d FAQ > > f87461be6cbaecc4dce44ac58e5bd52364b0491ccdadaf846cb9b452e9550f31 INSTALL > > 0ceb6fbab3e0e29bc374683fd5c2ccd0c9c62ce8eca2a394a4603775b3ef129c NEWS > > 4e21b62f515b749f80997063fceab626d7258c7d650e81a662ba8e0640f12f62 NEWS.0 > > 12b30c724117b1b2b11484673906a6dcd48a361f69fc420b36194f9218692d01 NEWS.1 > > ca04f78ffe54afa326fe3ed40e7e1411aca0000ed2fa5ead97ddf51c6aa5b7bc NEWS.2 > > bd65a45cddfb88f37370fbcee4ac8dd3f1aebeebe47c2f968fd9770ba2bbc954 > R-latest.tar.gz > > 2fdd3e90f23f32692d4b3a0c0452f2c219a10882033d1774f8cadf25886c3ddc README > > 408737572ecc6e1135fdb2cf7a9dbb1a6cb27967c757f1771b8c39d1fd2f1ab9 > RESOURCES > > 2a8dca916cd92229ef9e328f3610ca204809c262823b860252b42072dac2473a THANKS > > 40cc7cea5f0e67cf8f2f7b25a534ae6bc53f38eae2ab2c2649a952ed37f0654a > VERSION-INFO.dcf > > bd65a45cddfb88f37370fbcee4ac8dd3f1aebeebe47c2f968fd9770ba2bbc954 > R-3/R-3.6.2.tar.gz > > > > This is the relevant part of the NEWS file > > > > CHANGES IN R 3.6.2: > > > > NEW FEATURES: > > > > * runmed(x, *) gains a new option na.action determining _how_ to > > handle NaN or NA in x. > > > > * dotchart() gains new options ann, xaxt, frame.plot and log. > > > > INSTALLATION on a UNIX-ALIKE: > > > > * Detection of the C stack direction has been moved from run-time > > to configure: this is safer with LTO builds and allows the > > detection to be overridden - see file config.site. > > > > * Source-code changes enable installation on platforms using gcc > > -fno-common (the expected default for gcc 10.x). > > > > C-LEVEL FACILITIES: > > > > * installTrChar (which is nowadays is wrapped by installChar) is > > defined in Rinternals.h. (Neither are part of the API.) > > > > PACKAGE INSTALLATION: > > > > * Header Rconfig.h contains the value of FC_LEN_T deduced at > > installation which is used by the prototypes in headers > > R_ext/BLAS.h and R_ext/Lapack.h but to avoid extensive breakage > > this is only exposed when USE_FC_LEN_T is defined. > > > > If a package's C/C++ calls to BLAS/LAPACK allow for the 'hidden' > > arguments used by most Fortran compilers to pass the lengths of > > Fortran character arguments, define USE_FC_LEN_T and include > > Rconfig.h (possibly _via_ R.h) before including R_ext/BLAS.h or > > R_ext/Lapack.h. > > > > * A package with Fortran source code and perhaps C (but not C++) > > sources can request for its shared object/DLL to be linked by the > > Fortran compiler by including a line USE_FC_TO_LINK= in > > src/Makevars[.win] and using $(SHLIB_OPENMP_FFLAGS) as part of > > PKG_LIBS. > > > > The known reason for doing so is a package which uses Fortran > > (only) OpenMP on a platform where the Fortran OpenMP runtime is > > incompatible with the C one (e.g. gfortran 9.x with clang). > > > > UTILITIES: > > > > * R CMD check has a new option to mitigate checks leaving > > files/directories in /tmp. See the 'R Internals' manual - this > > is part of --as-cran. > > > > Windows: > > > > * The default standard for C++ in package installation is C++11 (as > > it has been on other platforms where available since R 3.6.0: the > > default toolchain on Windows was defaulting to C++98). > > > > DEPRECATED AND DEFUNCT: > > > > * Support for specifying C++98 in package installation is > > deprecated. > > > > * Support in R CMD config for F77, FCPIFCPLAGS, CPP, CXXCPP and > > CXX98 and similar is deprecated. (CPP is found from the system > > make and may well not be set.) > > > > Use $CC -E and $CXX -E instead of CPP and CXXCPP. > > > > BUG FIXES: > > > > * runmed(x, *) when x contains missing values now works > > consistently for both algorithm="Stuetzle" and "Turlach", and no > > longer segfaults for "Turlach", as reported by Hilmar Berger. > > > > * apply(diag(3), 2:3, mean) now gives a helpful error message. > > > > * dgamma(x, shape, log=TRUE) now longer overflows to Inf for shape > > < 1 and very small x, fixing PR#17577, reported by Jonathan > > Rougier. > > > > * Buffer overflow in building error messages fixed. Reported by > > Benjamin Tremblay. > > > > * options(str = .) is correctly initialized at package utils load > > time, now. A consequence is that str() in scripts now is more > > consistent to interactive use, e.g., when displaying function(**) > > argument lists. > > > > * as.numeric(<call>) now gives correct error message. > > > > * Printing ls.str() no longer wrongly shows "<missing>" in rare > > cases. > > > > * Auto-printing S4 objects no longer duplicates the object, for > > faster speed and reduced memory consumption. Reported by Aaron > > Lun. > > > > * pchisq(<LRG>, <LRG>, ncp=100) no longer takes practically forever > > in some cases. Hence ditto for corresponding qchisq() calls. > > > > * x %% L for finite x no longer returns NaN when L is infinite, nor > > suffers from cancellation for large finite L, thanks to Long Qu's > > PR#17611. > > > > Analogously, x %/% L and L %/% x suffer less from cancellation > > and return values corresponding to limits for large L. > > > > * grepl(NA, *) now returns logical as documented. > > > > * options(warn=1e11) is an error now, instead of later leading to C > > stack overflow because of infinite recursion. > > > > * R_tryCatch no longer transfers control for all conditions. > > Reported and patch provided by Lionel Henry in PR#17617. > > > > * format(object.size(.), digits=NULL) now works, fixing PR#17628 > > reported by Jonathan Carroll. > > > > * get_all_vars(f, d) now also works for cases, e.g. where d > > contains a matrix. Reported by Simon Wood in 2009 and patch > > provided by Ben Bolker in PR#13624. > > > > Additionally, it now also works when some variables are data > > frames, fixing PR#14905, reported by Patrick Breheny. > > > > * barplot() could get spacings wrong if there were exactly two bars > > PR#15522. Patch by Michael Chirico. > > > > * power.t.test() works in more cases when returning values of n > > smaller than 2. > > > > * dotchart(*, pch=., groups=.) now works better. Reported by > > Robert and confirmed by Nic Rochette in PR#16953. > > > > * canCoerce(obj, cl) no longer assumes length(class(obj)) == 1. > > > > * plot.formula(*, subset = *) now also works in a boundary case > > reported by Robert Schlicht (TU Dresden). > > > > * readBin() and writeBin() of a rawConnection() now also work in > > large cases, thanks to a report and proposal by Taeke Harkema in > > PR#17665. > > > > -- > > Peter Dalgaard, Professor, > > Center for Statistics, Copenhagen Business School > > Solbjerg Plads 3, 2000 Frederiksberg, Denmark > > Phone: (+45)38153501 > > Office: A 4.23 > > Email: pd.mes at cbs.dk Priv: PDalgd at gmail.com > > > > ______________________________________________ > > R-devel at r-project.org mailing list > > https://stat.ethz.ch/mailman/listinfo/r-devel > > -- > > Sent from Gmail Mobile > > -- > Peter Dalgaard, Professor, > Center for Statistics, Copenhagen Business School > Solbjerg Plads 3, 2000 Frederiksberg, Denmark > Phone: (+45)38153501 > Office: A 4.23 > Email: pd.mes at cbs.dk Priv: PDalgd at gmail.com > > > > > > > > > > --Sent from Gmail Mobile [[alternative HTML version deleted]]
It is possible that this means that it is the intention to port the changes from R-devel to 3.6.2 patched once 3.6.2 is out. In that case, you can be pretty sure that the changes are NOT in 3.6.2 (and actually not in 3.6.2 patched either -- yet). If so, you have provided a nice illustration of why I keep telling people not to do that... -pd> On 12 Dec 2019, at 18:05 , Avraham Adler <avraham.adler at gmail.com> wrote: > > Thank you. > > I apologize for not providing the link. [1] Under the news for R-revel there is a single entry for R 3.6.2-patched. > > The file I downloaded was [2] with a date of 2019-12-12 01:50. > > Is it safe to say that 3.6.2 has the LAPACK upgrades and fixes? > > Apologies in advance if iOS links the URL below. I cannot access gmail desktop from behind my corporate firewall. > > Thank you again, > > Avi > > [1] > https://cran.r-project.org/doc/manuals/r-devel/NEWS.html > [2] > https://stat.ethz.ch/R/daily/R-patched.tar.gz > > On Thu, Dec 12, 2019 at 11:10 AM Peter Dalgaard <pd.mes at cbs.dk> wrote: > It is not obvious what it is that you are calling "R-patched", nor where there could be an entry for "3.6.2 patched". > > The prerelease/patched versions are snapshots of R-3-6-branch made at 00:20 so the current one will have been made before the release version run started at 09:00 this morning, and hence the nightly tarball will be of the release candidate. However it will not be called R-patched: > > lrwxr-xr-x 1 pd staff 29 Dec 12 00:20 R-latest.tar.gz -> R-rc_2019-12-06_r77555.tar.gz > > The current version in SVN differs only by the VERSION file. Its NEWS.Rd starts > > Peters-MacBook-Air:R pd$ more VERSION > 3.6.2 Patched > Peters-MacBook-Air:R pd$ more doc/NEWS.Rd > % -*- coding: utf-8 -*- > \newcommand{\Rlogo}{\if{html}{\figure{../../html/Rlogo.svg}{options: class="toplogo" alt="[R logo]"}}\if{latex}{\figure{Rlogo.pdf}{options: width=0.5in}}} > > \name{NEWS} > \title{R News} > \encoding{UTF-8} > > \section{\Rlogo CHANGES IN R 3.6.2}{ > > \subsection{NEW FEATURES}{ > \itemize{ > .... > > and any changes for 3.6.2 patched should go above the entries for 3.6.2. > > - pd > > > > On 12 Dec 2019, at 16:34 , Avraham Adler <avraham.adler at gmail.com> wrote: > > > > Hi. > > > > Under R-news there is an entry for 3.6.2 patched regarding LAPACK. However, when uncompresding the current R-patched, it creates R-Rc directories. Is this a naming oversight or is the patched version actually the unadjusted release candidate? > > > > Thank you, > > > > Avi > > > > On Thu, Dec 12, 2019 at 4:58 AM Peter Dalgaard via R-devel <r-devel at r-project.org> wrote: > > The build system rolled up R-3.6.2.tar.gz (codename "Dark and Stormy Night") this morning. > > > > The list below details the changes in this release. > > > > You can get the source code from > > > > http://cran.r-project.org/src/base/R-3/R-3.6.2.tar.gz > > > > or wait for it to be mirrored at a CRAN site nearer to you. > > > > Binaries for various platforms will appear in due course. > > > > > > For the R Core Team, > > > > Peter Dalgaard > > > > These are the checksums (md5 and SHA-256) for the freshly created files, in case you wish > > to check that they are uncorrupted: > > > > MD5 (AUTHORS) = b9c44f9f78cab3184ad9898bebc854b4 > > MD5 (COPYING) = eb723b61539feef013de476e68b5c50a > > MD5 (COPYING.LIB) = a6f89e2100d9b6cdffcea4f398e37343 > > MD5 (FAQ) = 28a3942a7129877e9af1d5ea16202052 > > MD5 (INSTALL) = 7893f754308ca31f1ccf62055090ad7b > > MD5 (NEWS) = 45437b38c75e0248b527c00e6d42ee6a > > MD5 (NEWS.0) = bfcd7c147251b5474d96848c6f57e5a8 > > MD5 (NEWS.1) = eb78c4d053ec9c32b815cf0c2ebea801 > > MD5 (NEWS.2) = 591dcf615162127f904e4e461f330ce9 > > MD5 (R-latest.tar.gz) = 90d23d138cee26d275da14b58296e521 > > MD5 (README) = f468f281c919665e276a1b691decbbe6 > > MD5 (RESOURCES) = 529223fd3ffef95731d0a87353108435 > > MD5 (THANKS) = bb45f89c01d509721c47fd41f147da60 > > MD5 (VERSION-INFO.dcf) = 9c33701e25092aefc1d16beb5858f20f > > MD5 (R-3/R-3.6.2.tar.gz) = 90d23d138cee26d275da14b58296e521 > > > > > > 2cde824a7b18958e5f06b391c801c8288be0f84fa8934b7ddefef23c67e60c09 AUTHORS > > e6d6a009505e345fe949e1310334fcb0747f28dae2856759de102ab66b722cb4 COPYING > > 6095e9ffa777dd22839f7801aa845b31c9ed07f3d6bf8a26dc5d2dec8ccc0ef3 COPYING.LIB > > 38219d9c6221ccfbf075ef03711b420a1aa8731f890c8f2337148b602a217c2d FAQ > > f87461be6cbaecc4dce44ac58e5bd52364b0491ccdadaf846cb9b452e9550f31 INSTALL > > 0ceb6fbab3e0e29bc374683fd5c2ccd0c9c62ce8eca2a394a4603775b3ef129c NEWS > > 4e21b62f515b749f80997063fceab626d7258c7d650e81a662ba8e0640f12f62 NEWS.0 > > 12b30c724117b1b2b11484673906a6dcd48a361f69fc420b36194f9218692d01 NEWS.1 > > ca04f78ffe54afa326fe3ed40e7e1411aca0000ed2fa5ead97ddf51c6aa5b7bc NEWS.2 > > bd65a45cddfb88f37370fbcee4ac8dd3f1aebeebe47c2f968fd9770ba2bbc954 R-latest.tar.gz > > 2fdd3e90f23f32692d4b3a0c0452f2c219a10882033d1774f8cadf25886c3ddc README > > 408737572ecc6e1135fdb2cf7a9dbb1a6cb27967c757f1771b8c39d1fd2f1ab9 RESOURCES > > 2a8dca916cd92229ef9e328f3610ca204809c262823b860252b42072dac2473a THANKS > > 40cc7cea5f0e67cf8f2f7b25a534ae6bc53f38eae2ab2c2649a952ed37f0654a VERSION-INFO.dcf > > bd65a45cddfb88f37370fbcee4ac8dd3f1aebeebe47c2f968fd9770ba2bbc954 R-3/R-3.6.2.tar.gz > > > > This is the relevant part of the NEWS file > > > > CHANGES IN R 3.6.2: > > > > NEW FEATURES: > > > > * runmed(x, *) gains a new option na.action determining _how_ to > > handle NaN or NA in x. > > > > * dotchart() gains new options ann, xaxt, frame.plot and log. > > > > INSTALLATION on a UNIX-ALIKE: > > > > * Detection of the C stack direction has been moved from run-time > > to configure: this is safer with LTO builds and allows the > > detection to be overridden - see file config.site. > > > > * Source-code changes enable installation on platforms using gcc > > -fno-common (the expected default for gcc 10.x). > > > > C-LEVEL FACILITIES: > > > > * installTrChar (which is nowadays is wrapped by installChar) is > > defined in Rinternals.h. (Neither are part of the API.) > > > > PACKAGE INSTALLATION: > > > > * Header Rconfig.h contains the value of FC_LEN_T deduced at > > installation which is used by the prototypes in headers > > R_ext/BLAS.h and R_ext/Lapack.h but to avoid extensive breakage > > this is only exposed when USE_FC_LEN_T is defined. > > > > If a package's C/C++ calls to BLAS/LAPACK allow for the 'hidden' > > arguments used by most Fortran compilers to pass the lengths of > > Fortran character arguments, define USE_FC_LEN_T and include > > Rconfig.h (possibly _via_ R.h) before including R_ext/BLAS.h or > > R_ext/Lapack.h. > > > > * A package with Fortran source code and perhaps C (but not C++) > > sources can request for its shared object/DLL to be linked by the > > Fortran compiler by including a line USE_FC_TO_LINK= in > > src/Makevars[.win] and using $(SHLIB_OPENMP_FFLAGS) as part of > > PKG_LIBS. > > > > The known reason for doing so is a package which uses Fortran > > (only) OpenMP on a platform where the Fortran OpenMP runtime is > > incompatible with the C one (e.g. gfortran 9.x with clang). > > > > UTILITIES: > > > > * R CMD check has a new option to mitigate checks leaving > > files/directories in /tmp. See the 'R Internals' manual - this > > is part of --as-cran. > > > > Windows: > > > > * The default standard for C++ in package installation is C++11 (as > > it has been on other platforms where available since R 3.6.0: the > > default toolchain on Windows was defaulting to C++98). > > > > DEPRECATED AND DEFUNCT: > > > > * Support for specifying C++98 in package installation is > > deprecated. > > > > * Support in R CMD config for F77, FCPIFCPLAGS, CPP, CXXCPP and > > CXX98 and similar is deprecated. (CPP is found from the system > > make and may well not be set.) > > > > Use $CC -E and $CXX -E instead of CPP and CXXCPP. > > > > BUG FIXES: > > > > * runmed(x, *) when x contains missing values now works > > consistently for both algorithm="Stuetzle" and "Turlach", and no > > longer segfaults for "Turlach", as reported by Hilmar Berger. > > > > * apply(diag(3), 2:3, mean) now gives a helpful error message. > > > > * dgamma(x, shape, log=TRUE) now longer overflows to Inf for shape > > < 1 and very small x, fixing PR#17577, reported by Jonathan > > Rougier. > > > > * Buffer overflow in building error messages fixed. Reported by > > Benjamin Tremblay. > > > > * options(str = .) is correctly initialized at package utils load > > time, now. A consequence is that str() in scripts now is more > > consistent to interactive use, e.g., when displaying function(**) > > argument lists. > > > > * as.numeric(<call>) now gives correct error message. > > > > * Printing ls.str() no longer wrongly shows "<missing>" in rare > > cases. > > > > * Auto-printing S4 objects no longer duplicates the object, for > > faster speed and reduced memory consumption. Reported by Aaron > > Lun. > > > > * pchisq(<LRG>, <LRG>, ncp=100) no longer takes practically forever > > in some cases. Hence ditto for corresponding qchisq() calls. > > > > * x %% L for finite x no longer returns NaN when L is infinite, nor > > suffers from cancellation for large finite L, thanks to Long Qu's > > PR#17611. > > > > Analogously, x %/% L and L %/% x suffer less from cancellation > > and return values corresponding to limits for large L. > > > > * grepl(NA, *) now returns logical as documented. > > > > * options(warn=1e11) is an error now, instead of later leading to C > > stack overflow because of infinite recursion. > > > > * R_tryCatch no longer transfers control for all conditions. > > Reported and patch provided by Lionel Henry in PR#17617. > > > > * format(object.size(.), digits=NULL) now works, fixing PR#17628 > > reported by Jonathan Carroll. > > > > * get_all_vars(f, d) now also works for cases, e.g. where d > > contains a matrix. Reported by Simon Wood in 2009 and patch > > provided by Ben Bolker in PR#13624. > > > > Additionally, it now also works when some variables are data > > frames, fixing PR#14905, reported by Patrick Breheny. > > > > * barplot() could get spacings wrong if there were exactly two bars > > PR#15522. Patch by Michael Chirico. > > > > * power.t.test() works in more cases when returning values of n > > smaller than 2. > > > > * dotchart(*, pch=., groups=.) now works better. Reported by > > Robert and confirmed by Nic Rochette in PR#16953. > > > > * canCoerce(obj, cl) no longer assumes length(class(obj)) == 1. > > > > * plot.formula(*, subset = *) now also works in a boundary case > > reported by Robert Schlicht (TU Dresden). > > > > * readBin() and writeBin() of a rawConnection() now also work in > > large cases, thanks to a report and proposal by Taeke Harkema in > > PR#17665. > > > > -- > > Peter Dalgaard, Professor, > > Center for Statistics, Copenhagen Business School > > Solbjerg Plads 3, 2000 Frederiksberg, Denmark > > Phone: (+45)38153501 > > Office: A 4.23 > > Email: pd.mes at cbs.dk Priv: PDalgd at gmail.com > > > > ______________________________________________ > > R-devel at r-project.org mailing list > > https://stat.ethz.ch/mailman/listinfo/r-devel > > -- > > Sent from Gmail Mobile > > -- > Peter Dalgaard, Professor, > Center for Statistics, Copenhagen Business School > Solbjerg Plads 3, 2000 Frederiksberg, Denmark > Phone: (+45)38153501 > Office: A 4.23 > Email: pd.mes at cbs.dk Priv: PDalgd at gmail.com > > > > > > > > > > -- > Sent from Gmail Mobile-- Peter Dalgaard, Professor, Center for Statistics, Copenhagen Business School Solbjerg Plads 3, 2000 Frederiksberg, Denmark Phone: (+45)38153501 Office: A 4.23 Email: pd.mes at cbs.dk Priv: PDalgd at gmail.com