The libssh package uses wildcards on SONAME version. The package was upgraded from 0.7.5 to 0.8.1 in Fedora 27+ that included a SONAME bump.
Please remove the wildcard in libssh and begin package rebuilds. Stable versions of Fedora now contain broken software as the package has been released to stable.
Thanks, Michael
On Fri, Aug 17, 2018 at 08:19:17AM -0500, Michael Cronenworth wrote:
The libssh package uses wildcards on SONAME version. The package was upgraded from 0.7.5 to 0.8.1 in Fedora 27+ that included a SONAME bump.
Please remove the wildcard in libssh and begin package rebuilds. Stable versions of Fedora now contain broken software as the package has been released to stable.
This soname change only appears to have affected the libssh_threads.so library, which was replaced by a back-compat hack which appears to not be correct. The normal libssh.so library appears unchanged
In 0.7.5 we have
/usr/lib64/libssh.so.4 /usr/lib64/libssh.so.4.4.2
# eu-readelf -a /usr/lib64/libssh.so.4 | grep SONAME SONAME Library soname: [libssh.so.4] # eu-readelf -a /usr/lib64/libssh_threads.so.4 | grep SONAME SONAME Library soname: [libssh_threads.so.4]
While in 0.8.1 we have
/usr/lib64/libssh.so.4 /usr/lib64/libssh.so.4.5.1
# eu-readelf -a /usr/lib64/libssh.so.4 | grep SONAME SONAME Library soname: [libssh.so.4] # eu-readelf -a /usr/lib64/libssh_threads.so.4 | grep SONAME SONAME Library soname: [libssh.so.4]
Regards, Daniel
Le ven. 17 août 2018 à 16:05, Michael Cronenworth mike@cchtml.com a écrit :
The libssh package uses wildcards on SONAME version. The package was upgraded from 0.7.5 to 0.8.1 in Fedora 27+ that included a SONAME bump.
I don't see any SONAME bump libssh.so.4 is still used in both packages version in f28 at least.
That been said, there are some unusual things with libssh_threads.so.4 merged with libssh.so.4 Some packages that are failing still uses libssh_threads.so.4 (1)
The failure seems caused by a missing symlink from libssh_threads.so.4 to the real library (using libssh.so.4 SONAME) That was with libssh-0.8.1-3.fc28.x86_64. According to rpm -V libssh, seems like the symlink is correctly present in the package and was corrupted on the filesystem. Using dnf reinstall libssh solved the failure for me.
There was probably an issue with the transition to the new library from the package history.
I would recommends packages still using libssh_threads.so.4 to switch to libssh.so.4 despite the compat layer present in libssh that is broken for some reason...
(1) Failing packages according to dnf repoquery: remmina-0:1.2.0-0.51.20180408.git.6b62986.fc28.x86_64 remmina-plugins-nx-0:1.2.0-0.51.20180408.git.6b62986.fc28.x86_64 x2goclient-0:4.1.1.1-1.fc28.x86_64 x2goplugin-0:4.1.1.1-1.fc28.x86_64
On 08/17/2018 09:21 AM, Nicolas Chauvet wrote:
The failure seems caused by a missing symlink from libssh_threads.so.4 to the real library (using libssh.so.4 SONAME) That was with libssh-0.8.1-3.fc28.x86_64.
Yes, this was the reason. The -4 package fixes it.
Apologies, Andreas, for jumping the gun. I saw the minor version bump.
The -3 package unfortunately received 3 very quick +1 karma to push it to stable before Andreas could issue the -4 package.
On Fri, 2018-08-17 at 08:19 -0500, Michael Cronenworth wrote:
The libssh package uses wildcards on SONAME version. The package was upgraded from 0.7.5 to 0.8.1 in Fedora 27+ that included a SONAME bump.
Please remove the wildcard in libssh and begin package rebuilds. Stable versions of Fedora now contain broken software as the package has been released to stable.
It is not really a so-name bump, but rather a replacing of a now-defunc library. As far as I understand it should be addressed by:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-4794ce5b1f
regards, Nikos
-
Daniel P. Berrangé -
Michael Cronenworth -
Nicolas Chauvet -
Nikos Mavrogiannopoulos