Ok, finally, after many hours of debugging and fixing, we got a jibri package that actually works. :smile:

Most noteably, I switched from tagged "stable" v8 to untagged 99288dc, because the latest stable debian package is built from that commit. After that, things got much better. Sadly,
logging cannot redirected to syslog anymore, because they hardcoded FileHandler everywhere. I might create a PR for that in upstream at a later time.
Also noteable: They switched to a new config file format (HOCON) which is much better. The old config.json format is still supported, but since the new format supports substitutions similar to those in pom files, it is much more convenient.

Tested on a separate fresh fc32 with both recording and youtube streaming. Works even behind NAT.

The necessary config changes for jitsi-meet, jitsi-prosody and jicofo will follow in a separate PR.

Well. not quite there yet. 😞
On fc32 everything works well, but on fc33 there is a different ffmpeg version which apparently does not behave properly when killed with SIGINT. So when terminating a recording or YT-stream jibri detects a failure. Among other side-effects, this prevents creation of the metadata file in the recording directory and does not call the finalize-script. I might have a workaround involving an additional wrapper script for ffmpeg, but no definitive result yet.
Still, it would be nice if you could make a release of everything so that all the recent changes get published in the repo.

Ok, that problem with killing ffmpeg on fc33 was not ffmpeg but the java runtime version.
jibri specifically requires a java-8 jre, because they have some rather stupid code to get the PID of a subprocess. It does not work with anything newer.

That said, with the last commit, it now works on fc33 as well.