Bug 168655
Summary: | Patch which fixes building as "python24". | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | jafo-redhat |
Component: | python | Assignee: | Mihai Ibanescu <mihai.ibanescu> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | katzj |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 2.4.1-11 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-30 14:59:03 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
jafo-redhat
2005-09-19 05:52:36 UTC
Not sure I understand yor comment - if you install python24, do you not want tools_dir and demo_dir to be /usr/lib/python2.4/Tools and /Demo, respectively? Why would they be living under /usr/lib/python? (this assumes a 32-bit system). If you have both python = 2.4.1 and python24 = 2.4.1 then you will have conflicts anyway. I must be missing something. The "%define __python_ver 24" exists so that you can use a Python 2.4 (or in the future, 2.5) package on a system with a previous version of Python on it. However, the current packages are broken in that respect. It looks like the first hunk of my patch is wrong, please ignore it. Otherwise, the patch should resolve the problems with defining __python_ver. I'm not talking about installing both python=2.4.1 and python24=2.4.1. Yes, there would be conflicts in that instance, and there's really no need to build a python24 in that instance. However, on FCN where N<4 there is. I'm the Python RPM maintainer for python.org, and was attempting to use these RPMs for some Python.org packages when I ran into the problems above. Of course, on FC3 I also ran into a problem with the DB library version, but that's not something that should be changed in your base package. We are currently working to fix the lib64 issue in the base Python release, but in the meantime it looks like the Fedora packages are a good base set for me to use, particularly for people running on systems with lib64. So, in short, the __python_ver stuff in the Fedora package is not functional. Sean Patch should be incorporated in the latest Rawhide (2.4.1-11 or newer). |