Error publishing to shinyapps.io: ERROR: configuration failed for package ‘jqr’

Hi,

I'm getting the following error on attempting to deploy a web app from RStudio to shinyapps.io.

I'd be grateful for any advice on how to resolve.

Thanks,
Richard

Blockquote

  • DONE (lazyeval)
    [2017-10-23T12:16:06.982906748+0000] Building R package: jqr (1.0.0)
    /mnt/packages/build /mnt
  • installing to library ‘/usr/local/lib/R/site-library’
  • installing source package ‘jqr’ ...
    ** package ‘jqr’ successfully unpacked and MD5 sums checked
    Using PKG_CFLAGS=
    Using PKG_LIBS=-ljq
    ------------------------- ANTICONF ERROR ---------------------------
    Configuration failed because libjq was not found.
    On Ubuntu 14.04 or 16.04 you can use the PPA:
    sudo add-apt-repository -y ppa:opencpu/jq
    sudo apt-get update
    sudo apt-get install libjq-dev
    On other sytems try installing:
  • deb: libjq-dev (Debian, Ubuntu 16.10 and up).
  • rpm: jq-devel (Fedora, EPEL)
  • csw: libjq_dev (Solaris)
  • brew: jq (OSX)
    If is already installed set INCLUDE_DIR and LIB_DIR manually via:
    R CMD INSTALL --configure-vars='INCLUDE_DIR=... LIB_DIR=...'

ERROR: configuration failed for package ‘jqr’

  • removing ‘/usr/local/lib/R/site-library/jqr’
    ################################# End Task Log #################################
    Error: Unhandled Exception: Child Task 492810781 failed: Error building image: Error building jqr (1.0.0). Build exited with non-zero status: 1
    In addition: Warning message:
    In value[3L] :
    Failed to parse /tmp/RtmpNkwPAt/file62a767228b17/test.R ; dependencies in this file will not be discovered.
    Execution halted

Blockquote

I think the package is a dependency of rmapshaper,
After removing rmapshaper, I was able to deploy the web app.

jqr 1.0.0 was recently released and removed the bundled jq it previously had.

http://docs.rstudio.com/shinyapps.io/getting-started.html#system-packages
https://github.com/rstudio/shinyapps-package-dependencies/issues/108

Until that issue is resolved, you can use an older version of jqr to work around this problem.