Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#53457 - [steam-native-runtime] Needs lib32-openssl-1.0
Attached to Project:
Community Packages
Opened by AaronP (Bellum) - Sunday, 26 March 2017, 03:47 GMT
Last edited by Maxime Gauduin (Alucryd) - Friday, 26 May 2017, 09:36 GMT
Opened by AaronP (Bellum) - Sunday, 26 March 2017, 03:47 GMT
Last edited by Maxime Gauduin (Alucryd) - Friday, 26 May 2017, 09:36 GMT
|
DetailsWith Arch moving to 1.1, steam is going to need a lib32-openssl-1.0 package.
|
This task depends upon
Closed by Maxime Gauduin (Alucryd)
Friday, 26 May 2017, 09:36 GMT
Reason for closing: Fixed
Additional comments about closing: 1.0.0.54-3
Friday, 26 May 2017, 09:36 GMT
Reason for closing: Fixed
Additional comments about closing: 1.0.0.54-3
Comment by Daniel M. Capella (polyzen) -
Sunday, 26 March 2017, 06:06 GMT
Worked fine for me?
Comment by AaronP (Bellum) -
Sunday, 26 March 2017, 22:51 GMT
Sorry, I meant the runtime needs it. The Steam client doesn't need it, but games linking to libcrypto.so.1.0.0 do.
Comment by Kevin Dodd (Jesin) -
Tuesday, 28 March 2017, 00:57 GMT
I have also run into this problem. For 64-bit binaries that require libcrypto.so.1.0.0, the openssl-1.0 package does exactly what I need. But I also have some binaries that require the 32-bit version of the library, and the lack of a lib32-openssl-1.0 package has forced me off of multilib-testing.