SLES 12.5

liblz4-1_7 package comes from SUSE-PackageHub-12-SP5-Standard-Pool. To my understanding, it is a non-commercial (free of charge) repo/product, but it is not enabled by default.
The question whether it can be considered a "standard" SLES-12 repository was discussed before, and so far we had been leaning towards "no".

In buildbot the package is currently pre-installed on the build machine and the repo is enabled on the install machine.
The dependency appeared between 10.6.4 and 10.6.5, possibly due to installation of the library on the build machine for other purposes.

If we want to avoid the dependency in future, we will need to either drop the package at runtime before 10.6 build on SLES-12, or somehow instruct Columnstore not to use it, if it has a switch for it; and we should do it before the upcoming set of releases, so that at least 10.7 GA doesn't have it, and for 10.6 the exposure is minimal.

I think it's fine if ColumnStore will use it. The server should only use default standard repos, but if one wants an extra special engine — I think it's reasonable to expect that it might require an extra special repository.

tturenko,

See the above. I guess you can enable that repo/product in your tests. If possible, better to do it conditionally – only when Columnstore 10.6+ is involved. If the conditional approach isn't possible, then just enable it – we do it in the CS buildbot anyway.

Closing based on Sergei's comment above.