This issue needs further fixing in order for the charm to work on Jammy. At present the charm pins cryptography<3.4 in order to avoid the Rust build time dependency.
Actually the package in Ubuntu does something similar but also contains patches to allow cryptography 3.4.x to work with OpenSSL 3.x [0].
In a charms wheelhouse we do not have the luxury or desire to carry patches for Python packages, so I think what we need to do is unpin cryptography and just add the required build dependencies.
Given reactive charms are already compiling C source dependencies avoiding dependencies written in other languages feel artificial to me.
We of course want to stop building source packages on install altogether, but that is a longer canvas to bleach.
This issue needs further fixing in order for the charm to work on Jammy. At present the charm pins cryptography<3.4 in order to avoid the Rust build time dependency.
Actually the package in Ubuntu does something similar but also contains patches to allow cryptography 3.4.x to work with OpenSSL 3.x [0].
In a charms wheelhouse we do not have the luxury or desire to carry patches for Python packages, so I think what we need to do is unpin cryptography and just add the required build dependencies.
Given reactive charms are already compiling C source dependencies avoiding dependencies written in other languages feel artificial to me.
We of course want to stop building source packages on install altogether, but that is a longer canvas to bleach.
0: https:/ /git.launchpad. net/ubuntu/ +source/ python- cryptography/ tree/debian/ patches/ openssl3? h=ubuntu/ jammy