New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libc dependency while uplifting redis library from 6.2.12 to 6.2.13 #12580
Comments
Hi Team, can you please help us with this issue. It is quite an urgent requirement for our project right now. |
Redis does not specify the minimum libc version, it depends on how the distribution is built.
|
@sundb
Can you please give us some insights on this ? Thanks |
By comparing between 6.2.12 and 6.2.13 (https://github.com/redis/redis/pull/12400/files) I don't see any changes related to the dependency library. |
@sundb To check this, if we use a package which has redis 6.2.12, then the upgrade is successful. Thanks |
This is actually - the Vendor(Oracle Linux) problem, if you are facing any. None to do with Redis. And - what groundbreaking feature you get upgrading redis version. Enterprises requires stable application. I think when minor dependency issues, you better use whats available. However, adding the dependency and building - Redis is not so difficult. But it is another problem, to maintain the self-built project. |
I am using Oracle Linux 7, which is similar to redhat 7. In this, the default supported libc version is libc-2.17.so. With the above setup, when we install Redis 6.2.12 version, everything seems to be working properly. Recently, I have uplifted to Redis 6.2.13 and there is a direct dependency on libc library. It specifically requires libc-2.28.so instead of libc-2.17.so. However, in the previous version of Redis i.e 6.2.12, the libc used was libc-2.17.so.
NOTE : From what I understand, libc-2.28.so is generally available from linux 8 onwards. So, can someone please let me know if the dependency on libc-2.28.so is added intentionally for Redis 6.2.13? If not, how this dependency can be resolved ?
The text was updated successfully, but these errors were encountered: