Bug 1748994
| Summary: | Rebase 389-ds-base to 1.4.2 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Viktor Ashirov <vashirov> |
| Component: | 389-ds-base | Assignee: | mreynolds |
| Status: | CLOSED ERRATA | QA Contact: | RHDS QE <ds-qe-bugs> |
| Severity: | unspecified | Docs Contact: | Marc Muehlfeld <mmuehlfe> |
| Priority: | unspecified | ||
| Version: | 8.2 | CC: | cheimes, lkrispen, mreynolds, nkinder, pasik, spichugi, tbordaz, vashirov |
| Target Milestone: | rc | Keywords: | Rebase |
| Target Release: | 8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 389-ds-1.4-8020020191114225524-bf00efc9 | Doc Type: | Enhancement |
| Doc Text: |
.Directory Server rebased to version 1.4.2.4
The _389-ds-base_ packages have been upgraded to upstream version 1.4.2.4, which provides a number of bug fixes and enhancements over the previous version. For a complete list of notable changes, read the upstream release notes before updating:
* https://directory.fedoraproject.org/docs/389ds/releases/release-1-4-2-4.html
* https://directory.fedoraproject.org/docs/389ds/releases/release-1-4-2-3.html
* https://directory.fedoraproject.org/docs/389ds/releases/release-1-4-2-2.html
* https://directory.fedoraproject.org/docs/389ds/releases/release-1-4-2-1.html
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-04-28 16:01:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1748987 | ||
|
Description
Viktor Ashirov
2019-09-04 15:54:37 UTC
# rpm -q 389-ds-base 389-ds-base-1.4.2.4-4.module+el8.2.0+4930+d4051b3a.x86_64 In the logs: [03/Dec/2019:13:22:36.535106388 +0000] - INFO - main - 389-Directory/1.4.2.4 B2019.331.1525 starting up Marking as VERIFIED. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:1703 |