MDBF-882 - ColumnStore packages not created for OpenSuse/Sles #681
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The failure on OpenSuse 15.6 is unrelated to my changes. |
|
yes https://bugzilla.opensuse.org/show_bug.cgi?id=1228968 seems a few minor increments above permissions-20240826-150600.10.9.1 created https://bugzilla.opensuse.org/show_bug.cgi?id=1235873 for the current version. list seems to match https://github.com/MariaDB/server/pull/2651/files - good. |
grooverdan
reviewed
Jan 15, 2025
This is 1/2 PR in the series for solving **MDBF-882**. It will align `buildbot.mariadb.{NET,ORG}` in terms of produced packages by fixing ColumnStore package creation for MariaDB Server versions 10.5, 10.6, 10.11
ColumnStore package creation for 11.4 onward will be solved in a separate PR as it needs more attention.
How to test this PR:
-> pull an opensuse/sles container image from quay -> install the missing libraries added in this PR
-> follow build instructions on any opensuse / sles autobake builder -> check that the CS packages were produced
How to deploy to Production:
-> after the OpenSuse/Sles images are re-generated in DEV, sync with Main branch and the GitHub workflow
will automatically promote it to Production.
RazvanLiviuVarzaru
force-pushed
the
bug/MDBF-882
branch
from
46514b4 to
9c818f4
Compare
We can merge this PR and I will make the required changes manually to OpenSuse 15.6 image and push it to QUAY. |
RazvanLiviuVarzaru
added a commit
to RazvanLiviuVarzaru/buildbot-r
that referenced
this pull request
Jan 16, 2025
This is a fix for MariaDB#681 While boost components were installed on SLES, the CS package was still missing. After doing a CMAKE --trace I've found out that limbxml2 is missing. MESSAGE_ONCE(CS_NO_LIBXML Could not find a usable libxml2 development environment! ) Tested locally with the current sles1506 container image and after installing libxml2-devel, the CS packages are generated for mariadb server 10.11.
RazvanLiviuVarzaru
added a commit
that referenced
this pull request
Jan 16, 2025
This is a fix for #681 While boost components were installed on SLES, the CS package was still missing. After doing a CMAKE --trace I've found out that limbxml2 is missing. MESSAGE_ONCE(CS_NO_LIBXML Could not find a usable libxml2 development environment! ) Tested locally with the current sles1506 container image and after installing libxml2-devel, the CS packages are generated for mariadb server 10.11.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is 1/2 PR in the series for solving MDBF-882. It will align
buildbot.mariadb.{NET,ORG}in terms of produced packages by fixing ColumnStore package creation for MariaDB Server versions 10.5, 10.6, 10.11ColumnStore package creation for 11.4 onward will be solved in a separate PR as it needs more attention.
How to test this PR:
-> pull an opensuse/sles container image from quay -> install the missing libraries added in this PR
-> follow build instructions on any opensuse / sles autobake builder -> check that the CS package was produced.
How to deploy to Production:
-> after the OpenSuse/Sles images are re-generated in DEV, sync with Main branch and the GitHub workflow
will automatically promote it to Production.