Arch Linux User Repository

This package won't build any more since it depends on an outdated Electron version, and I think there is not much we can do about that here. I have filed a bug report upstream, so let's wait and see. The binary package rocketchat-client-bin should still work though.

@r0b0t This currently doesn't work with nodejs>=13 due to node-spellchecker which is pretty much unmaintained.

I'm not sure why your build errors though. There are nodejs packages for version 8, 10 and 12. Are you running makepkg or using AUR helper?

Edit: I will replace the current nodejs version pinning with nodejs-lts-erbium as soon as I get some feedback on this issue: https://bugs.archlinux.org/task/64641

warning: nodejs-13.2.0-1 is up to date -- skipping there is nothing to do error: unable to satisfy dependency 'nodejs<13' required by rocketchat-desktop

Can we have this work with nodejs > 13?

My system is up to date as I'm writing.

@Polly I can not reproduce this. Build works fine without eslint. The warning comes from upstream and doesn't affect the application at all.

On my machine (up to date on 2019/11/1) the build got stuck while rebuilding packages. Installing eslint solved the issue. Also there is the warning:

warning " > @rocket.chat/eslint-config@0.4.0" has incorrect peer dependency "eslint@^4.19.1 || ^5.16.0".

Is there a missing dependency?

Just pushed an update to fix build with electron 7.

• https://github.com/atom/node-spellchecker/issues/127
• https://github.com/atom/node-spellchecker/pull/128

Finally got rid of the python2 dependency. node-gyp works fine with python now.

Had to pin nodejs version to 12 because it doesn't build with 13 (which is in community-testing right now)

Updated to 2.15.5. Please excuse the delay, there were some issues upstream.

To build this nodejs<12 is now required. Version 12 is in community-testing right now and breaks the build due to a dependency. I have created an issue upstream https://github.com/anaisbetts/node-system-idle-time/issues/17

Hopefully this will be resolved soon. If it is not the case, I'll recreate the issue in the rocketchat repository.

The notification timeout works fine in the new version... I guess it's fixed by ignoring the issue. :)

Hello my dudes. So there we go 2.15.0 is out. The notifications timeout patch is gone and hopefully all the related issues as well.

Now depends on electron (3) instead of electron2. This is good, but might not quiet perfect since upstream actually wants electron 4(!).

As you can see in the PKGBUILD, I downgraded to electron@^3.1.4, because I noticed at least one thing that was broken. Looks like 4 is not fully backwardscompatible.

@Turtizzle

I didn't know what to answer or what to do. But today I saw this merged pull request arrive:

https://github.com/RocketChat/Rocket.Chat.Electron/pull/1101

This might actually solve all the notification issues. Let's hope it does.

@matthias.lisin That's weird, I am using xfce4-notifyd and have a default timeout of 10 seconds configured, which works fine when I test it with notify-send. My rocketchat messages do not disappear though... and it used to work when I was still testing it with the hardcoded 10 seconds patch.

Honestly, the behavior I'd prefer is having a single notification that adapts when new messages arrive, similarly to how smartphones tell you about consecutive messages... or have notifications automatically disappear when you read the respective messages in RocketChat... but that's a larger issue. As for what do do now, I suppose that's up to you. You can always make it configurable in the PKGBUILD for people who prefer it differently, if you want... that's what we build packages from source for. :P