Custom Query (1173 matches)
Results (100 - 102 of 1173)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5083 | fixed | npm wants to install to /home/mediagoblin, but the mg system account doesn't use a home dir | ||
| Description |
We specifically don't create a home directory for the 'mediagoblin' system account as part of the setup process, but npm wants to install to the mediagoblin user home dir: checking for virtualenv... virtualenv
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for a BSD-compatible install... /usr/bin/install -c
configure: creating ./config.status
config.status: creating Makefile
config.status: creating mediagoblin/_version.py
./devtools/update_extlib.sh
which: no bower in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin)
Bower not found, installing via npm!
npm ERR! Error: EACCES, mkdir '/home/mediagoblin'
npm ERR! { [Error: EACCES, mkdir '/home/mediagoblin'] errno: 3, code: 'EACCES', path: '/home/mediagoblin' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! System Linux 3.10.0-229.1.2.el7.x86_64
npm ERR! command "node" "/usr/bin/npm" "install" "bower"
npm ERR! cwd /srv/mediagoblin.chicagolug.org/mediagoblin
npm ERR! node -v v0.10.33
npm ERR! npm -v 1.3.6
npm ERR! path /home/mediagoblin
npm ERR! code EACCES
npm ERR! errno 3
npm ERR! stack Error: EACCES, mkdir '/home/mediagoblin'
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /srv/mediagoblin.chicagolug.org/mediagoblin/npm-debug.log
npm ERR! not ok code 0
make: *** [extlib] Error 3
Is there an alternate install location for this part of the process (e.g., somewhere in /srv/mediagoblin.example.org/bin ) or should we create a mediagoblin home directory? I'm setting this as a 0.8 milestone bug because I think we need to decide which approach to take & document things appropriately in the deployment docs. |
|||
| #355 | fixed | nose and modules with optional library deps | ||
| Description |
During unit tests nose imports every ``*.py`` it finds in the tree. It does so to search for unit tests there. If the import fails, this gives an error in the final unit test results. For GMG this can fail, because some modules import optional libraries (video for example). Currently known options: 1. Add hard dependencies again for all optional libraries. Not nice, but would solve the problem at hand. 2. Rewrite the affected modules to somehow gracefully handle the situation and not error. Not really nice, but acceptable. 3. Change ``runtests.sh`` to call nose in a way, that tests are only searched in ``mediagoblin.tests``. This seems the nicest way. |
|||
| #5080 | fixed | node vs nodejs on Debian Jessie | ||
| Description |
The currently-supported Debian platform is Debian Wheezy, but Debian Jessie will be out soon, so I attempted a test install on Jessie. If we do not intend to support Debian Jessie for the 0.8 release, this issue can be pushed-back to the 0.9 release. The issue is that the ./bin/bootstrap.sh . . . && make step fails due to a naming change in Debian / Ubuntu, whereby "node" is now packaged as "nodejs". See here for more details on that change: http://stackoverflow.com/questions/18130164/nodejs-vs-node-on-ubuntu-12-04 Creating a symlink between /usr/bin/nodejs and /usr/bin/node allows the bootstrap process to proceed, so it isn't really a problem with the overall program / code. Perhaps, as part of the bootstrap step, we should check to see if "node" works, and (if not) try "nodejs", and if that doesn't work, say that the step failed. The existing setup / code which looks for "node" does work on Fedora 21 installs, though, so I don't think that we can just flat-out switch from looking for "node" to looking for "nodejs". As a final comment, I'm not at a computer where I would have access to the actual error message, but hopefully what I've provided is enough information. Thanks. |
|||
