389 Directory Server
389 Directory Server is a full-featured LDAPv3 compliant server. In
addition to the standard LDAPv3 operations, it supports multi-master
replication, fully online configuration and administration, chaining,
virtual attributes, access control directives in the data, Virtual
List View, server-side sorting, SASL, TLS/SSL, and many other
features. (The server started out as Netscape Directory Server.)
-
1
derived packages
- Links to network:ldap / 389-ds
- Has a link diff
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout server:Kolab:Extras/389-ds && cd $_ - Create Badge
Refresh
Refresh
Source Files (show merged sources derived from linked package)
| Filename | Size | Changed |
|---|---|---|
| 0001-init_fhs.patch | 0000001717 1.68 KB | |
| 0002-use-python2-for-selinux-detection.patch | 0000000794 794 Bytes | |
| 389-ds-base-1.4.0.18.tar.bz2 | 0005678130 5.42 MB | |
| 389-ds-rpmlintrc | 0000000038 38 Bytes | |
| 389-ds.changes | 0000084071 82.1 KB | |
| 389-ds.spec | 0000015700 15.3 KB | |
| LICENSE.openldap | 0000002214 2.16 KB | |
| _link | 0000000120 120 Bytes | |
| extra-schema.tgz | 0000013093 12.8 KB |
Latest Revision
Aeneas Jaißle (aeneas_jaissle)
committed
(revision 1)
Comments 3
Nothing build! failed or unresolvable!
This is failing in tumbleweed because the bcond flags aren't being detected or applied properly. This could be a fault in this repositories configuration, rather than an issue in 389-ds, but I don't know enough about obs to determine it.
IMO you should probably just use the 389-ds package from tumbleweed/leap without putting it into your own branch here.
No. Leap 15.1, 15.2 and Tumbleweed is building with older version of 389. See my linked package. 389 need some changes to new version of 389 as it has in older 389 version.