-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Binary packages not compatible with Ubuntu 22.04: OpenSSL 3 transition #892
Comments
Thanks for reporting! The latest Ubuntu release has updated to OpenSSL 3, requiring that SSL-using applications like Tectonic link to I had hoped that there would be some kind of compatibility package provided to ease the transition here but it looks like there is not (which is understandable given that this is security-critical infrastructure). So I think that we will need to provide new builds of Tectonic that link to this library. In the meantime, you're going to have to compile Tectonic yourself if you want to use it on Ubuntu 22.04. I'll have to look into how other Rust-based applications are handling this transition. Normally in Rust platform dependencies are encoded in the "target triple" information, but this library dependency doesn't have an obvious mapping into that scheme. note: On my Fedora machine, there are both |
I managed to get cargo to intstall it. And notably, in addtion to the recommended packages-
-and the usual suspects-
-I also had to add-
before it would compile. |
Great! The list of recommended packages already includes |
My bad - Didn't see it in there. I was sure that the install of libssl-dev happened after trying the default packages turned out not to be enough. But looking at my bash history I can see this is not the case. |
I met this problem either. It seems like the |
Same issue on latest master @ abd98d4:
|
Tectonic switched to "semi-static" linking since ab731b8, however it seems that static linking is still not possible as the issue mentioned in the commit message is still yet to be fixed. For those who don't want build tectonic from source, I have had a good experience with the AppImage from the releases page. It only has a dependency on libfuse2 and bundles the rest of tectonic's libraries. |
Just a heads up. OpenSSL 1.1 is no longer supported on Debian Bookworm and later. So there is basically no way for you to run Tectonic without Docker if you own such a system. It would be great if we can move towards OpenSSL 3 to support these systems + the security benefits. |
Basically the only stumbling block here has been that the CI system keys different builds by Rust architecture triplets, and I haven't sat down and devised a scheme to allow me to split But also enough time has passed that most systems probably have OpenSSL 3 at least available at this point, so it's probably high time to switch the default to v3, and the people who need 1.1 can use the MUSL version or compile themselves. |
Yeap, I am all for dropping OpenSSL 1.1. The inertia for someone trying to install OpenSSL 1.1 will be the same as someone installing OpenSSL 3 anyways. |
The last release of openssl 1.x happened now too. So its best to migrate to openssl 3 since version 1 is nearing the EOL (unless you are paying for support I think) |
OK, I now have a PR to just cut the Linux builds over to OpenSSL3 (#1092) — looks like it should basically be straightforward. |
Hi
I'm on a fresh ("full feature") install of Ubuntu 22.04 LTS 64-bit. Downloading the latest relase gives an error when I try to run it.
It looks like an unmet dependency, but one that I am unable to resolve.
edit: I seem to have a package called
libssl3
already installed, if that helps.The text was updated successfully, but these errors were encountered: