Package Details: jitsi-meet-desktop 2025.2.0-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://github.com/jitsi/jitsi-meet-electron
Licenses: Apache-2.0
Submitter: SamWhited
Maintainer: xiota
Last Packager: xiota
Votes: 31
Popularity: 0.35
First Submitted: 2020-04-10 13:16 (UTC)
Last Updated: 2025-02-13 23:19 (UTC)

Dependencies (3)

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

smw commented on 2021-12-06 16:32 (UTC) (edited on 2021-12-06 16:41 (UTC) by smw)

2021.12.2-1 fails to build, with

 Warning: cannot resolve "electron>=16.0.4", a dependency of "jitsi-meet-desktop"

...but the most recent available version of electron16-bin is 16.0.1-1. Help?

lsf commented on 2021-12-06 09:50 (UTC)

Yep, that seems to be an odd error with nvm. Thanks for reminding me to open a PR there! (https://github.com/nvm-sh/nvm/pull/2678).

aorth commented on 2021-12-03 12:04 (UTC) (edited on 2021-12-06 13:31 (UTC) by aorth)

2021.11.2-1 doesn't build in a chroot (aur build -c):

==> Extracting sources...
  -> Extracting jitsi-meet-desktop_2021.11.2.tar.gz with bsdtar
==> Starting prepare()...
Downloading and installing node v14.18.2...
Binary download failed, trying source.
==> ERROR: A failure occurred in prepare().
    Aborting...
==> ERROR: Build failed, check /var/lib/aurbuild/x86_64/aorth/build

smw commented on 2021-11-12 18:27 (UTC) (edited on 2021-11-12 18:27 (UTC) by smw)

Yes, I can also confirm that 2021.11.2-1 installs cleanly. Thank you!

shavenne commented on 2021-11-12 14:05 (UTC)

I can confirm that it's working now. Had the same problem. Thank you!

lsf commented on 2021-11-12 13:04 (UTC)

=> should be fixed now @smw.

smw commented on 2021-11-12 00:19 (UTC) (edited on 2021-11-12 00:21 (UTC) by smw)

I tried to update to jitsi-meet-desktop_2021.11.1 today, but the update failed with these messages:

17573 error /sbin/git ls-remote -h -t ssh://git@github.com/jitsi/eslint-config-jitsi.git
17573 error 
17573 error ssh_askpass: exec(/usr/lib/ssh/ssh-askpass): No such file or directory
17573 error Host key verification failed.
17573 error fatal: Could not read from remote repository.
17573 error 
17573 error Please make sure you have the correct access rights
17573 error and the repository exists.

It's true that my system has no /usr/lib/ssh/ssh-askpass; if that's required, shouldn't there be a dependency on openssh-askpass or equivalent?

...but just for fun I ran the git command manually, and it still failed:

% /sbin/git ls-remote -h -t ssh://git@github.com/jitsi/eslint-config-jitsi.git
The authenticity of host 'github.com (140.82.112.4)' can't be established.
RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'github.com' (RSA) to the list of known hosts.
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.

je-vv commented on 2021-09-05 22:11 (UTC)

I rebuilt with 14, and it's working back. Not sure if it was a temporal out of service somewhere. Thanks a lot !

lsf commented on 2021-09-05 10:41 (UTC)

@je-vv

That's… odd (because I only ever had that "hanging, issue before when running nvm install (or use) during package building when already in a directory with an .nvmrc and running the nvm sourcing there, but hadn't had it for ages).

With your modifications, I'd assume it will fall back to npm 12 (as specified in the .nvmrc – which shouldn't hurt, so if it works, that's fine.

Alternatively, it might be worth trying to do the cd jitsi-meet-electron-${pkgver} only after the nvm commands (and _ensure_local_nvm are run) as a workaround.

I'll see if I can find out the root cause, though, as that's probably better than trying to find workarounds ;)

nvm install or use with a major version only shouldn't cause the issue, but admittedly I cannot recall why I went and set it to 14 in the first place instead of using the "predetermined" one in the .nvmrc (12). There probably was some reason ;)

je-vv commented on 2021-09-05 09:46 (UTC)

BTW, by changing:

nvm install 14

To:

nvm install

And, by removing:

nvm use 14

The build process doesn't hang any more. Not sure if the right thing to do, but it works, :) I guess the "nvm use 14" had to be removed, since "nvm install 14" doesn't really works out. Besides, the "nvm use" is not documented on:

https://wiki.archlinux.org/title/Node.js_package_guidelines#Using_nvm

Even though a full version is exemplified there...

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »