-
Notifications
You must be signed in to change notification settings - Fork 255
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
Installer fails on Fedora Silverblue #962
Comments
Hi @evenreven, assuming that package makes the shared lib files available, then yeah, it should be safe to install using the tarball. Most likely the standard (non-RHEL) one would be the appropriate one, we create a special RHEL package because RHEL rolls their own OpenSSL version that uses a different SONAME value from the stock OpenSSL tree. If using the tarball, you'll need to replicate what the install script does, which primarily is:
The last step there will modify your shell's startup scripts to include Volta on the PATH, so it should prompt you afterwards to open a new terminal. For more details, the process is described under "Custom Installers" in the Installer Docs. |
Thanks for the lightning-fast response! I actually prefer installing from tar balls and setting up the zshrc stuff myself, so no trouble there. I'll go for the regular openssl 1.1. 👍 (Also tempted to start a thread on discussion.fedoraproject.org to ask some more knowledgeable people why it's like this, but that's no big rush.) |
I did some digging, and Fedora has split openssl into two packages, Since Silverblue is immutable and you can't easily remove base packages, the maintainers err on the side of minimalism, so they include only the -libs package (the same is true on the podman fedora image). Both are probably there on Fedora (don't have it handy to check, though). It's a niche distro (for now), so I'm used to applying elbow grease and doing stuff manually. But is it doable to check for the existence of openssl without using the output of the PS: I tried actually using Volta after a manual install. Works really well, thanks for writing this! |
@evenreven Thanks for digging in a bit! I suspect we may be able to detect the openssl version without using the So glad you're enjoying Volta despite the difficulties! |
What's the status here, @charlespierce @evenreven? I do not personally use or work with Fedora, so do not have any visibility here. I think our work to switch over to rustls in #1214 should have helped? |
I believe the switch to Rustls (and the associated change to the installer) should have resolved this. We no longer depend on OpenSSL at all and so shouldn’t have any concerns about differing versions.
…On Tue, Dec 19, 2023, at 6:02 PM, Chris Krycho wrote:
What's the status here, @charlespierce <https://github.com/charlespierce> @evenreven <https://github.com/evenreven>? I do not personally use or work with Fedora, so do not have any visibility here. I think our work to switch over to rustls in #1214 <#1214> should have helped?
—
Reply to this email directly, view it on GitHub <#962 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AENNW7X5O7ZZ2WCSWM5QY6TYKJBLPAVCNFSM4ZDBJCW2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBWGM3TGNRYGI3A>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Excellent! 🎉 I am going to go ahead and close this accordingly, and ask folks to open new issues if they have similar issues. |
Looks like Silverblue doesn't actually have an executable named
openssl
. There's a package calledopenssl-libs-1.1.1i-3.fc33.x86_64
, but it doesn't provide an executable. Would that be a problem actually using Volta, or is it only a problem for the installer shell script? Can I safely install thevolta-1.0.2-linux-openssl-1.1.tar.gz
archive instead? I noticed there's a RHEL openssl version, but I assume Silverblue (which is an immutable/ostree-based Fedora spin) shouldn't use this?The text was updated successfully, but these errors were encountered: