FS#70635 - Ruby2.7 libraries names seem wrong
Attached to Project:
Community Packages
Opened by Daniel Zaoui (jackdanielz) - Thursday, 29 April 2021, 05:17 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 29 April 2021, 20:36 GMT
Opened by Daniel Zaoui (jackdanielz) - Thursday, 29 April 2021, 05:17 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 29 April 2021, 20:36 GMT
|
Details
Description:
Programs such as dislocker link with ruby2.7. However, the execution fails: dislocker: error while loading shared libraries: libruby.so.2.7: cannot open shared object file: No such file or directory The libraries for ruby 2.7: usr/lib/libruby-2.7.so usr/lib/libruby-2.7.so.2.7 usr/lib/libruby-2.7.so.2.7.3 For Ruby 3.0.1: usr/lib/libruby.so usr/lib/libruby.so.3.0 usr/lib/libruby.so.3.0.1 If the symbolic link 'libruby.so.2.7' is created to usr/lib/libruby-2.7.so, dislocker works. Is the naming intented? Steps to reproduce: Just install dislocker and run it |
This task depends upon
Ruby is now 3.0 but you can not rebuild dislocker as the PKGBUILD has not been updated to apply [1].
The PKGBUILD also can not build against ruby2.7 without changes. So you are using the symlink.
Not a bug in ruby or ruby2.7.
[1] https://github.com/Aorimn/dislocker/commit/77fcdd8e00e6934d4e503aaf9743d563f249129d
I was more wondering regarding the naming of the libraries. libruby-2.7.so.2.7 just seems weird but if it is intended, so I am ok :-)