Package Details: quassel-webserver-git 2.2.8.r1.g4d8031e-1

Git Clone URL: https://aur.archlinux.org/quassel-webserver-git.git (read-only, click to copy)
Package Base: quassel-webserver-git
Description: A web client for Quassel (requires a running quasselcore)
Upstream URL: https://github.com/magne4000/quassel-webserver
Licenses: MIT
Submitter: nylocx
Maintainer: xiota
Last Packager: nylocx
Votes: 0
Popularity: 0.000000
First Submitted: 2016-11-03 11:09 (UTC)
Last Updated: 2017-02-22 12:50 (UTC)

Latest Comments

nylocx commented on 2019-05-05 14:45 (UTC)

I had to install the nodejs-ws package to make the server work again.

AndrzejL commented on 2018-05-06 22:47 (UTC)

gyp ERR! build error gyp ERR! stack Error: make failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/node-gyp/lib/build.js:258:23) gyp ERR! stack at ChildProcess.emit (events.js:182:13) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:225:12) gyp ERR! System Linux 4.14.39-1-lts gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /home/andrzejl/.makepkgs/quassel-webserver-git/src/quassel-webserver/node_modules/bufferutil gyp ERR! node -v v10.0.0 gyp ERR! node-gyp -v v3.6.2 gyp ERR! not ok npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! bufferutil@2.0.1 install: prebuild-install || node-gyp rebuild npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the bufferutil@2.0.1 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/andrzejl/.npm/_logs/2018-05-06T22_46_01_317Z-debug.log ==> ERROR: A failure occurred in package(). Aborting...

Gnurou commented on 2017-05-22 04:25 (UTC)

Just installed this package on a nginx reverse proxy and edited settings-user.js to reflect the prefix I used. The UI loads but remains stuck in "loading" status, and looking at the logs I see that /quassel/javascripts/libquassel.min.js cannot be found. And sure enough it doesn't exist in public/javascripts/ - actually a bunch of files seem to be missing. Would you know why?