Details
-
Type:
Bug
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 5.5.38, 10.0.12
-
Component/s: Platform Debian
Description
Current MariaDB libmysqlclient/libmariadbclient package has the files:
usr/lib/*/libmariadbclient.so.* usr/lib/mysql/plugin/dialog.so usr/lib/mysql/plugin/mysql_clear_password.so
According to Debian policy, in a package like this all of these files should be in /usr/*/.., for example like this:
usr/lib/x86_64-linux-gnu/libmariadbclient.so usr/lib/x86_64-linux-gnu/dialog.so usr/lib/x86_64-linux-gnu/mysql_clear_password.so
How does dialog.so and mysql_clear_password.so work, can they safely be moved like this to another location, or will it break their refrencing or something?
Please advice on how to fix this. A patch would be even better.
Debian bug with https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739452 against mariadb-5.5 (Severity: important).
Gliffy Diagrams
Attachments
Issue Links
- is blocked by
-
MDEV-6284 Merge downstream Debian/Ubuntu packaging into upstream MariaDB
-
- Stalled
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
It's actually not in the policy yet, thus I cannot provide a link but the new comments at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739452 describes the issue better.
Okay, so all architecture-dependent .so files should be in /usr/lib64 (or /usr/lib32) on debian? This can be easily done.
Added versions to get it back on the radar. If it's not relevant anymore, it should be closed.
Yes, this is still waiting for a fix. As of 5.5.38 at least the path has not changed and the bug is open in Debian. The fix should be easy, just move the plugin path, right?
I don't see an issue here. Our libmariadbclient18.deb package is consistent. It does not have Multi-Arch: Same (as far as I understand, it's Multi-Arch: no by default), it puts libmysqlclient.so.18.0.0 in /usr/lib. So it has to put dialog.so and mysql_clear_password.so in /usr/lib too.
When we'll have new deb packaging, then dialog.so and mysql_clear_password.so will go in /usr/lib/x86_64-linux-gnu/ just as libmysqlclient.so.18.0.0 will. Either way client plugins should always go together with the client library.
Ah, right, sorry. This issue is — see issue links — blocked by MDEV-6284. It cannot be done until the blocker issue is done.
What does the debian policy say exactly? Please, provide a link.
These files cannot be moved, they are plugins that are loaded (with dlopen()) by libmariadbclient.so from the plugin directory.