Moving Packrat between different R versions with incompatible packages, and dealing with archived packages.
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 409
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
I'm facing two problems with Packrat currently, for a project I moved from a machine with R 3.3 to one with 3.2.
First the output of status():
packrat::status()
The following packages are referenced in your code, but are not present
in your library nor in packrat:
RSofia
actuar
e1071
You will need to install these packages manually, then use
packrat::snapshot() to record these packages in packrat.
The following packages have been updated in your library, but have not been recorded in packrat:
library packrat
Ckmeans.1d.dp 3.4.6 NA
car 2.0-20 NA
caret 6.0-70 NA
doMC 1.3.4 NA
nlme 3.1-128 NA
xgboost 0.4-4 NA
zoo 1.7-13 NA
Use packrat::snapshot() to record these packages in packrat.
Warning messages:
1: In FUN(X[[i]], ...) :
Package 'actuar' not available in repository or locally
2: In FUN(X[[i]], ...) :
Package 'RSofia' not available in repository or locally
RSofia and actuar are the main problems here.
RSofia has been archived and I can install it, but I'm getting some connection errors.
actuar is not available for R 3.2, so there's no way for me to install it. I've tried removing it from the packrat.lock file but the error remains.
Is there a way for me to "purge" these packages so packrat no longer cares if they are installed or not?
When I try clean("actuar", force = TRUE) I get Error in find.package(pkgs, lib) : there is no package called ‘actuar’
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported status() and clean("actuar", force = TRUE) behavior in a project using the referenced packrat.lock. Start by examining how packrat handles unavailable or archived packages and edited lockfile entries; done when the intended purge behavior is clear and status() no longer reports the removed package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100