Bug 590071

Summary: basemap data files need update
Product: [Fedora] Fedora EPEL Reporter: joseph.lingevitch
Component: python-basemap-dataAssignee: Jef Spaleta <jspaleta>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: el5CC: jspaleta, tremble
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-22 08:08:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description joseph.lingevitch 2010-05-07 16:20:50 UTC
Description of problem:

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

How reproducible:


Steps to Reproduce:
1. start ipython shell
2. import mpl_toolkits.basemap as basemap
3. m=basemap.Basemap()
Actual results:

IOError: Basemap unable to open boundary dataset file

Expected results:

Create a basemap instance

Additional info:

It appears from the error message, that the python-basemap-data and python-basemap-data-hires need to be updated to be compatible with python-basemap-0.99.4-6.el5.x86_64.rpm

Comment 1 Jef Spaleta 2010-05-07 17:28:50 UTC
It has been updated. And the update is sitting in epel-testing as part the QA guidelines.  Packages must either sit in testing for a minimum of two weeks before being released to stable.

Please test the python-basemap-data out of the epel-testing repository and provide positive karma here: 


yum --enablerepo=epel-testing update "python-basemap-data*"

to cherry pick the basemap-data updates from testing.

It's unfortunate that the -data package was not synced with the update to basemap. There was some miscommunication regarding updates to numpy and matplotlib.. and update to basemap was spun up quickly to address to sync with the matplotlib update already in the stable repository. The in the rush I forgot the -data package and filed it as an additional update a few days later. 


Comment 2 Mark Chappell 2010-09-22 08:08:28 UTC
The update that should fix this has been pushed to the main EPEL repos, I've just tested it and it appears to be working now, feel free to reopen the bug if it's still not working for you.