Thank you for the reply, Antonis. It is nice to know that I'm not the only worried about this. Not only is there a question about the status of the packages in the repo. The instructions on: https://www.port389.org/docs/389ds/download.html don't even work for RHEL 10. Running "dnf copr enable @389ds/389-directory-server" results in an error: Error: It wasn't possible to enable this project. Repository 'epel-10-x86_64' does not exist in project '@389ds/389-directory-server'. -Bryan On Tue, Jul 07, 2026 at 06:39:35PM +0300, Antonis Kopsaftis via 389-users wrote: > Hello, > > I had similar concerns over the past year. > The packages available through the various repos are either old or generally > not updated. > The packages which are included in the distros are fine, but no package for > cockpit is available. > > So we choose to setup a separate VM with the same OS with our new LDAP > servers. In our case it was Oracle Linux 9.x > > We followed the instructions on > https://www.port389.org/docs/389ds/development/building.html > and manage to compile various 2.x versions of 389DS. > The we took the created rpms and installed 389DS on our servers. After a > couple of months of testing, we are running in production. > > We also tried to compile various 3.x versions, but we did not succeed. The > binaries were compiled successfully but the rpm packaging failed. > > My personal opinion is that the development of the project is focuses for > Fedora OS and not RHEL clones. > So as RHEL clones have older version of various packages (e.g various python > modules), the build is not always successfully in RHEL clones. > > Antonis > > On 7/7/2026 4:40 μ.μ., Bryan K. Walton via 389-users wrote: > > Hi, > > > > I have a few questions about the 389-ds versions available for RHEL. > > > > On https://www.port389.org/docs/389ds/download.html it states that to > > install the cockpit-389-ds package, we must use the copr repo. > > When we enable that repo on RHEL 8, the newest version of 389-ds-base and > > cockpit-389-ds available to us is 2.2.9. This seems to correspond with > > this page: > > https://copr.fedorainfracloud.org/coprs/g/389ds/389-directory-server/builds/ > > > > That pages shows that the most recent successful build was version > > 2.2.9-2. However, digging around the copr servers, I see an epel 8 > > version 2.5.2 available here: > > https://download.copr.fedorainfracloud.org/results/%40389ds/389-directory-server-2.5/epel-8-x86_64/08189134-389-ds-base/ > > > > Questions: > > 1. Is that 2.5.2 version bad? > > 2. Is the 2.2.9 version really the lastest supported version for RHEL 8? > > 3. If we upgrade our server to RHEL 10, I see that epel 10 has version > > 3.2.0 of 389-ds-base in it. How do we get a newer version of > > cockpit-389-ds for use with the newer versions of 389-ds-base? > > > > Thanks, > > Bryan Walton > > -- > _______________________________________________ > 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, report it: https://forge.fedoraproject.org/infra/tickets/issues/new -- Bryan K. Walton 319-337-3877 Senior Linux Systems Administrator Leepfrog Technologies, Inc -- _______________________________________________ 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, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
No comments:
Post a Comment