Bug 784135 - Rebuild for python 2.6.6
Summary: Rebuild for python 2.6.6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: mod_python
Version: el6
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-23 22:33 UTC by Orion Poplawski
Modified: 2013-08-29 17:41 UTC (History)
2 users (show)

Fixed In Version: mod_python-3.3.1-16.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-29 17:41:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Orion Poplawski 2012-01-23 22:33:02 UTC
Description of problem:

I'm seeing:

Mon Jan 23 15:10:14 2012] [error] python_init: Python version mismatch, expected '2.6.5', found '2.6.6'.  Perhaps worth a rebuild?

Version-Release number of selected component (if applicable):
mod_python-3.3.1-14.el6.1.i686

Comment 1 daryl herzmann 2012-08-14 14:59:56 UTC
me too, *bump* :)

Comment 2 daryl herzmann 2013-08-28 12:52:37 UTC
A year later *bump* :)

Comment 3 Fedora Update System 2013-08-28 15:09:12 UTC
mod_python-3.3.1-16.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/mod_python-3.3.1-16.el6

Comment 4 Fedora Update System 2013-08-28 16:43:35 UTC
Package mod_python-3.3.1-16.el6:
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing mod_python-3.3.1-16.el6'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11370/mod_python-3.3.1-16.el6
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2013-08-29 17:41:49 UTC
mod_python-3.3.1-16.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.