David Crook

It is a strange situation. It looks like the package `libssl1.1` is being removed from jammy (22.04). see, e.g. it is not found for jammy. ```console $ apt search libssl...

BTW, `espanso` builds and runs successfully on same (Ubuntu 22.04 beta) host when following the compiling instructions from:

Something else I have just determined. Building the .deb on 22.04 beta host obviates the dependency. Building the .deb-s on fresh clone (using [build_deb.sh](https://github.com/federico-terzi/espanso/blob/master/.github/scripts/ubuntu/build_deb.sh) as guide), the dependency that caused...

> ### The locally built .deb: > ``` > $ dpkg-deb --field target/debian/espanso-wayland_2.1.5-beta_amd64.deb Depends > libc6 (>= 2.34), systemd, libxkbcommon0, libxkbcommon0 (>= 0.5.0), libnotify-bin, libwxgtk3.0-gtk3-0v5 (>= 3.0.5.1+dfsg), libwxgtk3.0-gtk3-0v5, wl-clipboard, libssl3...

In Ubuntu 22.04 jammy jellyfish `libssl1.1` has been superceded by `libssl3`. When Jammy is released, the following files for espanso release will be affected for this to be handled appropriately...

> I would really prefer finding a way to support both without forking the build process... Cheers :) I see your point. There could be a way to update the...

changed title as Ubuntu 22.04 has been released

>There could be a way to update the dependency to accept libssl1.1 or libssl3? I don't know enough about the capabilities there. The rust crate for building the deb's is...

> "downgrade Werkzeug" Is there a quick and dirty way I can do this in a `requirements.txt` file that needs to use version 4? It is pinning latest 4.x version...

> > "downgrade Werkzeug" > > Is there a quick and dirty way I can do this in a `requirements.txt` file that needs to use version 4? It is pinning...