jamovi

Posted: **Fri Feb 24, 2023 2:08 pm**

When running

jmvtools::install()

I constantly have to remove the LOCK file

Code: Select all

build/R4.0.5-win64/00LOCK-temp

Can this be automated? I tried looking for a force option but could not find it.

Posted: **Mon Feb 27, 2023 2:59 am**

hi,

that file is created by R, and it is usually only left behind when the installation process crashes. i'm not sure why it would be left behind otherwise.

jonathon

Posted: **Mon Feb 27, 2023 3:55 pm**

Strange, it does not look like the installation crashes but it still consistently leaves the LOCK file behind. This is the jmvtools:install() output I get:

Code: Select all

jamovi compiler

jamovi 2.2.5 found at C:\Program Files\jamovi 2.2.5.0\bin\jamovi.exe
wrote: bmtest.h.R
wrote: bmtest.src.js
(node:18636) [DEP0128] DeprecationWarning: Invalid 'main' field in 'C:\Program Files\R\R-4.2.1\library\jmvtools\node_modules\jamovi-compiler\node_modules\po2json\package.json' of './lib/po2json'. Please either fix that or report it to the module author
(Use `node --trace-deprecation ...` to show where the warning was created)
wrote: bmtest.js
writing module meta
wrote: 0000.yaml
wrote: jamovi.yaml
wrote: jamovi-full.yaml
* installing *source* package 'bmtest' ...
** using staged installation
Warning in as.POSIXlt.POSIXct(x, tz) : unknown timezone 'Europe/Berlin'
Warning in as.POSIXlt.POSIXct(x, tz) : unknown timezone 'GMT'
Warning in as.POSIXlt.POSIXct(x, tz) :
  unknown timezone 'America/New_York'
Warning in as.POSIXlt.POSIXct(x, tz) : unknown timezone 'GMT'
Warning in as.POSIXlt.POSIXct(x, tz) :
  unknown timezone 'America/New_York'
** R
** inst
** byte-compile and prepare package for lazy loading
** building package indices
** testing if installed package can be loaded from temporary location
** testing if installed package can be loaded from final location
** testing if installed package keeps a record of temporary installation path
* DONE (bmtest)
wrote module: bmtest_0.0.0.jmo

Installing bmtest_0.0.0.jmo

Posted: **Tue Feb 28, 2023 7:39 am**

I find it is quite random as to whether the LOCK file is produced.
So I just always run the two commands:

p_unlock(lib.loc = "C:/Users/.../build/R4.1.2-win64")
jmvtools::install()

whether or not it is found, the install goes ahead

jamovi

jmvtools::install() LOCK file

jmvtools::install() LOCK file

Re: jmvtools::install() LOCK file

Re: jmvtools::install() LOCK file

Re: jmvtools::install() LOCK file