Does it cause any real problems? As far as I can see, there is a symlink

lib/libgalera_smm.so -> galera/libgalera_smm.so

Still, nirbhay_c, please check if it is expected, and if so, if it should be documented somewhere.

dbart Hi! Did we change/update the library path in the script that packs it in server bintar?

nirbhay_c: the packages that the libgalera_smm.so is extracted from have the library at /usr/lib*/galera/libgalera_smm.so and I didn't change it.

The glibc_214 bintars do have a symlink under /usr/lib*/, but the other bintars do not.

Let me know what should be done and I'll make the necessary adjustments to the location. Thanks.

dbart

Let me know what should be done and I'll make the necessary adjustments to the location. Thanks.

Not sure. I am trying to figure out what exactly triggered this change.

• mariadb-10.1.10-linux-x86_64/lib/libgalera_smm.so
• mariadb-10.1.11-linux-x86_64/lib/galera/libgalera_smm.so
• mariadb-10.1.12-linux-x86_64/lib/galera/libgalera_smm.so
• mariadb-10.1.10-linux-x86_64/lib/libgalera_smm.so

Looks the like change occurred on 10.1.11 release, but IIRC the directory structure for galera packages did not change around that release.

Both locations are fine with me, its just we have to ensure that the file location does not change with release.

I think the best path forward will be to unify the location between the bintar, rpm, and deb packages, so in the bintars the location going forward will remain lib/galera/libgalera_smm.so with a symlink in the lib/ directory that points to it. I've implemented this for the MariaDB Galera Cluster 10.0.24 release coming out today (and I've made a note of it in the release notes). I've also added a note about the change to: https://mariadb.com/kb/en/getting-started-with-mariadb-galera-cluster/