#50812 dscontainer executable should be placed under /usr/libexec/dirsrv/
Closed: wontfix 4 years ago by mreynolds. Opened 4 years ago by mreynolds.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 8): Bug 1714688

Description of problem:
dscontainer is not a user-runnable executable. Per packaging guidelines it
should be placed under /usr/libexec/dirsrv/

Version-Release number of selected component (if applicable):
389-ds-base-1.4.1.3-1.module+el8.1.0+3259+a5bc8ad3.x86_64

How reproducible:
always

Steps to Reproduce:
# rpm -ql python3-lib389 | grep dscontainer
/usr/sbin/dscontainer


There are also executables that come from python3-lib389, that should be part
of 389-ds-base rather than python3-lib389 (since it's literally a library):
# rpm -ql python3-lib389 | grep sbin
/usr/sbin/dsconf
/usr/sbin/dscontainer
/usr/sbin/dscreate
/usr/sbin/dsctl
/usr/sbin/dsidm

Metadata Update from @mreynolds:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1714688

4 years ago

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

4 years ago

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to review

4 years ago

Commit 74557db relates to this ticket

Commit 74557db relates to this ticket

f5bd9e7..22d53d0 389-ds-base-1.4.2 -> 389-ds-base-1.4.2

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue set to the milestone: 1.4.2 (was: 1.4.1)
- Issue status updated to: Closed (was: Open)

4 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/3866

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
Related Pull Requests