Error in hash(descFile) : No DESCRIPTION file at path

Open
#317 13 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
r

Research direction

The reported entry point is packrat::init("H:/elicit_falls") on Windows; first reproduce it and inspect the DBI installation and extraction step, including the R CMD INSTALL command shown. Done means initialization installs DBI without the missing DESCRIPTION error, extraction warning, or non-zero exit status.

Written by the indexing model from the issue text.

Description

I am working on a shinyapp that requires packrat to deploy to shinyapp.io. When I try to initialize the package I get the following output:

packrat::init("H:/elicit_falls")
Initializing packrat project in directory:

  • "H:/elicit_falls"

Adding these packages to packrat:
_
BH 1.60.0-2
DBI 0.5
R6 2.1.2
RApiSerialize 0.1.0
Rcpp 0.12.6
RcppRedis 0.1.7
assertthat 0.1
bitops 1.0-6
chron 2.3-47
curl 1.1
data.table 1.9.6
digest 0.6.10
dplyr 0.5.0
htmltools 0.3.5
httpuv 1.3.3
httr 1.2.1
jsonlite 1.0
lazyeval 0.2.0
magrittr 1.5
mime 0.5
miniUI 0.1.1
openssl 0.9.4
packrat 0.4.7-1
rdrop2 0.7.0
shiny 0.13.2
shinyjs 0.6
tibble 1.1
xtable 1.8-2

Fetching sources for BH (1.60.0-2) ... OK (CRAN current)
Fetching sources for DBI (0.5) ... OK (CRAN current)
Fetching sources for R6 (2.1.2) ... OK (CRAN current)
Fetching sources for RApiSerialize (0.1.0) ... OK (CRAN current)
Fetching sources for Rcpp (0.12.6) ... OK (CRAN current)
Fetching sources for RcppRedis (0.1.7) ... OK (CRAN current)
Fetching sources for assertthat (0.1) ... OK (CRAN current)
Fetching sources for bitops (1.0-6) ... OK (CRAN current)
Fetching sources for chron (2.3-47) ... OK (CRAN current)
Fetching sources for curl (1.1) ... OK (CRAN current)
Fetching sources for data.table (1.9.6) ... OK (CRAN current)
Fetching sources for digest (0.6.10) ... OK (CRAN current)
Fetching sources for dplyr (0.5.0) ... OK (CRAN current)
Fetching sources for htmltools (0.3.5) ... OK (CRAN current)
Fetching sources for httpuv (1.3.3) ... OK (CRAN current)
Fetching sources for httr (1.2.1) ... OK (CRAN current)
Fetching sources for jsonlite (1.0) ... OK (CRAN current)
Fetching sources for lazyeval (0.2.0) ... OK (CRAN current)
Fetching sources for magrittr (1.5) ... OK (CRAN current)
Fetching sources for mime (0.5) ... OK (CRAN current)
Fetching sources for miniUI (0.1.1) ... OK (CRAN current)
Fetching sources for openssl (0.9.4) ... OK (CRAN current)
Fetching sources for packrat (0.4.7-1) ... OK (CRAN current)
Fetching sources for rdrop2 (0.7.0) ... OK (CRAN current)
Fetching sources for shiny (0.13.2) ... OK (CRAN current)
Fetching sources for shinyjs (0.6) ... OK (CRAN current)
Fetching sources for tibble (1.1) ... OK (CRAN current)
Fetching sources for xtable (1.8-2) ... OK (CRAN current)
Snapshot written to "H:/elicit_falls/packrat/packrat.lock"
Installing BH (1.60.0-2) ...
OK (downloaded binary)
Installing DBI (0.5) ...
Error in hash(descFile) :
No DESCRIPTION file at path 'H:/elicit_falls/packrat/lib/x86_64-w64-mingw32/3.3.1/DBI/DESCRIPTION'!
In addition: Warning messages:
1: In unzip(zipname, exdir = dest) :
write error in extracting from zip file
2: running command '"C:/PROGRA1/R/R-331.1/bin/x64/R" CMD INSTALL -l "H:\elicit_falls\packrat\lib\x86_64-w64-mingw32\3.3.1" C:\Users\name\AppData\Local\Temp\Rtmpqk8NYM/downloaded_packages/DBI_0.5.tar.gz' had status 1
3: In utils::install.packages(pkgRecord$name, lib = lib, repos = repos, :
installation of package ‘DBI’ had non-zero exit status

Any thought on why this might be happening and solutions?

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

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.

More from rstudio/packrat

All issues in rstudio/packrat

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.