Bug 600214

Summary: update python-mechanize to latest 1.x version
Product: [Fedora] Fedora EPEL Reporter: Felix Schwarz <fschwarz>
Component: python-mechanizeAssignee: Luke Macken <lmacken>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: el5CC: lmacken, pfrields
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: python-mechanize-0.1.10-3.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-08 18:01:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Felix Schwarz 2010-06-04 07:21:26 UTC
Fedora EPEL 5 ships python-mechanize 0.1.6-0.1.b. Unfortunately there are a couple of bugs in this old version and I'd like to request an update to the latest 1.x version (which is API compatible, judging from the change log). Version 1.0.8 contains a fix for my particular bug, though you might want to go to 0.1.11 if you push an update.

I could provide a spec file patch if you like.

Comment 1 Fedora Update System 2011-01-20 21:04:06 UTC
python-mechanize-0.1.10-3.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/python-mechanize-0.1.10-3.el5

Comment 2 Fedora Update System 2011-01-21 19:22:10 UTC
python-mechanize-0.1.10-3.el5 has been pushed to the Fedora EPEL 5 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update python-mechanize'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/python-mechanize-0.1.10-3.el5

Comment 3 Fedora Update System 2011-02-08 18:00:56 UTC
python-mechanize-0.1.10-3.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.