Description of problem:
The package python-basemap-data depends on the package python-basemap. Therefore, if one wants to remove just python-basemap (perhaps, to install from source), the package manager then wants to remove python-basemap-data. It is also feasible that one may want to use python-basemap-data for other use without using python-basemap.
python-basemap should definitely depend on python-basemap-data, but I don't see a reason for the other way around.
Version-Release number of selected component (if applicable):
At least as far back as fedora 11.
You know, that makes some sense.
I'll make the change in rawhide. But considering the size of the data package I'm not inclined to roll an update with just this change for any fedora release. I don't want to push a 100M+ package down the tubes just for a minor packaging issue.
Fine by me, but I wish noticed it before this recent release. Makes me wonder when rpmdeltas are going to become standard...
I can roll packages for you in the build system I guess...and stage the change so its picked up by any subsequent update..but even with deltas I'm not sure its worth pushing to the update repo by itself. If a more substantial update is needed...I'll definitely include this change. As well as moving the examples subpackage to the python-basemap srpm.
No thanks, I am now using the svn checkout from matplotlib. I merely noticed the potential issue when I was removing the basemap package to prepare for the installation from source.
Staging it sounds like a good idea on the off-chance that there is an update to the data. I have no opinion about the examples, as I usually use the online documentation instead.
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.