[opensuse-factory] "no version information available"
Hi All, I just updated TW and got a bunch of warnings each time I run most programs. For example, zypper: zypper: /lib64/libcrypto.so.1.0.0: no version information available (required by /usr/lib64/libzypp.so.1600) zypper: /lib64/libssl.so.1.0.0: no version information available (required by /usr/lib64/libldap-2.4.so.2) zypper: /lib64/libcrypto.so.1.0.0: no version information available (required by /usr/lib64/libldap-2.4.so.2) Looking online this is caused by some VER* metadata in the .so not being present while VERNEED is present in the binary linked against it (the warning comes from GCC). Oddly `rpm -qf` doesn't tell me what package owns /lib64/libcrypto.so.1.0.0 but I figured out that it's OpenSSL. Was there a recent change in the OpenSSL package? Should I file a bug or is this already known? -- Aleksa Sarai Software Engineer (Containers) SUSE Linux GmbH https://www.cyphar.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Oddly `rpm -qf` doesn't tell me what package owns /lib64/libcrypto.so.1.0.0 but I figured out that it's OpenSSL.
`rpm -qf /usr/lib64/libcrypto.so.1.0.0` gave me the right result, but I just checked and I appear to have two different versions of those shared libraries (and /lib64/ takes precedence in LD_LIBRARY_PATH). % file /usr/lib64/libssl.so.1.0.0 /usr/lib64/libssl.so.1.0.0: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=39f08807159eed4df59ed0b85c58663586ebe97e, with debug_info, stripped % file /lib64/libssl.so.1.0.0 /lib64/libssl.so.1.0.0: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=c37f657813861d6fe764a5d485b8fc423b7d69f3, with debug_info, stripped So it looks like a classic PEBKAC case. ;) -- Aleksa Sarai Software Engineer (Containers) SUSE Linux GmbH https://www.cyphar.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Aleksa Sarai
Hi All,
I just updated TW and got a bunch of warnings each time I run most programs. For example, zypper:
zypper: /lib64/libcrypto.so.1.0.0: no version information available (required by /usr/lib64/libzypp.so.1600) zypper: /lib64/libssl.so.1.0.0: no version information available (required by /usr/lib64/libldap-2.4.so.2) zypper: /lib64/libcrypto.so.1.0.0: no version information available (required by /usr/lib64/libldap-2.4.so.2)
Looking online this is caused by some VER* metadata in the .so not being present while VERNEED is present in the binary linked against it (the warning comes from GCC). Oddly `rpm -qf` doesn't tell me what package owns /lib64/libcrypto.so.1.0.0 but I figured out that it's OpenSSL.
maybe because there is no /lib64/libcrypto.so.1.0.0, it is id /usr/lib64 and /usr/lib
Was there a recent change in the OpenSSL package? Should I file a bug or is this already known?
rpm -q --last openssl openssl-1.0.2k-4.1.noarch Mon 22 May 2017 08:16:39 AM EDT -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, May 26, 2017 at 01:46:22PM +1000, Aleksa Sarai wrote:
Hi All,
I just updated TW and got a bunch of warnings each time I run most programs. For example, zypper:
zypper: /lib64/libcrypto.so.1.0.0: no version information available (required by /usr/lib64/libzypp.so.1600) zypper: /lib64/libssl.so.1.0.0: no version information available (required by /usr/lib64/libldap-2.4.so.2) zypper: /lib64/libcrypto.so.1.0.0: no version information available (required by /usr/lib64/libldap-2.4.so.2)
Looking online this is caused by some VER* metadata in the .so not being present while VERNEED is present in the binary linked against it (the warning comes from GCC). Oddly `rpm -qf` doesn't tell me what package owns /lib64/libcrypto.so.1.0.0 but I figured out that it's OpenSSL.
Was there a recent change in the OpenSSL package? Should I file a bug or is this already known?
The packaging was restructured, so this could be from there. If rpm -qf no longer associates the /lib64/libcrypto.so.1.0.0 package to an RPM, delete it. It should have been removed automatically though. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Aleksa Sarai -
Marcus Meissner -
Patrick Shanahan