Gábor Csárdi

https://github.com/Claudius-Appel/duflor/blob/7a43ff7936737eb8ebc0f9609dd95bed01fa860e/renv.lock#L27 https://github.com/Claudius-Appel/duflor.gui/blob/67e8eefa501aefe40b8f1e765d690aac9420f06a/renv.lock#L7

AFAICT there is nothing for me to do here, but please reopen if you think otherwise. Thanks!

Can you try to create a reproducible example that I can actually run? `callr::r_bg()` returns a handle that you can use to manipulate the process and get its output. If...

Sorry, I meant an example that I can run without any setup and changes. Ideally it would use the callr package only, not extra packages that I am not familiar...

``` ~/works/callr upkeep-2025-04 ❯ Rscript ~/Downloads/cron.test.txt 12:32:56 CRON STARTED ~/works/callr upkeep-2025-04* ❯ ``` What am I supposed to see here?

I am sorry for being repetitive here, but what is supposed to happen when I run your code? What happens instead?

I suggest you use `pak::pkg_name_check()` instead of `available::available()`: ``` ❯ pak::pkg_name_check("isitwet") ╔══════════════════════════════════════════════════════════════════════════════╗ ║ –*– isitwet –*– ║ ╚══════════════════════════════════════════════════════════════════════════════╝ ┌──────────────────────────────────────────────────────────────────────────────┐ │ ✔ valid name ✔ CRAN ✔ Bioconductor ✔ not a...

@louisaslett With what version of pak and R? On what platform? How did you install pak?

Seems to be fixed in the dev version, you can install it like this: ``` install.packages("pak", repos = sprintf( "https://r-lib.github.io/p/pak/devel/%s/%s/%s", .Platform$pkgType, R.Version()$os, R.Version()$arch )) ``` https://pak.r-lib.org/reference/install.html#nightly-builds

Thanks for the detailed report! I suggest you try the pak package for this, it might work out of the box.