Coturn is a package written in a not memory safe language, very complex with tons of options, and a such has already suffered quite a few security vulnerabilities. It’s possible to rebuild a Coturn package from the latest source (21.10) by patching the package of course (the fix is in the Ubuntu bug I filed), but it’s more involved and much worse, there is the problem of security vulnerabilities to follow up. This does not install Coturn of course, but at least it does not install Nginx AND Apache2. Sudo apt install default-jre jitsi-meet -no-install-recommends So the final Ubuntu 22.04 installation magic command is: If people want newer Java they can install it explicitly.Ĭoturn: there is no workaround, other than asking to not install it. In fact I’d say that if Jitsi-meet devs love old things (when it’s Java, for other systems it’s the opposite), changing the package dependency to default-jre could be the best option. Just the one Jitsi-meet love to install and advise. This is peculiar because the jitsi-meet is asking to install java8 OR java11 and the result is tha the latest Java is installed (Java 17 for Ubuntu 20.04 for instance).īut asking for default-jre will install Java 11. Java 18: explicitly install a previous Java version Same things as Java, Debian is managing this package and has not upgraded OpenSSL in latest unstable, so no problem for Debian. This lack of Coturn is something Jitsi-meet packages have not envisioned it seems. Jitsi-meet installation can go on without Coturn, but of course Coturn functionality is missing, and as an added fun, Nginx AND Apache are both installed. Openssl 3.01: Coturn can’t compile out of the box under Openssl 3 and as such the package has been dropped.Package ca-certificates-java is not configured yet.ĭpkg: error processing package openjdk-18-jre-headless:amd64 (-configure):ĭependency problems - leaving unconfiguredĮrrors were encountered while processing:Į: Sub-process /usr/bin/dpkg returned an error code (1) Openjdk-18-jre-headless:amd64 depends on ca-certificates-java (>= 20190405~) however: Installed ca-certificates-java package post-installation script subprocess returned error exit status 127ĭpkg: dependency problems prevent configuration of openjdk-18-jre-headless:amd64: var/lib/dpkg/info/ca-certificates-java.postinst: line 101: java: command not foundĭpkg: error processing package ca-certificates-java (-configure): Head: cannot open '/etc/ssl/certs/java/cacerts' for reading: No such file or directory And installing jitsi-videobridge2 is one of these unhappy circonstnaces that are causing this installation inversion. However, these packages are managed by Debian teams and Debian has not upgraded to Java 18 even on the unstable version (Sid/Bookworm). That’s why (I guess) there is a strange path setting loop in the ca-certificates-jave postinst to find the appropriage Java to run. Usually Java gets installed first (no idea why), but some combination of circonstances can make that ca-certificates-java is installed before Java is fully configured. It seems that it is making the order of installation between these 2 packages not deterministic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |