search for: _tar

...30.231.102.145) For various reasons (which need not be expanded here) I have tried to update my long neglected R in MacOS X using handy command line tool update.packages() using readily available binaries of contributed packages at CRAN. However, this fails with message saying that packages xxxx_*_tar.gz is not found at the server (HTTP error 404). Obviously, the package name is expanded wrongly as the binary packages for MacOS X have type *.tgz. However, this seems not be the problem, but there are two other problems: 1. update.packages does not transfer the value of 'type' to the next...

...reasons (which need not be expanded here) I have tried to update my > > long neglected R in MacOS X using handy command line tool update.packages() > > using readily available binaries of contributed packages at CRAN. However, this > > fails with message saying that packages xxxx_*_tar.gz is not found at the server > > (HTTP error 404). Obviously, the package name is expanded wrongly as the binary > > packages for MacOS X have type *.tgz. However, this seems not be the problem, > > but there are two other problems: > > > > 1. update.packages does not...

...reasons (which need not be expanded here) I have tried to update my > > long neglected R in MacOS X using handy command line tool update.packages() > > using readily available binaries of contributed packages at CRAN. However, this > > fails with message saying that packages xxxx_*_tar.gz is not found at the server > > (HTTP error 404). Obviously, the package name is expanded wrongly as the binary > > packages for MacOS X have type *.tgz. However, this seems not be the problem, > > but there are two other problems: > > > > 1. update.packages does not...