Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - mattermost

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: mattermost 3.6.2-1

Git Clone URL: https://aur-dev.archlinux.org/mattermost.git (read-only)
Package Base: mattermost
Description: Open source Slack-alternative in Golang and React
Upstream URL: http://mattermost.org
Licenses: MIT
Submitter: mtorromeo
Maintainer: mtorromeo
Last Packager: mtorromeo
Votes: 14
Popularity: 0.632112
First Submitted: 2015-08-24 15:14
Last Updated: 2017-02-01 10:28

Latest Comments

1 2 3 Next › Last »

gabx commented on 2016-10-28 10:40

on 2016-10-26, package build fine IF you use git master branch and not the 3.4.0

gabx commented on 2016-08-26 08:37

Build failed too with the following error:

WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.14
npm WARN extract-text-webpack-plugin@1.0.1 requires a peer of webpack@^1.9.11 but none was installed.
npm WARN mocha-webpack@0.4.0 requires a peer of webpack@^1.12.13 but none was installed.
npm ERR! Linux 4.7.1-1-hortensia
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v6.4.0
npm ERR! npm v3.10.6

npm ERR! node-sass@3.8.0 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@3.8.0 postinstall script 'node scripts/build.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node scripts/build.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs node-sass
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls node-sass

serialoverflow commented on 2016-08-10 22:48

Fails building for me, too, although with a different message:

This issue was fixed just 3 days ago on git but maybe you can patch it:

cirkit commented on 2016-08-02 09:57

Getting a bunch of npm deprecated warnings that ultimately fails with 'make'.

Getting dependencies using npm
npm install
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated npmconf@2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN deprecated cross-spawn-async@2.2.4: cross-spawn no longer requires a build toolchain, use it instead!
npm WARN deprecated lodash@1.0.2: lodash@<3.0.0 is no longer maintained. Upgrade to lodash@^4.0.0.
npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
make[1]: *** [Makefile:15: .npminstall] KilledentlyRm don't care about contents; nuking /tmp/yaourt-tmp-cirkit/aur-mattermost/src/platform-3.2.0/web
make[1]: Leaving directory '/tmp/yaourt-tmp-cirkit/aur-mattermost/src/platform-3.2.0/webapp'
make: *** [Makefile:243: build-client] Error 2
==> ERROR: A failure occurred in build().
==> ERROR: Makepkg was unable to build mattermost.
==> Restart building mattermost ? [y/N]
==> -----------------------------------

vith commented on 2016-05-18 19:49

Not super important but the about page with 3.0.1-1 installed says "Version: 3.0.0 ()", "Build Hash:", and "Build Date:"

mtorromeo commented on 2016-05-10 09:10

Yeah, they did not care about the binary name since they are developing it without considering packaging issues. There is no official package to look into.

Upstream only documents manual installation and docker containers but since this IS a package I have to adapt it a little.

Thanks for pointing out about the conflict. I am going to revert to the `platform` name inside `/usr/share/webapps/mattermost` and maybe write a little wrapper `mattermostd` in /usr/bin.

I can also confirm that you need to make config.json writable by mattermost for thing to persist. I'll try to fix that too.

vith commented on 2016-05-09 22:15

Ah okay. I don't think they meant for `platform` to be in $PATH though. http://docs.mattermost.com/install/prod-ubuntu.html#set-up-mattermost-server step 8 for example has you run it as `./platform`.

In fact, running `platform` or `mattermost` doesn't work unless you cd to `/usr/share/webapps/mattermost/` first anyway (and also run it with `sudo -u mattermost`).

I haven't looked into how the official packaging distributes it, but if you want to keep it in /usr/bin maybe it's worth printing a hint during package installation that explains the binary has been renamed. As a side note, renaming it to `mattermost` makes this package conflict with aur/mattermost-desktop.

Another issue I noticed which may be due to the packaging here is that changes in the System Console webui do not persist between service restarts. I don't see any errors in the log but I imagine it's because `/etc/webapps/mattermost/config.json` isn't writable by the mattermost user as installed?

mtorromeo commented on 2016-05-09 19:31

There's a `mattermost` binary in /usr/bin which corresponds to the `platform` you are referring to.
I know it's a deviation from the official documentation but `platform` in /usr/bin felt wrong and way too generic.

vith commented on 2016-05-09 18:06

Can you package the `platform` binary? It's the only way to do a few things, like deleting teams.


mailme45 commented on 2016-04-11 15:17

Same error as gabomarin26