Hi,
On Thu, 31 Mar 2022 at 15:27, Neel Karandikar <Neel.Karandikar@sscinc.com> wrote:
Hello
At what point did the repo installation "stable/default" change from 1.4.4.17 to 2.0.x?
As described in https://www.port389.org/docs/389ds/download.html#centos-81-ds-14x, "stable" stream follows the oldest of the supported Fedora releases, i.e. right now it's F34. This is the update in EPEL that introduced the 2.0.13 version in EPEL8:
There is currently 2.0.15 in epel-testing:
EPEL8 will continue to use the 2.0.x version and will not switch to 2.1.x, because of the raised minimal required version of glibc to 2.30. At this point "stable", "testing" and "next" streams in EPEL8 converged and have the same version.
EPEL9 will likely not have modules. We're considering a different way to distribute upstream versions of 389DS with cockpit through our copr, but waiting for the final decision about modular content in EPEL9 in https://pagure.io/epel/issue/135.
Thanks.
_______________________________________________
I know this can depend on the variability of yum repos etcBut today on ours I noticed that
yum module info 389-directory-server -> stable/default is now pointing at v2.0.13
running Centos 8 stream
we are currently running 1.4.4.16 and 1.4.4.17, with some test servers at 2.0.13 (as they auto upgraded with what was in our repo)
I actually just want to know what versions of release notes I need to review, so I can see changes that might occur when I upgrade from 1.4.4.16 to 2.0.13.
Thx!
Neel
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Viktor
No comments:
Post a Comment