Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1356088
Description of problem: Installation of 389-ds-base-tests package fails since python-lib389 package not added in RHEL7. Version-Release number of selected component (if applicable): 389-ds-base-1.3.5.10-3 How reproducible: Steps to Reproduce: 1. Install 389-ds-base, 389-ds-base-tests and its dep components in rhel7.3 2. Brew link - https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=502959 3. Installation of 389-ds-base-tests fail with python-lib389 package not found. It fails in the CI environment... 07:21:32 --> Processing Dependency: python-lib389 for package: 389-ds-base-tests-1.3.5.10-3.el7.noarch 07:21:32 --> Finished Dependency Resolution 07:21:32 You could try using --skip-broken to work around the problem 07:21:32 Error: Package: 389-ds-base-tests-1.3.5.10-3.el7.noarch (brew-task-11333149-noarch) 07:21:32 Requires: python-lib389 Actual results: Jenkins job fails. Expected results: Add this package in rhel7. Jenkins job should be successful. Additional info:
Metadata Update from @nhosoi: - Issue set to the milestone: 1.3.7 backlog
Moving to 1.4
Metadata Update from @mreynolds: - Custom field component reset (from Admin - rest389) - Custom field origin adjusted to Dev (was: Community) - Issue close_status updated to: None - Issue set to the milestone: 1.4 backlog (was: 1.3.7 backlog)
lib389 source was absorbed into 1.3.7, and will become a subpackage. So this ticket can probably be closed.
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field reviewstatus adjusted to None - Custom field version adjusted to None
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/2091
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)
Login to comment on this ticket.