Package Details: mattermost-desktop 4.2.0-1

Git Clone URL: https://aur.archlinux.org/mattermost-desktop.git (read-only)
Package Base: mattermost-desktop
Description: Mattermost Desktop application for Linux (Beta)
Upstream URL: https://github.com/mattermost/desktop
Keywords: chat mattermost messenger networking slack
Licenses: Apache
Submitter: nineinchnick
Maintainer: akstrfn (wget)
Last Packager: wget
Votes: 41
Popularity: 1.912051
First Submitted: 2016-04-02 09:08
Last Updated: 2018-11-29 20:30

Latest Comments

1 2 3 4 5 Next › Last »

wget commented on 2018-12-16 17:13

@ocelot Could you please remove your pacaur cache ~/.cache/pacaur and see if this fix the issue? You problem is likely due to your aur helper (pacaur) as this package is working nicely when built without using an AUR helper. Could you stop using pacaur altogether, as it isn't maintained any more: https://wiki.archlinux.org/index.php/AUR_helpers#Pacman_wrappers.

ocelot commented on 2018-12-13 21:54

@wget I think it is a conflict or issue that this package has when building on a system that uses Node Version Manager. Even though I cleared the cache for this too, it still didn't work.

wget commented on 2018-12-08 15:10

@ocelot Sorry to hear that. I have just tested on a bare ArchLinux install and I wasn't able to reproduce. See for yourself: https://gist.github.com/wget/c86a38f970d60956b52a7544ff98e793 The patch is applied with successful and the build process continues without issue. The final application package can be installed and is running flawlessly. Even if this shouldn't have conflicts, make sure you remove your npm cache ~/.npm and that your ArchLinux distribution is up to date before trying to build this package. Feel free to reach us on IRC if you want further help. :)

ocelot commented on 2018-12-04 22:51

I am getting a build error - it seems like your patch in "mattermost-package-json.patch" to update the versions of webpack and webpack-cli is no longer applying, and is getting overwritten.

TypeError: Cannot read property 'properties' of undefined
    at module.exports (/home/ocelot/.cache/pacaur/mattermost-desktop/src/desktop-4.2.0/node_modules/webpack-cli/bin/config-yargs.js:89:48)
    at /home/ocelot/.cache/pacaur/mattermost-desktop/src/desktop-4.2.0/node_modules/webpack-cli/bin/webpack.js:60:27
    at Object.<anonymous> (/home/ocelot/.cache/pacaur/mattermost-desktop/src/desktop-4.2.0/node_modules/webpack-cli/bin/webpack.js:515:3)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:742:12)
    at startup (internal/bootstrap/node.js:266:19)

wget commented on 2018-11-29 20:31

Package updated. We are running into issues upstream. The deb system becomes quite outdated. This Arch Linux package is patching it on the fly. Will be upstreamed soon.

ArchangeGabriel commented on 2018-07-03 17:04

Well sha256 was not in my detailed proposition, because I don’t specially advocate it. It’s just that sha512 does not bring much more, while making way longer lines.

And of course string quotation is a matter of taste (just like $var vs ${var} is when there is no issue using the former), it’s just that I prefer to see explicitly where there might be issues without quotes (which is an inconsistent reasoning with my preference for ${var}, but eh, I’m just another strange human after all). ;)

wget commented on 2018-07-03 16:56

Thanks a lot ArchangeGabriel for this kind review.

I applied your changes except two: sha and (a bit like akstrfn) string quotations. I indeed prefer to quote the whole string because my brain sees it more clearly this is a string.

I still have kept i686 and arm support for this package.

akstrfn commented on 2018-06-20 20:53

I noticed that riot also has blurry icon but anyway I tried googleing around and reading electron docs to figure it out. I had an impression that it can be solved with js launcher instead of bash launcher. Good that you told me that it is a known bug ;)

ArchangeGabriel commented on 2018-06-20 20:39

I guessed something like that for the *, but since we removed tools to build as i686, I did not investigate further.

The tray icon is not a Mattermost issue, all electron apps have blurry icons in KDE systray (riot.im, cozy-desktop, slack-desktop…). It’s an electron/KDE issue, nothing you can fix in the PKGBUILD.

akstrfn commented on 2018-06-20 20:36

Thanks for the tips @ArchangeGabriel. * in cp line is there for the i686 build since you have something like linux-i32-unpacked or something similar in that arch.

I like to quote the whole path, instead of just e.g. {pkgdir} since it looks nicer to me, but its a matter of taste :)

There is one problem with the current build that I didn't explore further. The tray icon in my KDE system is blurry. I didn't figure out how to fix that when launching with shared electron binary.