| 1 |
Hi there, |
| 2 |
|
| 3 |
I just encountered a problem regarding binary packages and got some broken |
| 4 |
packages and I don't know how to solve this permanently; On my buildhost I |
| 5 |
compile all packages I need for several VMs and install only those packages I |
| 6 |
really need on the target machines. |
| 7 |
|
| 8 |
Problem combination: |
| 9 |
|
| 10 |
* net-fs/samba-4.15.12-r2 has a direct dependency to sys-libs/liburing. |
| 11 |
* dev-db/mariadb does not have a dependency to liburing, but during build, if |
| 12 |
liburing is available it will use it for some reason yielding a binary that |
| 13 |
links against it: |
| 14 |
|
| 15 |
Buildhost-server ~ # ldd /usr/sbin/mysqld |
| 16 |
linux-vdso.so.1 (0x00007ffec5b61000) |
| 17 |
libpcre2-8.so.0 => /usr/lib64/libpcre2-8.so.0 (0x00007fcfbd704000) |
| 18 |
libcrypt.so.2 => /lib64/libcrypt.so.2 (0x00007fcfbd6c9000) |
| 19 |
liburing.so.2 => /usr/lib64/liburing.so.2 (0x00007fcfbd6c2000) |
| 20 |
--- |
| 21 |
|
| 22 |
Installing that package on a target VM does not install liburing, hence |
| 23 |
yielding a broken /usr/sbin/mysqld binary because the library is missing, and |
| 24 |
the reason why I still have a consistent system on my buildhost is because |
| 25 |
samba has it as dependency. |
| 26 |
|
| 27 |
A quick on-the-fly solution is either manually installing liburing and adding |
| 28 |
it to the world profile (@world is required otherwise emerge -c will remove it |
| 29 |
again), or install mariadb by compiling it (not using emerge -k). But all of |
| 30 |
them are somewhat unclean. |
| 31 |
|
| 32 |
A) Is this a problem in the ebuild script of mysql because not taking care of |
| 33 |
this? |
| 34 |
b) Is this a problem of mariadb's configure/make script because of implicitly |
| 35 |
using the library without being told so by ebuild? |
| 36 |
|
| 37 |
Alex |
Archives