#48788 Install guide broken: No package 389-ds available
Closed: wontfix 6 years ago Opened 7 years ago by alanfranz.

Hello,
I'm trying to install 389 on Centos 7 x86_64 by following the official guide:

http://directory.fedoraproject.org/docs/389ds/download.html

Problem is: there's no "389-ds" package (or metapackage?) in CentOS or EPEL, there're many separated components; it would be good to understand which ones are required to setup a 389ds installation, without adding any bloat. I've seen the setup admin script exists in 389-admin script actually exists in 389-admin, but I'd like to know if that package is enough.

Thank you!

[root@b310cdb30a31 yum.repos.d]# yum search 389
Loaded plugins: fastestmirror, ovl
Loading mirror speeds from cached hostfile
 * base: mirror.crazynetwork.it
 * epel: epel.check-update.co.uk
 * extras: mirror.crazynetwork.it
 * updates: mirror.crazynetwork.it
============================================================================== N/S matched: 389 ==============================================================================
389-admin.x86_64 : 389 Administration Server (admin)
389-admin-console.noarch : 389 Admin Server Management Console
389-admin-console-doc.noarch : Web docs for 389 Admin Server Management Console
389-adminutil.x86_64 : Utility library for 389 administration
389-adminutil-devel.x86_64 : Development and header files for 389-adminutil
389-console.noarch : 389 Management Console
389-ds-base.x86_64 : 389 Directory Server (base)
389-ds-base-devel.x86_64 : Development libraries for 389 Directory Server
389-ds-base-libs.x86_64 : Core libraries for 389 Directory Server
389-ds-console.noarch : 389 Directory Server Management Console
389-ds-console-doc.noarch : Web docs for 389 Directory Server Management Console
pcp-pmda-ds389.x86_64 : Performance Co-Pilot (PCP) metrics for 389 Directory Servers
pcp-pmda-ds389log.x86_64 : Performance Co-Pilot (PCP) metrics for 389 Directory Server Loggers

  Name and summary matches only, use "search all" for everything.
[root@b310cdb30a31 yum.repos.d]# yum -y install 389-ds
Loaded plugins: fastestmirror, ovl
Loading mirror speeds from cached hostfile
 * base: mirror.crazynetwork.it
 * epel: epel.check-update.co.uk
 * extras: mirror.crazynetwork.it
 * updates: mirror.crazynetwork.it
No package 389-ds available.
Error: Nothing to do

Hi,

I've update the website to correctly refer to the 389-ds-base package.

Thanks for your patience.

{{{
Then you can install 389-ds-base and get all of the core directory server, admin server, and console components as per the directions below.
}}}

389-ds is a metapackage that pulls not only 389-ds-base, but 389-admin and console packages. So documentation is now not correct. In Fedora we didn't updated 389-ds for a long time, it was rebuilt during mass rebuild. In EPEL it wasn't updated and dropped(?) at some point. We should just rebuild the package in EPEL.

Build is done:
https://bodhi.fedoraproject.org/updates/389-ds-1.2.2-6.el7

alanfranz, could you please try it and give a karma if it works for you? Then, the package is moved from testing to stable. Thanks.

And I think the doc on 389port.org needs to be undone.

Metadata Update from @vashirov:
- Issue set to the milestone: N/A

7 years ago

Metadata Update from @firstyear:
- Custom field reviewstatus adjusted to new
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

6 years ago

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/1848

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

3 years ago

Login to comment on this ticket.

Metadata