Hi,

We generally don't support into extended lifetime of RHEL7 for all but x86_64, the last release announce this for ppc64 and aarch64 (despite the actual end occurring a while ago).

dbart, we seem to have 10.6-release packages for rhel8 and sles15, can we include these in the release for next time?

dbart thanks for adding jammy (22.04) s390x. So 10.8+ jammy packages are there. It will be 10.6+ next release, same as other architectures (top note, MDEV-28133, OpenSSL-3.0 wasn't back ported to 10.6 before the release)..

vivkong, how important is SLES12?

Currently we've only got only x86_64 tarballs currently. We've got a bit of work to go to get staticly linked dependencies and a reproducable environment for that. Once we've got that we might be able to extend this to all supported architectures.

Thanks for the detailed reply with links! It will be good to have SLES 12 if it is available for other architectures (I saw 10.6.x is available on SLES 12 ppc64le in the download page but I didn't find it in https://mirror.mariadb.org/yum/10.6/sles/12/). If we can help provide any assistance for this please let me know. Looking forward to seeing the packages for RHEL 8 and SLES 15 for next release!

I will check out the jammy packages for s390x. Thanks again!

I've made the changes to the prep scripts to create rhel8 and sles15 s390x package repositories with our next server releases.

Assigning back to danblack in case there are any other things to do on the Foundation side. If not feel free to close.

Thank you dbart. Very much appreciated.

I've reached out to SUSE to attempt to get some proper licenses to help generate build images for sles. vivkong if you know the right people in SUSE to talk about community licenses please email me daniel@mariadb.org

Thanks everyone. danblack I've sent you an email regarding the SUSE licenses.

Would it be possible to have s390x repo for bionic as well? Thanks.

I have some questions regarding the failures on s390x seen in the buildbot CI. Who should I contact about them? Thanks.

Thanks for SUSE contact.

bionic, noted, We'll look.

On test failures, most seem to be related to minor size differences involving compression. I think we're just a little time poor to verify with a high degree of accurancy that the result diffence isn't serious and isn't a big-endian issue which we need to fix. These do need to need to be addressed at some point. MDEV-28251 is there on main.func_json_notembedded.

I'm happy to take email which I'll read closely.

Thanks danblack. I will start looking into those failures and email you.

vivkong I am trying to create the SLES 12 image for s390x however I am getting the following error:

 ---> Running in 7606e7151924

Refreshing service 'container-suseconnect-zypp'.

Warning: Skipping service 'container-suseconnect-zypp' because of the above error.

All services have been refreshed.

Warning: There are no enabled repositories defined.

Use 'zypper addrepo' or 'zypper modifyrepo' commands to add or enable repositories.

Problem retrieving the repository index file for service 'container-suseconnect-zypp':

[container-suseconnect-zypp|file:/usr/lib/zypp/plugins/services/container-suseconnect-zypp]

I remember having this issue for SLES 15 and there was a problem with the underlying SLES subscription. Is this something that you can help us with?

Thank you!

vladbogo Let me email you to discuss the issue with SLES 12.

Applied changes to the SLES 12 builder - gcc 7 was needed in order to compile.

Based on my discussion with vivkong this can now be closed.