Bug 153197
Summary: | /sbin/ldconfig not run with --oldpackage | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Gene Czarcinski <gczarcinski> |
Component: | rpm | Assignee: | Paul Nasrat <nobody+pnasrat> |
Status: | CLOSED WONTFIX | QA Contact: | Mike McLean <mikem> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | matt, n3npq |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-04-24 23:02:55 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
Gene Czarcinski
2005-04-02 18:03:22 UTC
RPM does not support downgrades as with --oldpackage. I just hit the same problem downgrading my glib2 from rawhide back to Fedora 9 after I finished testing a program that needed the rawhide version. When I logged out of GNOME, gdm died and I had to run ldconfig manually from the terminal. What is the purpose of --oldpackage if not for downgrades? It seems to me that the problem could be fixed easily by letting ldconfig run a second time after the erasures are complete. I understand that the symlinks will still be broken during the erasures (the only way to fix that would be for rpm to somehow indicate its planned shared library deletions to ldconfig before actually performing them), but that's better than leaving them broken forever. |