Bug 844645 - Please rebuild mod_wsgi against python 2.7.3
Summary: Please rebuild mod_wsgi against python 2.7.3
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: mod_wsgi
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Runge
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-31 09:21 UTC by Jan Pazdziora
Modified: 2012-11-22 13:16 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-22 13:16:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jan Pazdziora 2012-07-31 09:21:43 UTC
Description of problem:

It looks like python 2.7.3 landed in Fedora 16 updates. This leads to warning in Apache's error_log upon startup.

Version-Release number of selected component (if applicable):

# rpm -q python mod_wsgi
python-2.7.3-3.fc16.x86_64
mod_wsgi-3.3-1.fc16.x86_64

How reproducible:

Deterministic.

Steps to Reproduce:
1. Have Fedora 16 with httpd, python-2.7.2, and mod_wsgi. Observe that there are not warnings upon Apache start and the notice line says

[Tue Jul 31 10:16:48 2012] [notice] Apache/2.2.22 (Unix) DAV/2 mod_wsgi/3.3 Python/2.7.2 configured -- resuming normal operations

2. Run yum upgrade python, note that version 2.7.3 gets installed.
3. Run service httpd restart, look into /var/log/httpd/error_log.
  
Actual results:

[Tue Jul 31 10:17:44 2012] [warn] mod_wsgi: Compiled for Python/2.7.2.
[Tue Jul 31 10:17:44 2012] [warn] mod_wsgi: Runtime using Python/2.7.3.
[Tue Jul 31 10:17:44 2012] [notice] Apache/2.2.22 (Unix) DAV/2 mod_wsgi/3.3 Python/2.7.3 configured -- resuming normal operations

Expected results:

[Tue Jul 31 10:17:44 2012] [notice] Apache/2.2.22 (Unix) DAV/2 mod_wsgi/3.3 Python/2.7.3 configured -- resuming normal operations

and no warn line.

Additional info:

This might or might not be a blocker for bug 833139.

Comment 1 Joe Orton 2012-11-22 13:16:04 UTC
It's only a warning; fixed in current releases.


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