Re: [Rd] Unexpected EOF in R-patched_2017-01-30

2017-02-01 Thread Avraham Adler
On Wed, Feb 1, 2017 at 3:14 AM, Martin Maechler wrote: > Or the file was corrupted during download? > > Here are the md5sum s from the server itself for the last three snapshots: > > 388b607afe732c92442dbb49845fe377 /ftp/R/R-patched_2017-01-31.tar.gz >

Re: [Rd] Unexpected EOF in R-patched_2017-01-30

2017-02-01 Thread Avraham Adler
It worked for me at home but not at work. I will email my work the copy I have at home. It could have been something with our connectivity or firewall. My home copy of 1-31 is also 388b607afe732c92442dbb49845fe377. I'll check the work ones tomorrow, or should I say later today. Thank you, Avi

Re: [Rd] Unexpected EOF in R-patched_2017-01-30

2017-02-01 Thread Martin Maechler
> Avraham Adler > on Tue, 31 Jan 2017 16:07:20 -0500 writes: > On Tue, Jan 31, 2017 at 3:30 PM, peter dalgaard wrote: >> >>> On 31 Jan 2017, at 18:56 , Avraham Adler wrote: >>> >>> Hello.

Re: [Rd] Unexpected EOF in R-patched_2017-01-30

2017-01-31 Thread Avraham Adler
On Tue, Jan 31, 2017 at 3:30 PM, peter dalgaard wrote: > >> On 31 Jan 2017, at 18:56 , Avraham Adler wrote: >> >> Hello. >> >> When trying to unpack today's version of R-patched, > > From which source? The files from cran.r-project.org seems OK, both

Re: [Rd] Unexpected EOF in R-patched_2017-01-30

2017-01-31 Thread peter dalgaard
> On 31 Jan 2017, at 18:56 , Avraham Adler wrote: > > Hello. > > When trying to unpack today's version of R-patched, >From which source? The files from cran.r-project.org seems OK, both those in >src/base-prerelease and those from ETHZ. Also, is it not "tar -xfz"

[Rd] Unexpected EOF in R-patched_2017-01-30

2017-01-31 Thread Avraham Adler
Hello. When trying to unpack today's version of R-patched, I get the following error: C:\R>tar -xf R-patched_2017-01-30.tar.gz gzip: stdin: unexpected end of file tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now I got the same error for