installation instructions on download page fail (user is not instructed to install 389-admin)
quoting http://www.port389.org/docs/389ds/download.html """ New Install:
yum install 389-ds-base setup-ds-admin.pl """
[greg@c75-389ds ~]$ sudo setup-ds-admin.pl sudo: setup-ds-admin.pl: command not found
$ sudo locate setup-ds-admin.pl $ # missing
[greg@c75-389ds ~]$ yum provides setup-ds-admin.pl 389-admin-1.1.46-1.el7.x86_64 : 389 Administration Server (admin) Repo : epel Matched from: Filename : /usr/sbin/setup-ds-admin.pl
[greg@c75-389ds ~]$ rpm -qa 389* 389-ds-base-libs-1.3.7.5-24.el7_5.x86_64 389-ds-base-1.3.7.5-24.el7_5.x86_64
Metadata Update from @mreynolds: - Issue assigned to mreynolds
Sorry the download page is VERY outdated and basically obsolete (we'll work on that)
As for installing we have two guides the legacy install guide (for 1.3.x or easiler):100:
https://bugzilla.redhat.com/show_bug.cgi?id=1593807
http://www.port389.org/docs/389ds/legacy/install-guide.html
This is still vague about install 389-admin
And the new install guide for 389-ds-base-1.4.x
http://www.port389.org/docs/389ds/howto/howto-install-389.html
We will get the download page revamped next week. Thanks for filing the ticket!
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
Fixed. If there are still issues or changes you want to make please reopen this ticket. Thanks!
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2963
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)