Finn Lindgren

Here's a demo with the latest version, showing that the `type` field contains "exercise" and "question", and not "exercise_submission": https://uoe-maths.shinyapps.io/StatCompQuizDemoDebug/#section-submit

The build process for the INLA R package requires a manual step of first building the standalone inla binary executable, so no INLA package version can be built purely using...

The documentation for `install.packages` contains a further option: > For a binary install from a repository, the function checks for the availability of a source package on the same repository,...

Did the `type = "binary"` method work?

I see in the NEWS.md file that 24.05.10 was the first R 4.4 build, so the error with that one is that it shouldn't be present in any form in...

Have you found a method for specifying a specific INLA version that actually works? I don't see an option for that in `install.packages`, and I don't have access to try...

It tries to build it because it finds a newer source package. I would have expected turning off that check to have fixed it; that may be an error in...

The most generally useful approach on windows and macos seems to be for such users to always specify `type = "binary"` when installing INLA, so that seems to be the...

I see that https://www.r-inla.org/download-install already does mention the `remotes::install_version()` option, specifically in the context of the transition period when INLA gets built for new R versions. But I think as...

There's always a way: downloading the needed tar/zip file manually and installing from the file instead of the repository. But the `type="binary"` option is easier.