Bug 842870 - python-basemap cannot be imported in epel6
Summary: python-basemap cannot be imported in epel6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-basemap
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jef Spaleta
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-24 19:03 UTC by Kevin Fenzi
Modified: 2015-04-22 22:49 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-07-31 17:00:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1125032 0 unspecified CLOSED python-basemap cannot be imported in epel6 2021-02-22 00:41:40 UTC

Internal Links: 1125032

Description Kevin Fenzi 2012-07-24 19:03:24 UTC
On a rhel6.3 box: 

% python
Python 2.6.6 (r266:84292, May  1 2012, 13:52:17) 
[GCC 4.4.6 20110731 (Red Hat 4.4.6-3)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from mpl_toolkits.basemap import Basemap
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib64/python2.6/site-packages/mpl_toolkits/basemap/__init__.py", line 38, in <module>
    import pyproj, sys, os, math, dbflib
  File "/usr/lib64/python2.6/site-packages/mpl_toolkits/basemap/pyproj.py", line 48, in <module>
    from _proj import Proj as _Proj
  File "c_numpy.pxd", line 76, in _proj (src/_proj.c:3234)
ValueError: numpy.dtype does not appear to be the correct type object

Comment 1 Patrice Dumas 2012-07-30 11:03:13 UTC
I see the same issue.  I think this comes from the recent numpy upgrade.  I rebuilt the basemap rpm and it works now.

Comment 2 Matt Domsch 2012-07-30 13:33:28 UTC
Devrim kicked off a build.

http://koji.fedoraproject.org/koji/taskinfo?taskID=4342411

Comment 3 Fedora Update System 2012-07-30 14:14:53 UTC
python-basemap-0.99.4-11.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/python-basemap-0.99.4-11.el6

Comment 5 Fedora Update System 2012-07-30 17:29:51 UTC
Package python-basemap-0.99.4-11.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 python-basemap-0.99.4-11.el6'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-6551/python-basemap-0.99.4-11.el6
then log in and leave karma (feedback).

Comment 6 Kevin Fenzi 2012-07-30 19:18:51 UTC
This seems to work here. ;) thanks.

Comment 7 Fedora Update System 2012-07-31 17:00:12 UTC
python-basemap-0.99.4-11.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Jef Spaleta 2012-07-31 17:28:45 UTC
thank you guys for taking care of this.  I'm at a remote radar site at the moment and I don't have an EPEL system with me.

Which reminds me I need to make a formal announcement about my upcoming one month of completely off the grid status.

-jef

Comment 9 Gregory Hennessy 2014-07-09 19:52:05 UTC
I think this bug may have come back. As of today, 9 July 2014, on a redhat 6.5 machine:

[gsh@localhost local_place]$ python
Python 2.6.6 (r266:84292, Nov 21 2013, 10:50:32) 
[GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from mpl_toolkits import basemap
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib64/python2.6/site-packages/mpl_toolkits/basemap/__init__.py", line 38, in <module>
    import pyproj, sys, os, math, dbflib
  File "/usr/lib64/python2.6/site-packages/mpl_toolkits/basemap/pyproj.py", line 48, in <module>
    from _proj import Proj as _Proj
  File "c_numpy.pxd", line 76, in _proj (src/_proj.c:3234)
ValueError: numpy.dtype does not appear to be the correct type object
>>> import numpy
>>> print numpy.__version__
1.8.1
>>>

Comment 10 Orion Poplawski 2015-04-22 22:49:09 UTC
(In reply to Gregory Hennessy from comment #9)
> >>> print numpy.__version__
> 1.8.1

Yeah, that's likely not going to work.  We're expecting numpy 1.4.1 in EL6:

numpy.x86_64        1.4.1-9.el6             @rhel-6-server-rpms

See also new bug #1125032


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