New to 2.5.14, was working prior. I wonder if it's a fedora change that's leaked into the SLE build.

OpenSUSE/SLE 15.3 = glibc/libm v2.31
OpenSUSE 15.1 & 15.2 = glibc/libm v2.26

maxscale is asking for glibc 2.29.

rpm -q --requires maxscale-2.5.14-1.sles.15.x86_64.rpm
<snip>
libm.so.6()(64bit)
libm.so.6(GLIBC_2.2.5)(64bit)
libm.so.6(GLIBC_2.29)(64bit)
</snip>

Definitely a build bug. Double entry? Maybe it should have been built as >=2.26 if updating and remove the old 2.2.5 line?

For reference, working last version:
rpm -q --requires maxscale-2.5.13-1.sles.15.x86_64.rpm
<snip>
libm.so.6()(64bit)
libm.so.6(GLIBC_2.2.5)(64bit)
</snip>

found and fixed first problem: 2.5.14 packages are wrong in the production repo, re-uploaded and waiting for sync.

after it, I will continue with opensuse

managed to install on openSUSE Leap 15.3

I'm not sure we can try with 15.2

Still seeing the old version
https://downloads.mariadb.com/MaxScale/2.5/sles/15/x86_64/

libm.so.6()(64bit)
libm.so.6(GLIBC_2.2.5)(64bit)
libm.so.6(GLIBC_2.29)(64bit)

1. sha256sum maxscale-2.5.14-1.sles.15.x86_64.rpm
   64aaeb60876bd8fcdef329aa0bc542a0e0e12ed9b49e7e5a008dc1e75aeb1163 maxscale-2.5.14-1.sles.15.x86_64.rpm

Slow sync?

it is another problem.

I can install on OpenSUSE 15.3, but I got the same error with OpenSUSE 15.2:

Problem: nothing provides 'libm.so.6(GLIBC_2.29)(64bit)' needed by the to be installed maxscale-2.5.14-1.sles.15.x86_64

upgrade:

sudo zypper --releasever=15.3 ref

sudo  zypper --releasever=15.3 dup --download-in-advance --allow-vendor-change

fixes the problem.

but in any case, we do not support for opensuse 15.2

SLE* 15.2 is supported by SUSE until 31 Dec 2021. According to your engineering doc you still support all flavours of SLE 15.

https://mariadb.com/wp-content/uploads/2021/06/mariadb-engineering-policies-v4-06_policy_1110.pdf

To the best of my knowledge SLE 15.1 and 15.2 is GLIBC v2.26

As per that engineering policy, we supports SLES (Enterprise servers) versions but not OpenSUSE.

I'm not talking about opensuse, I'm talking about SUSE SLE <15.3

Here's the build sources...
https://build.opensuse.org/package/show/SUSE:SLE-15:GA/glibc version = 2.26
https://build.opensuse.org/package/show/SUSE:SLE-15-SP2:GA/glibc version = 2.26

support for sles 15.1 and 15.2 can be implemented. I'm not sure I can make it with GCloud, but AWS can provide images for 15.2 at least.

tturenko I think we can revert the build VMs to use the oldest supported SLES version as they seem to be forwards compatible with newer SLES releases. This means we'll only have to update the build VM whenever a SLES minor version goes EOL.

Not wanting to go too far off topic, but you have assessed openbuildservice? It's can handle openSUSE, Debian 9+, Fedora 21+, Ubuntu 14+, Arch, Red Hat Enterprise Linux, centos 6+ and SUSE Linux Enterprise... A nice all in one, without having to worry about cloud images by third parties disappearing. https://openbuildservice.org/

This is currently in line with what the MariaDB Engineering policy states it wont' be fixed until that is changed.

https://mariadb.com/wp-content/uploads/2021/09/mariadb-engineering-policies-v4-08_policy_1117.pdf?page=7

SLES 12 and 15 are still listed. Are you saying you're not supporting SLES 15.2 and you're just waiting for the engineering policy to be updated?

The engineering policy doesn't seem to mention which specific minor SLES versions are supported and for how long so it seems to be left for interpretation. I'll request that the engineering policy is clarified with regards to this.

Additionally, since older 2.5 releases did use the older SLES releases, it'd at least be consistent to continue with it for this release.