Bug 114059
Summary: | after upgrade python 2.2 to 2.3 yum python apps can't find there modules | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | lupus <de_lupus> |
Component: | python | Assignee: | Mihai Ibanescu <mihai.ibanescu> |
Status: | CLOSED WONTFIX | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | rawhide | CC: | bjorn_bzilla, katzj, me |
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: | 2004-04-05 20:50:45 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
lupus
2004-01-22 00:27:00 UTC
I don't think there is an easy fix for this. Python 2.2 modules are installed in a different directory than the 2.3 ones. So are you saying that since the fix is not easy upgrades are to remain broken? This response makes no sense. Are we only fixing the easy parts? What am I missing? No, I wish I could say that though :-) The current transition from Fedora Core 1 to Fedora Core 2 cannot be safely performed with yum, the python upgrade being one of the reasons. The core problem is the fact yum (and the modules yum use) do not enforce the dependency on python 2.2; if that was the case, then yum would have realized it breaks a dependency, it would have tried to update itself and then everything would have been fine. So, until we fix the python dependencies for all the modules (and not only python itself), I cannot think of a way to not break python 2.2 compiled modules when we upgrade python. Does my two-line comment make more sense now? Yes it does. Thank you for the explaination. *** Bug 120616 has been marked as a duplicate of this bug. *** |