Bug 656256
Summary: | yum update fails when 389 components are installed | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Guenther Deschner <gdeschner> |
Component: | 389-admin | Assignee: | Rich Megginson <rmeggins> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 14 | CC: | dwalsh, mgrepl, nhosoi, nkinder, rmeggins, tcharl69 |
Target Milestone: | --- | Keywords: | screened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-11-24 17:24:58 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Guenther Deschner
2010-11-23 11:00:55 UTC
Please update 389-ds-base and 389-admin pkgs from the updates-testing repo and then update selinux-policy. # yum update 389-ds-base 389-admin --enablerepo=updates-testing # yum update selinux-policy It will work. Same problem here, working with the turnaround. Can you correct this issue without the trick? Regards, Charlie This issue will be solved once 389-ds-base and 389-admin are pushed to stable. This should occur soon since the packages have been marked as stable in Bodhi. The new 389-ds-base and 389-admin packages are now in the updates repository. Updates should work fine now. I am closing this bug. |