For this reason I wondered if there is a "switch" in the code that is inappropriate-- perhaps the 3.0 version doesn't really need 3.4 but something is telling it is does-- in a header or some part of a minor file. I don't know enough about what is really happening during install to know where this might be.
Package: INLA
Version: 0.0-1468872408
Depends: R (>= 2.10), sp, Matrix, splines
Suggests: mvtnorm, numDeriv, Rgraphviz, graph, fields, rgl, parallel,
pixmap, splancs, orthopolynom, compiler, devtools, knitr,
markdown, shiny
License: GPL (>= 2)
I am using R Studio (0.99.902) and R 3.3.3 on Windows.
I am required to download the package zip, then upload it to our remote system to install because the remote system has no internet access (or very limited-- can upload/download files and access CRAN mirror sites). So I am downloading the zip locally, and then uploading to a directory on the remote system, and installing. Here is the sequence. I am relatively new to this installing packages "by hand" so maybe I am just making a rookie mistake.
>install.packages("H:/Rpackages/INLA_0.0-1468872408.zip",lib="H:/Rpackages/lib") Warning in install.packages :
package `H:/Rpackages/INLA_0.0-1468872408.zip' is not available (for R version 3.3.3)
Warning message:
In dir.create(configdir, recursive=TRUE) :
'\\[path omitted]\R\connect\accounts' already exists
(I have omitted a long network path in the [path omitted] part. I do not want to put network addresses and usernames here.)
R thinks for a while longer and then returns, but subsequently
library(INLA)
Error in library(INLA) : there is no package called 'INLA'
library(INLA, lib.loc="H:/Rpackages/lib")
Error in library(INLA, lib.loc="H:/Rpackages/lib") :
there is no package called 'INLA'