Gábor Csárdi

My guess is that this is the same as https://github.com/r-lib/actions/issues/559 Here is a workaround: ``` ❯ pak::pak("any::MASS?reinstall") → Will install 1 package. → The package (1.16 MB) is cached. +...

@schloerke you can specify a read only, ephemeral PAT, though, no? If this is for GH actions.

This is how you restrict the permissions for the temporary token: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions AFAIR the rate limit for the automatic token is 1000 requests per hour per repo, which is usually...

I thought that the limit of the automatic token was per repo,no?

@cderv I built a new binary for R 4.0.x Windows, you can try `pak::pak_update()`. I haven't actually tested it much, so I might need to reopen this...

Oh, that's great, because it did not work for the thing I tried. :) Let me write some tests for this...

For the record, #175 is not a related issue, that is a download error, this one is an installation error. I am not sure why it happens, but it has...

It is more clear when running the underlying pkgdepends commands: ```r > p p$solve() ✔ Loading global cached package metadata ... done > p$download() ℹ Getting 1 pkg (115.13 kB)...

> Could it be a "staged install" thing where ps already is loaded and used by pak and some lock during a staged install phase prevents it from be "replaced"?...

I am fairly sure that the issue is that the package (e.g. ps) is already installed on the parent image, and pak tries to move/rename its directory before the installation....