Package Details: jitsi-meet 1.0.4628-1

Git Clone URL: (read-only, click to copy)
Package Base: jitsi-meet
Description: WebRTC JavaScript video conferences
Upstream URL:
Licenses: Apache
Submitter: fordprefect
Maintainer: fordprefect (C0rn3j)
Last Packager: C0rn3j
Votes: 5
Popularity: 0.67
First Submitted: 2020-04-22 09:00
Last Updated: 2021-02-04 01:36

Latest Comments

celogeek commented on 2020-05-26 23:56


I have several remarks:

  • jitsi-meet should be named like the upstream: jitsi-meet-web
  • the package copy the whole content instead of the compiled version exposing through nginx/apache files that should not be there
  • the package should follow the upstream and be installed in /usr/share/jitsi-meet
  • the package missing part of the installation: countries-*.js in lang/
  • the package should place like the upstream config in /etc/jitsi/meet (interface_config.js logging_config.js config.js) in order for the user to know what it can update and have a handy example

Jitsi gives the command: "make source-package" to bundle the result and deploy it on the system. Can you use it?

A complete example can be found here:

Can you integrate those changes?

TheGoliath commented on 2020-05-22 20:17

jitsi-meet/src/jitsi-meet-jitsi-meet_4548: No such file or directory

Change the PKGBUILD as archtom has already pointed out in order to get things working again

archtom commented on 2020-05-03 17:02

@fordperfekt: The PKGBUILD needs changes to work.

In build and in package ${pkgname}-${_tag} needs to be ${pkgname}-stable-${_tag}. Same in the jicofo package.

Would be nice if you could change the install dirs to /etc/jitsi/meet and /etc/jitsi/jicofo to match the original bin packages and avoid install/config confusion.

Furthermore it would be nice if the jicofo package could use the config and service file from jicofo-git for the same reason.

Additionally it seems they have released two stable versions on the same day. I guess there was something wrong with the first one. Would be nice to include the updated version in the next package update.


@C0rn3j: Thanks, plugin_paths seems to do the trick ;)

C0rn3j commented on 2020-05-02 15:20

@archtom You should be able to point prosody at the plugins folder. plugin_paths = { "/opt/jitsi-meet/resources/prosody-plugins/" }

(as per my email, posting here so it's visible)

@fordprefect Could you also add me as a comaintainer here and jicofo? Jicofo and JVB need some config changes because of JVB2 migration and because I'm fixing up the service files and paths to be identical with the upstream debian packages, and I'd like to do be able to do it for both at the same time.

archtom commented on 2020-05-02 08:51

@fordprefect: Thanks for updating the packages. Could you please add copying the jitsi-meet prosody plugins from the unzipped dir (or after install from /opt/jitsi-meet/resources/prosody-plugins/*) to /usr/lib/prosody/modules/. They are needed for the latest and recommended configurations. Thanks

archtom commented on 2020-04-23 22:39

I downloaded the PKGBUILDs of all the packages and found the problem with this one.

Changing the build part back to the one below makes everything work, and I also changed back to the latest stable 4025 without problems.

cd "${srcdir}/${pkgname}-${pkgver}"

npm install

make -j1

Trying npm install -g --user root --prefix or npm audit fix both make me ran in different problems and issues that I only could solve partially. There was no combination of them where I got it to work. The official website also suggests only doing the working commands above.

archtom commented on 2020-04-23 10:28

It seems they list/release the stable versions here. You find the link on their website.;O=D

It would be very nice if you could upgrade/downgrade all your packages (meet, videobridge, jicofo and jigasi) to these version numbers. Thanks a lot.

archtom commented on 2020-04-22 21:24

Thanks for the update. I'm also interested in using a "stable" release cycle.

fordprefect commented on 2020-04-22 20:57

thanks for trying. I bumped to the newest release, but due to the ridiculous release scheme I'm not quite sure which of these to actually use. I've contacted the jitsi dev team to clarify and will adapt the packages accordingly.

archtom commented on 2020-04-22 19:23

hey, thanks for the Jitsi packages. Unfortunately 4041 installs fine but does not work giving some java exceptions and only showing a gray screen. 3093 worked in the first version submitted. I did not test the second one.