Package Details: mattermost 4.7.2-1

Git Clone URL: https://aur.archlinux.org/mattermost.git (read-only)
Package Base: mattermost
Description: Open source Slack-alternative in Golang and React
Upstream URL: https://mattermost.com
Licenses: Apache, AGPL
Submitter: mtorromeo
Maintainer: wget (caleb)
Last Packager: caleb
Votes: 24
Popularity: 1.878056
First Submitted: 2015-08-24 15:14
Last Updated: 2018-03-01 12:43

Latest Comments

chrissnell commented on 2018-03-30 01:44

Any chance we could get 4.8.x, @caleb?

caleb commented on 2018-02-24 09:01

I've pushed 4.7.x to this, especially with security patches out now that apply to 4.6.x as well it seemed important to get it up to date. I realize the plugins system isn't working properly yet in this package, but that has been the case for several releases now and I'm reasonably confident that there are not regressions here from the 4.6.x series that was posted before. Also the entire plugins system is still considered a beta feature upstream, so I don't think we should be holding up otherwise stable releases for it.

That being said a warning to 4.4.x users: If you have plugins configured from that release when they first made their appearance you might move cautiously in upgrading. 4.5 and beyond isn't working as expected in the plugins department.

caleb commented on 2018-02-20 17:06

Just a heads up reminder for myself or @wget where we might see it: not this cycle (4.7.1) but next release, we need to review the systemd service file to based on this PR that got merged: https://github.com/mattermost/mattermost-server/pull/8296

caleb commented on 2018-02-19 10:40

For those wondering why the update delay, Mattermost 4.7.0 has some sort of upgrade migration issue. I looks like some bogus code slipped through their release process. I haven't had time to evaluate the effect on Arch users, but I am kind of holding off packaging this until the hotfix 4.7.1 is out (currently RC1).

Anybody feeling adventurous is welcome to try this from my Github: https://github.com/alerque/aur-mattermost

ArchangeGabriel commented on 2018-01-22 10:24

Tried a clever trick, but it did not work. @wget you have to adopt the package.

wget commented on 2018-01-22 00:37

@caleb Wrt. the API changes, yes acknowledge this would be great if we could provide minimum working examples of NGINX and Apache configurations. Good point for the .pacsave.

But first, in the urgent tasks: I need to fix the plugin issue directory first. For now, plugins (Mattermost addons) don't work on Arch Linux yet.

wget commented on 2018-01-22 00:35

@caleb Great. Thanks. I'll check you changes and merge them if this build.

As for the CI, all is manual for now. This is basically a bunch of LXC scripts (for x84), KVM for x86 on a Proxmox and a real Raspberry Pi 2 for armv6. I run a git clone on them and try to build and launch the installation. I also tested Mattermost on a 512 core armv8 server (thanks to a friend of mine), but I don't have access to this machine any more. I have brand new Raspberry Pi 3 for armv8. I still need to deploy ArchLinux ARM on it though.

In a few weeks, I'll have a completely configured Gitlab with CI and everything will be automated, I'll give you access to it if you want. ;)

Also, on March 1st and March 2, I'll meet Mattermost Inc officials in Portugal. I'll have the ability to discuss a partnership with them for scale Mattermost deployment in Belgium for my company. Will you be there as well since this is a community event? (This depends if you're active upstream as well or not).

wget commented on 2018-01-22 00:28

@mtorromeo Yes you can add caleb as comaintainer as well. Btw, if you do not want to be bothered by us maintaining this package, you can drop it and I'll take its full maintainership and add caleb as comaintainer. ;)

caleb commented on 2018-01-17 08:44

I recently bumped into my Apache config for Mattermost being obsoleted because of the API version change and it wasn't immediately apparent that it was even broken. See https://github.com/mattermost/mattermost-server/issues/8026 for the story.

I'm wondering if including a sample Apache config in this package that could then me managed by pacman's config updates so that people were alerted to changes via .pacnew files when the recommended configuration options changes might not be a bad idea.

caleb commented on 2018-01-17 08:08

@wget. I bumped my repo to 4.6.0 and am running it in production without any issues. How are you handling CI for this by the way?

All comments