Bug 590071 - basemap data files need update
Summary: basemap data files need update
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-basemap-data
Version: el5
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jef Spaleta
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-07 16:20 UTC by joseph.lingevitch
Modified: 2010-09-22 08:08 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-09-22 08:08:28 UTC


Attachments (Terms of Use)

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



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


How reproducible:

Always

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: 

https://admin.fedoraproject.org/updates/python-basemap-data-0.99.4-1.el5

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. 

-jef

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.


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