I am looking for some advice regarding upgrading our deployment.
I am currently on v2.0.15 running on four AlmaLinux release 8.10
Running cockpit-389-ds as well

Based on this page
389 Directory Server - 
Download<https://www.port389.org/docs/389ds/download.html>
The copr repo
Builds for 
@389ds/389-directory-server<https://copr.fedorainfracloud.org/coprs/g/389ds/389-directory-server/builds/>
is at 2.2.9-2

Available Packages
Name         : 389-ds-base
Version      : 2.2.9
Release      : 2.el8
Architecture : src
Size         : 22 M
Source       : None
Repository   : copr:copr.fedorainfracloud.org:group_389ds:389-directory-server
Summary      : 389 Directory Server (base)
URL          : https://www.port389.org
License      : GPLv3+ and (ASL 2.0 or MIT) and MIT and (0BSD or MIT or ASL 2.0) 
and (Unlicense or MIT) and MPLv2.0 and BSD and (ASL 2.0 with exceptions or ASL 
2.0 or MIT) and (MIT or
             : zlib or ASL 2.0) and ASL 2.0 and (ASL 2.0 or Boost) and ((MIT or 
ASL 2.0) and Unicode-DFS-2016)
Description  : 389 Directory Server is an LDAPv3 compliant server.  The base 
package includes
             : the LDAP server and command line utilities for server 
administration.

I see that there are other repos representing multiple versions that I could 
move to from here depending on what copr repo I point at
Project List<https://copr.fedorainfracloud.org/coprs/fulltext/?fulltext=389ds>
I am unsure if i should switch my repo and what is the easiest upgrade as well 🙂
migrating to Alma 9 is probably in the cards later this year as well so that 
might be a factor in picking a version ...

thx!
NeeL
-- 
_______________________________________________
389-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to