Created attachment 437520 [details]
the spec file diff between MySQL-python-1.2.1 and my MySQL-python-1.2.3
Description of problem:
Request to update MySQL-python-1.2.1.
I noticed Django requires MySQL-python and that version is more than 1.2.2. Django-1.1.1-2.el5 as an EPEL package is already provided, but EPEL's MySQL-python package version is 1.2.1. So, I suggest to update MySQL-python more than 1.2.2 if by updating that package has no affect.
I made MySQL-python-1.2.3 package and uploaded as follows repository.
I tested MySQL-python-1.2.3 with my Django application, it seems well.
Please let me know if you have any comment on what I can do.
MySQL-python source tarball
Django requires MySQL-python 1.2.2
You've reported this bug to the wrong component.
As far as I can tell there's no MySQL-python in EPEL.
Assigning to MyProxy is really the wrong person.
However I happen to know about the this MySQL bug.
It's fixed in RHEL4 but not in RHEL5. I have a ticket open for nearly
a year open with RHEL5 to get it fixed.
But as mentioned this cannot be fixed in EPEL since MySQL-python is
already part of RHEL.
Sorry for my mistake. I understood #475854 is a bug report which I require.
I'm looking forward to get the updated MySQL-python package.
*** This bug has been marked as a duplicate of bug 475854 ***