Re: Can't update RPM package to latest version
| От | Evan Rempel |
|---|---|
| Тема | Re: Can't update RPM package to latest version |
| Дата | |
| Msg-id | YT2P288MB01728DF6694056B1FA5A20BDB9D4A@YT2P288MB0172.CANP288.PROD.OUTLOOK.COM обсуждение исходный текст |
| Ответ на | Can't update RPM package to latest version ("Nicolas Ross" <rossnick-lists@cybercat.net>) |
| Ответы |
Re: Can't update RPM package to latest version
|
| Список | pgsql-admin |
The latest release from RedHat, that came out this month is
$ rpm -q --whatprovides 'libcrypto.so.3(OPENSSL_3.4.0)(64bit)'
$ rpm -q --whatprovides 'libcrypto.so.3(OPENSSL_3.4.0)(64bit)'
Openssl-libs-3.5.1-3.el9.x86_64
At our site we freeze deployment of packages at the beginning of the month so that our prod hosts get the same packages that were updated/deployed in our dev environments.
This package, frozen from the beginning of the month is only
openssl-libs-3.2.2-6.el9_5.1.x86_64
openssl-libs-3.2.2-6.el9_5.1.x86_64
which does not satisfy this requirement. On a system that has the actual latest packages from RedHat this package has been updated to
openssl-libs-3.5.1-3.el9.x86_64
openssl-libs-3.5.1-3.el9.x86_64
% rpm -q --whatprovides 'libcrypto.so.3(OPENSSL_3.4.0)(64bit)'
openssl-libs-3.5.1-3.el9.x86_64
If you update to the latest packages on your host, this requirement will be satisfied.
--
Evan
В списке pgsql-admin по дате отправления: