Package Details: jitsi-meet-desktop 2023.11.3-1

Git Clone URL: https://aur.archlinux.org/jitsi-meet-desktop.git (read-only, click to copy)
Package Base: jitsi-meet-desktop
Description: Jitsi Meet desktop application
Upstream URL: https://jitsi.org/jitsi-meet/
Keywords: chat IM video
Licenses: Apache
Conflicts: jitsi-meet-electron, jitsi-meet-electron-bin
Replaces: jitsi-meet-electron
Submitter: SamWhited
Maintainer: samsapti
Last Packager: samsapti
Votes: 29
Popularity: 0.012209
First Submitted: 2020-04-10 13:16 (UTC)
Last Updated: 2023-11-25 17:08 (UTC)

Latest Comments

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

xiota commented on 2023-09-20 07:54 (UTC) (edited on 2023-11-20 19:01 (UTC) by xiota)

Please remove replaces directive, in accordance with AUR submission guidelines.

cedricroijakkers commented on 2023-09-13 08:01 (UTC)

As mentioned on the Jitsi Github, there is currently an issue with version 2023.9.0 that in some cases the application crashes with a blank screen.

There is a workaround: change all mentions of electron26 to electron25 in the PKGBUILD to get it working again. The bug upstream will be fixed at some point, but until then build against Electron v25 or do not upgrade.

samsapti commented on 2023-07-18 14:02 (UTC)

@je-vv thanks for making me aware of that. @joru thanks for the fix!

joru commented on 2023-07-18 09:10 (UTC)

I created a fixed version of the patch file, just needs to be included

je-vv commented on 2023-07-18 00:24 (UTC) (edited on 2023-07-18 00:27 (UTC) by je-vv)

The patch is failing on prepare stage, with 2023.7.2-1:

==> Starting prepare()...
Found '/home/general/.pkgs/src/laur/jitsi-meet-desktop/src/jitsi-meet-electron-2023.7.2/.nvmrc' with version <16>
v16.20.1 is already installed.
Now using node v16.20.1 (npm v8.19.4)
patching file package.json
Hunk #1 FAILED at 27.
Hunk #2 FAILED at 63.
2 out of 2 hunks FAILED -- saving rejects to file package.json.rej
==> ERROR: A failure occurred in prepare().
Aborting...

samsapti commented on 2023-02-18 11:22 (UTC) (edited on 2023-02-18 11:23 (UTC) by samsapti)

@je-vv the webpack dependency is specified in upstream's package.json, so I can't change that.

The Electron download thing is probably because I forgot to change the Electron directory. I've fixed that.

Upstream requires Electron 21.

je-vv commented on 2023-02-18 02:55 (UTC)

Also, is this necessary?

  • downloading     url=https://github.com/electron/electron/releases/download/v22.0.3/electron-v22.0.3-linux-x64.zip size=93 MB parts=8
  • downloaded      url=https://github.com/electron/electron/releases/download/v22.0.3/electron-v22.0.3-linux-x64.zip duration=12.432s

Can system electron be used instead? BTW, it's weird it's packaging electron 22 at the end, while it was built with electron 21. Perhaps it's possible to build it with 22... But more importantly is why downloading electron...

je-vv commented on 2023-02-18 02:45 (UTC) (edited on 2023-02-18 02:46 (UTC) by je-vv)

Got it @samsapti, yeap current electron is 22, but if required by upstream it's fine.

Can this package be made dependent on a provider of nodejs-webpack, currently nodejs-webpack-cli (full) and nodejs-webpack (just the module I'd guess) are, and then stop downloading and using webpack while building this package? Both mentioned providers are on AUR BTW.

samsapti commented on 2023-02-17 18:29 (UTC)

@je-vv I've pinned electron21 as a dependency, because the devs have downgraded it due to an issue. I've adopted the package btw.

je-vv commented on 2022-11-05 07:53 (UTC)

@lsf, could you please update the electron used to be electron20, I see no issue with that. Thanks !