rstudio / rstudio/packrat

Error about "file exists" when opening a project

Open
#609 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
R
Stars
409
Forks
89
PR merge metrics
No merged PRs in 30d

Description

I just updated R via homebrew, and now when I launch the RStudio IDE on my mac and open an existing project I get

Warning message:
In file.symlink(from, to) :
  cannot symlink '/usr/local/Cellar/r/4.0.2_1/lib/R/library/base' to '/Users/mike/src/work/gRED/packrat/lib-R/x86_64-apple-darwin19.5.0/4.0.2/base', reason 'File exists'

I'm assuming that this is something with the update to R, since the symlink exists but points to the old version of R I had:

$ ls -l /Users/mike/src/work/gRED/packrat/lib-R/x86_64-apple-darwin19.5.0/4.0.2/base
lrwxr-xr-x 1 mike staff 44 Jun 23 21:58 /Users/mike/src/work/gRED/packrat/lib-R/x86_64-apple-darwin19.5.0/4.0.2/base -> /usr/local/Cellar/r/4.0.2/lib/R/library/base

Running packrat::restore() didn't seem to help out any.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the warning by opening the existing project and running packrat::restore(), then inspect the symlink paths under packrat/lib-R/x86_64-apple-darwin19.5.0/4.0.2 and the old and new Homebrew R library targets shown in the report. Done means the project opens and restores without the file-exists warning while handling the existing base link correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.