https://www.debian.org/releases/trixie/release-notes/upgrading.en.html#start-from-pure-debian The upgrade process described in this chapter has been designed for “pure” Debian stable systems. APT controls what is installed on your system. If your APT configuration mentions additional sources besides bookworm, or if you have installed packages from other releases or from third parties, then to ensure a reliable upgrade process you may wish to begin by removing these complicating factors.
And, not Debian, but (so, beyond this point, should probably refer to Jitsi for support): https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-quickstart/ Debian 11 (Bullseye) or newer Note OpenJDK 17 must be used And as for Debian: $ cat /etc/debian_version && apt-cache search openjdk | sed -ne 's/^\(openjdk-[0-9]\{2\}\).*/\1/p' | sort -u 13.2 openjdk-21 openjdk-25 $ $ cat /etc/debian_version && apt-cache search openjdk | sed -ne 's/^\(openjdk-[0-9]\{2\}\).*/\1/p' | sort -u 12.12 openjdk-17 $ So, there you have it, per Jitsi's documentation, it's not (yet) compatible with Debian 13, the current stable, but is compatible with Debian 12, the current oldstable which is still supported on main support through 2026-06-10, after that, there's LTS, and then ELTS. As to why Jitsi doesn't (yet) support OpenJDK 21 or 25, that would be a question for Jitsi. On Sat, Dec 27, 2025 at 2:54 PM Gary Dale <[email protected]> wrote: > > I'm trying to reinstall Jitsi-meet on my server after purging it (an > attempt to correct connection issues). While is was somewhat working > (and often working well) for several years, now it is refusing to install: > > # apt install jitsi-meet > Solving dependencies... Error! > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > Unsatisfied dependencies: > jicofo : Depends: openjdk-11-jre-headless but it is not installable or > openjdk-11-jre but it is not installable or > openjdk-17-jre-headless but it is not installable or > openjdk-17-jre but it is not installable > jitsi-videobridge2 : PreDepends: openjdk-11-jre-headless but it is not > installable or > openjdk-11-jre but it is not > installable or > openjdk-17-jre-headless but it is not > installable or > openjdk-17-jre but it is not installable > Error: Unable to correct problems, you have held broken packages. > Error: The following information from --solver 3.0 may provide > additional context: > Unable to satisfy dependencies. Reached two conflicting decisions: > 1. libpam-runtime:amd64 is selected for install because: > 1. util-linux:amd64 is selected for install > 2. util-linux:amd64 PreDepends libpam-runtime > 2. libpam-runtime:amd64 Depends debconf (>= 1.5.19) | cdebconf > but none of the choices are installable: > - debconf:amd64 is selected for removal > - cdebconf:amd64 Depends debconf > but none of the choices are installable: > - debconf:amd64 is selected for removal > > > apt-mark showhold shows no packages being held. > > I can't install openjdk-11 or -17 because they are not available on > Trixie. Jitsi-meet won't install with openjdk-21, the earliest version > available on Trixie. > > I have no idea what the other messages are complaining about. apt > install <any of them> tells me they are already the latest version. > > Apparently the issue is that Jitsi hasn't been updated to work with a > non-obsolete version of JDK. There are complaints about this from others > as no rational distribution is still using 17, let alone 11. > > I think that Debian automatically held JDK 17 when I upgraded to Trixie > but even that led to problems with Jitsi. I have no idea why the Jitsi > developers haven't provided an update yet, but right now Jitsi is not > installable on Trixie. >
