Lorenz Walthert

@gravesti thanks for your work. This works now in principle. Only practical problem are the heavly dependencies, in particular in a CI setting. So, it may work best if you...

Thanks @smingerson, I will look into that. Meanwhile, you can check out what Kevin wrote about `load()` Vs. `source(„renv/activate“)` in https://github.com/rstudio/renv/issues/900: > That seems strange to me -- calling source("renv/activate.R")...

Can you @smingerson try the latest main branch? I.e. in your `.pre-commit-config.yaml`, use `rev: 45e412b` for the hook repo instead of `0.2.2.9010`? The problem was probably with the file I...

Did you re-initialize the project? That `activate.R` is not supposed to be changed, whats supposed to change is `renv/activate.R`. Can you confirm this has the right version in line 5?

If the problem still occurs, we might indeed have to change `activate.R`, but that won't be here but in the upstream pre-commit framework.

> Precommit generated a new environment if that is what you mean by re-initialize. like run `$ pre-commit clean` and `$ pre-commit install` in that git repo.

Thanks for your persistence. Can you try again (with `$ pre-commit clean` and `$ pre-commit install`) with setting your `activate.R` to (commenting out the lines from your previous example). ```r...

> Unfortunately I cannot share it, but it is essentially a bare RStudio project. I can tinker with a new project and try to reproduce on Linux sometime this week...

Ok, thanks. What the pre-commit version you are using? Because it was also fixed there in [release v2.17.0](https://github.com/pre-commit/pre-commit/releases/tag/v2.17.0) to cover the case when you have an out-of-data {renv} version and...

I don’t expect it to solve the issue, but let’s upgrade and rule this out.