Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 455005 - file conflict with python-matplotlib
Summary: file conflict with python-matplotlib
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-basemap
Version: rawhide
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Jef Spaleta
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-11 12:25 UTC by John Ellson
Modified: 2008-07-11 23:53 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-11 23:53:09 UTC


Attachments (Terms of Use)

Description John Ellson 2008-07-11 12:25:07 UTC
Description of problem:
    /usr/lib64/python2.5/site-packages/mpl_toolkits/__init__.pyc
conflicts with:
    python-matplotlib-0.98.1-1.fc10.x86_64

Version-Release number of selected component (if applicable):
python-basemap-0.99-1.fc10.x86_64
python-matplotlib-0.98.1-1.fc10.x86_64

How reproducible:
100%

Steps to Reproduce:
1. yum update python-basemap
2.
3.
  
Actual results:
Transaction Check Error:
  file /usr/lib64/python2.5/site-packages/mpl_toolkits/__init__.pyc from install
of python-basemap-0.99-1.fc10.x86_64 conflicts with file from package
python-matplotlib-0.98.1-1.fc10.x86_64
  file /usr/lib64/python2.5/site-packages/mpl_toolkits/__init__.pyo from install
of python-basemap-0.99-1.fc10.x86_64 conflicts with file from package
python-matplotlib-0.98.1-1.fc10.x86_64


Expected results:


Additional info:

Comment 1 Jef Spaleta 2008-07-11 15:58:08 UTC
Now see that's just extremely silly of me.

I'm on it.

-jef

Comment 2 Jef Spaleta 2008-07-11 23:53:09 UTC
Fixed and built new python-basemap in development.


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