Package Details: shiny-server-git 1:1.5.23.1030.r0.gc3cae6c-1

Git Clone URL: https://aur.archlinux.org/shiny-server-git.git (read-only, click to copy)
Package Base: shiny-server-git
Description: Host Shiny applications over the web
Upstream URL: https://rstudio.com/shiny/server
Licenses: AGPL-3.0-only
Conflicts: shiny-server
Provides: shiny-server
Submitter: hwkiller
Maintainer: a821
Last Packager: a821
Votes: 6
Popularity: 0.000000
First Submitted: 2014-01-11 06:46 (UTC)
Last Updated: 2024-10-03 08:18 (UTC)

Dependencies (8)

Required by (0)

Sources (4)

Latest Comments

« First ‹ Previous 1 2 3 4

hwkiller commented on 2016-06-06 03:49 (UTC)

I'm getting the same issue. I'm not sure it's a packaging problem.

jjlynch commented on 2016-06-05 22:50 (UTC)

@minorsecond, I am receiving the same issue compiling. It's failing to compile nodejs?

minorsecond commented on 2016-05-07 09:41 (UTC)

Shiny does not compile at the moment. I submitted an issue on GitHub: https://github.com/rstudio/shiny-server/issues/207

hwkiller commented on 2016-02-23 20:37 (UTC)

Fixed, artem. Thanks. It's been a while since I touched this package. It still seems to compile fine though. I added the /etc/shiny-server

Anatin commented on 2014-02-10 23:58 (UTC)

I've tracked the "global name 'file' is not defined' problem down to the Python 2.6-2.7 vs 3.x issue and the fact that the workaround in the github instructions (PYTHON=`which python2`), while enabling the cmake configuration to complete successfully, still leaves the actual build step broken. I tried the tactic suggested by someone (possibly yourself) on the shiny board, namely linking /usr/local/bin/python to /usr/bin/python2, and that worked. It would be interesting to know if you found another fix.

Anatin commented on 2014-02-10 22:25 (UTC)

Thanks for getting this into the AUR. I do have a problem, though. When I run makepkg, I'm getting a build error that seems centered on the message NameError: global name 'file' is not defined I don't think the problem is with your package, since I get the same thing when building directly from the git project. I'm asking about it because a google search turned up a pastebin of yours with the same error. How did you go about fixing it? Thanks

« First ‹ Previous 1 2 3 4