Package Details: mattermost 5.7.0-1

Git Clone URL: (read-only)
Package Base: mattermost
Description: Open source Slack-alternative in Golang and React
Upstream URL:
Keywords: chat mattermost messenger networking slack
Licenses: Apache, AGPL
Submitter: mtorromeo
Maintainer: wget (caleb)
Last Packager: wget
Votes: 26
Popularity: 0.164023
First Submitted: 2015-08-24 15:14
Last Updated: 2019-01-20 19:50

Latest Comments

1 2 3 4 5 6 ... Next › Last »

baltitenger commented on 2019-02-07 18:38

It seems like the /usr/share/webapps/mattermost/bin/client/ directory doesn't get created on install, and mattermost shows this warning: "msg":"Failed to start up plugins","error":"mkdir ./client/plugins: no such file or directory".

EDIT: I've tried creating it, reset the database, and now it only shows a 404 page, but no warnings. If I delete it and reset the database again, it works but shows the warnings.

Dr0ID commented on 2019-02-01 10:07

Hi, please provide wget in makedepends packages.

/bin/sh: line 1: wget: command not found
/bin/sh: line 1: wget: command not found
make: *** [build/ package] Error 127

ArchangeGabriel commented on 2018-11-24 11:45

Building without -i indeed works.

ArchangeGabriel commented on 2018-11-21 16:06

We don’t have reproducible builds yet, building tools still need to be updated. However there is a test server that try to assess whether our builds are reproducible using the new devtools code, you can see it in action here:

Regarding the way to build Go packages, I don’t know, things are moving quite fast there (I think the today standard is go modules, replacing go dep and whatever there was before).

wget commented on 2018-11-12 18:57

@ArchangeGabriel Also, wrt. the aforementioned Go issues you linked to me. It is written in the issues comments we shouldn't be using go install -i any more. Should I report/fix this upstream i.e. directly at Mattermost?

wget commented on 2018-11-12 18:56

@ArchangeGabriel Thanks. Actually I know what these go related compilation trimming functions did, but what I didn't was their purpose: going a step forward to reproducible builds. And for the record, I usually got warnings when building Mattermost. The warnings said local paths were leaking in the final executable. It seems this is even fixing these. Do we have a reproducible build now, or yet further work is required?

ArchangeGabriel commented on 2018-11-11 23:30

They are necessary to remove the building path from the produced objects, which is a good practice and also helps reproducibility of builds.

wget commented on 2018-11-11 22:49

@ArchAngeGabriel Ok thanks. I thought the gcflags and asmflags were part of the patch to support PIE. Why do you have specified them? What was their purpose in this context?

ArchangeGabriel commented on 2018-11-11 22:45

@wget: There is a transient bug with the -trimpath GOFLAGS that often results in this (upstream bugs at and You can leave those flags apart for now, they are definitively not as import as PIE/RELRO.

wget commented on 2018-11-11 22:35

@ArchangeGabriel: I implemented all the changes you requested but for some reason locally, the build system now tries to overwrite local go libraries: Do you know why?