[Rd] R 3.6.1 is released

2019-07-05 Thread Peter Dalgaard via R-devel
The build system rolled up R-3.6.1.tar.gz (codename "Action of the Toes") 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.1.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) = 0b9e5d3077558ec2d91d39e03bfb2ad5
MD5 (NEWS.0) = bfcd7c147251b5474d96848c6f57e5a8
MD5 (NEWS.1) = eb78c4d053ec9c32b815cf0c2ebea801
MD5 (NEWS.2) = 591dcf615162127f904e4e461f330ce9
MD5 (R-latest.tar.gz) = f5003472d58a3d3765a1c537fdae71d5
MD5 (README) = f468f281c919665e276a1b691decbbe6
MD5 (RESOURCES) = 529223fd3ffef95731d0a87353108435
MD5 (THANKS) = 08158353102084599797db8c9ccf8e2a
MD5 (VERSION-INFO.dcf) = ff3f371396553df4e1936c10a56d973d
MD5 (R-3/R-3.6.1.tar.gz) = f5003472d58a3d3765a1c537fdae71d5

2cde824a7b18958e5f06b391c801c8288be0f84fa8934b7ddefef23c67e60c09  AUTHORS
e6d6a009505e345fe949e1310334fcb0747f28dae2856759de102ab66b722cb4  COPYING
6095e9ffa777dd22839f7801aa845b31c9ed07f3d6bf8a26dc5d2dec8ccc0ef3  COPYING.LIB
38219d9c6221ccfbf075ef03711b420a1aa8731f890c8f2337148b602a217c2d  FAQ
f87461be6cbaecc4dce44ac58e5bd52364b0491ccdadaf846cb9b452e9550f31  INSTALL
dd2ff3bc1e94c9751aed4182da7ed381bb546535bdf61f33b033474067c85c7c  NEWS
4e21b62f515b749f80997063fceab626d7258c7d650e81a662ba8e0640f12f62  NEWS.0
12b30c724117b1b2b11484673906a6dcd48a361f69fc420b36194f9218692d01  NEWS.1
ca04f78ffe54afa326fe3ed40e7e1411acaed2fa5ead97ddf51c6aa5b7bc  NEWS.2
5baa9ebd3e71acecdcc3da31d9042fb174d55a42829f8315f2457080978b1389  
R-latest.tar.gz
2fdd3e90f23f32692d4b3a0c0452f2c219a10882033d1774f8cadf25886c3ddc  README
408737572ecc6e1135fdb2cf7a9dbb1a6cb27967c757f1771b8c39d1fd2f1ab9  RESOURCES
2d2e85e85574c4430951f6b070c08cd5aff1602abfd1bb162bed6d89c436b11f  THANKS
20cf23c12614c5d9e8f9b3983005a35c8bac4c7340db4d7911afe05ca0688e07  
VERSION-INFO.dcf
5baa9ebd3e71acecdcc3da31d9042fb174d55a42829f8315f2457080978b1389  
R-3/R-3.6.1.tar.gz

This is the relevant part of the NEWS file

CHANGES IN R 3.6.1:

  INSTALLATION on a UNIX-ALIKE:

* The default detection of the shell variable libNN is overridden
  for derivatives of Debian Linux, some of which have started to
  have a /usr/lib64 directory.  (E.g. Ubuntu 19.04.)  As before, it
  can be specified in config.site.

  UTILITIES:

* R CMD config knows the values of AR and RANLIB, often set for LTO
  builds.

  DEPRECATED AND DEFUNCT:

* The use of a character vector with .Fortran() is formally
  deprecated and gives a non-portability warning.  (It has long
  been strongly discouraged in 'Writing R Extensions'.)

  BUG FIXES:

* On Windows, GUI package installation via menuInstallPkgs() works
  again, thanks to Len Weil's and Duncan Murdoch's PR#17556.

* R CMD check on data() fixing PR#17558 thanks to Duncan Murdoch.

* quasi(*, variance = list(..)) now works more efficiently, and
  should work in all cases fixing PR#17560.  Further, quasi(var =
  mu(1-mu)) and quasi(var = "mu ^ 3") now work, and quasi(variance
  = "log(mu)") now gives a correct error message.

* Creation of lazy loading database during package installation is
  again robust to Rprofile changing the current working directory
  (PR#17559).

* boxplot(y ~ f, horizontal=TRUE) now produces correct x- and
  y-labels.

* rbind.data.frame() allows to keep  levels from factor columns
  (PR#17562) via new option factor.exclude.

  Additionally, it works in one more case with matrix-columns which
  had been reported on 2017-01-16 by Krzysztof Banas.

* Correct messaging in C++ pragma checks in tools code for R CMD
  check, fixing PR#17566 thanks to Xavier Robin.

* print()ing and auto-printing no longer differs for functions with
  a user defined print.function, thanks to Bill Dunlap's report.

* On Windows, writeClipboard(.., format = ) now does correctly
  pass format to the underlying C code, thanks to a bug report
  (with patch) by Jenny Bryan.

* as.data.frame() treats 1D arrays the same as vectors, PR#17570.

* Improvements in smoothEnds(x, *) working with NAs (towards
  runmed() working in that case, in the next version of R).

* vcov(glm(), dispersion = *) works correctly again, fixing
  PR#17571 thanks to Pavel Krivitsky.

* R CMD INSTALL of binary packages on Windows now works also with
  per-directory locking.

* R CMD INSTALL and install.packages() on Windows are now more
  robust against a locked

[Rd] parse() drops parse data when encountering `` (bug?)

2019-07-05 Thread Miles McBain
Hi,

I've noticed that partial parse data from parse() is irretrivable when it
errors due to encountering '``' - two backticks in sequence. The print
output also looks more limited than a regular parser error which leads me
to suspect this is a bug. If this is the case could someone with the
authority please add it to R's bug tracker?

My reprex follows.

Thanks,
Miles

``` r
target_text <- "foo = 1 `` {r} foo = 2"
tstfile = srcfile(tempfile())
parse(text = target_text,
  keep.source = TRUE,
  srcfile = tstfile)
#> Error in parse(text = target_text, keep.source = TRUE, srcfile =
tstfile): attempt to use zero-length variable name

getParseData(tstfile)
#> NULL

target_text2 <- "foo = 1 {r} foo = 2"
tstfile = srcfile(tempfile())
parse(text = target_text2,
  keep.source = TRUE,
  srcfile = tstfile)
#> Error in parse(text = target_text2, keep.source = TRUE, srcfile =
tstfile): /tmp/RtmpXuGaL1/file5434ebd1f95:1:9: unexpected '{'
#> 1: foo = 1 {
#> ^

getParseData(tstfile)
#>   line1 col1 line2 col2 id parenttoken terminal text
#> 8 11 17  8  0 equal_assignFALSE
#> 1 11 13  1  3   SYMBOL TRUE  foo
#> 3 11 13  3  8 exprFALSE
#> 2 15 15  2  8EQ_ASSIGN TRUE=
#> 4 17 17  4  5NUM_CONST TRUE1
#> 5 17 17  5  8 exprFALSE
#> 6 19 19  6  0  '{' TRUE{

sessionInfo()
#> R version 3.6.0 (2019-04-26)
#> Platform: x86_64-pc-linux-gnu (64-bit)
#> Running under: Pop!_OS 18.10
#>
#> Matrix products: default
#> BLAS:   /usr/lib/x86_64-linux-gnu/blas/libblas.so.3.8.0
#> LAPACK: /usr/lib/x86_64-linux-gnu/lapack/liblapack.so.3.8.0
#>
#> locale:
#>  [1] LC_CTYPE=en_AU.UTF-8   LC_NUMERIC=C
#>  [3] LC_TIME=en_AU.UTF-8LC_COLLATE=en_AU.UTF-8
#>  [5] LC_MONETARY=en_AU.UTF-8LC_MESSAGES=en_AU.UTF-8
#>  [7] LC_PAPER=en_AU.UTF-8   LC_NAME=C
#>  [9] LC_ADDRESS=C   LC_TELEPHONE=C
#> [11] LC_MEASUREMENT=en_AU.UTF-8 LC_IDENTIFICATION=C
#>
#> attached base packages:
#> [1] stats graphics  grDevices utils datasets  methods   base
#>
#> loaded via a namespace (and not attached):
#>  [1] compiler_3.6.0  magrittr_1.5tools_3.6.0 htmltools_0.3.6
#>  [5] yaml_2.2.0  Rcpp_1.0.1  stringi_1.4.3   rmarkdown_1.12
#>  [9] highr_0.8   knitr_1.23  stringr_1.4.0   xfun_0.8
#> [13] digest_0.6.19   evaluate_0.14
```

Created on 2019-07-05 by the [reprex package](
https://reprex.tidyverse.org) (v0.2.1)

[[alternative HTML version deleted]]

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel


[Rd] CRAN down ?

2019-07-05 Thread Dirk Eddelbuettel


There seems to be another outage of the Vienna CRAN server [1] though from
what I can from afar not related to DNS outage [2].

Could anyone confirm and possibly alert the local team in Vienna?

Dirk

[1] https://twitter.com/d_olivaw/status/1147161883797086214
[2] The DNS resolves on a few sites but eg simple pings stall

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel


Re: [Rd] CRAN down ?

2019-07-05 Thread peter dalgaard
Hum, I could reach the machine once:

$ ssh cran.r-project.org

The programs included with the Debian GNU/Linux system are free software;


but now it hangs on connecting. So either it is being DOS'ed or someone saw the 
problem and restarted it.

-pd


> On 5 Jul 2019, at 18:45 , Dirk Eddelbuettel  wrote:
> 
> 
> There seems to be another outage of the Vienna CRAN server [1] though from
> what I can from afar not related to DNS outage [2].
> 
> Could anyone confirm and possibly alert the local team in Vienna?
> 
> Dirk
> 
> [1] https://twitter.com/d_olivaw/status/1147161883797086214
> [2] The DNS resolves on a few sites but eg simple pings stall
> 
> -- 
> http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
> 
> __
> R-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

-- 
Peter Dalgaard, Professor,
Center for Statistics, Copenhagen Business School
Solbjerg Plads 3, 2000 Frederiksberg, Denmark
Phone: (+45)38153501
Office: A 4.23
Email: pd@cbs.dk  Priv: pda...@gmail.com

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel


Re: [Rd] CRAN down ?

2019-07-05 Thread Friedrich Leisch


> On Fri, 5 Jul 2019 11:45:41 -0500,
> Dirk Eddelbuettel (DE) wrote:

  > There seems to be another outage of the Vienna CRAN server [1] though from
  > what I can from afar not related to DNS outage [2].

  > Could anyone confirm and possibly alert the local team in Vienna?

Seems to work fine for me, both http and ping from non-WU machines
(but of course from Vienna):

leisch@nona01:~$ ping cran.r-project.org
PING cran.wu-wien.ac.at (137.208.57.37) 56(84) bytes of data.
64 bytes from cran.wu-wien.ac.at (137.208.57.37): icmp_seq=1 ttl=58 time=1.43 ms
64 bytes from cran.wu-wien.ac.at (137.208.57.37): icmp_seq=2 ttl=58 time=1.22 ms
64 bytes from cran.wu-wien.ac.at (137.208.57.37): icmp_seq=3 ttl=58 time=1.62 ms
64 bytes from cran.wu-wien.ac.at (137.208.57.37): icmp_seq=4 ttl=58 time=1.47 ms

Best,
Fritz

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel


Re: [Rd] CRAN down ?

2019-07-05 Thread peter dalgaard
The latter

pd@cran:~$ uptime
 19:37:51 up 0 min,  2 users,  load average: 4.80, 1.30, 0.44


> On 5 Jul 2019, at 19:37 , peter dalgaard  wrote:
> 
> Hum, I could reach the machine once:
> 
> $ ssh cran.r-project.org
> 
> The programs included with the Debian GNU/Linux system are free software;
> 
> 
> but now it hangs on connecting. So either it is being DOS'ed or someone saw 
> the problem and restarted it.
> 
> -pd
> 
> 
>> On 5 Jul 2019, at 18:45 , Dirk Eddelbuettel  wrote:
>> 
>> 
>> There seems to be another outage of the Vienna CRAN server [1] though from
>> what I can from afar not related to DNS outage [2].
>> 
>> Could anyone confirm and possibly alert the local team in Vienna?
>> 
>> Dirk
>> 
>> [1] https://twitter.com/d_olivaw/status/1147161883797086214
>> [2] The DNS resolves on a few sites but eg simple pings stall
>> 
>> -- 
>> http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
>> 
>> __
>> R-devel@r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-devel
> 
> -- 
> Peter Dalgaard, Professor,
> Center for Statistics, Copenhagen Business School
> Solbjerg Plads 3, 2000 Frederiksberg, Denmark
> Phone: (+45)38153501
> Office: A 4.23
> Email: pd@cbs.dk  Priv: pda...@gmail.com
> 
> 
> 
> 
> 
> 
> 
> 
> 

-- 
Peter Dalgaard, Professor,
Center for Statistics, Copenhagen Business School
Solbjerg Plads 3, 2000 Frederiksberg, Denmark
Phone: (+45)38153501
Office: A 4.23
Email: pd@cbs.dk  Priv: pda...@gmail.com

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel