On Fri, Aug 6, 2010 at 11:39 PM, Jon Peatfield < [email protected]> wrote:
> On Fri, 6 Aug 2010, Arnau Bria wrote: > > But your _answer_ mentioned python-numpy NOT python-numeric: > Wops, you're right!! I mixed names at some point and got confused from then!!! So my previosu mails were completly wrong! Sorry !!! > I'd suggest removing the python-numpy and any rf/dag versions of >>> python-numeric from your repos and do the tests with just the sl5 >>> repos enabled... >>> >> >> I do need dag. removing it my question about numpy feature won't be >> answered. >> >> *Probably with only SL5 repos I won't have this problem cause only one >> package will server numpy feature. >> > > > But the sl5 repo contains numpy - and it seems to be newer than the version > in python-numpy anyway. > > The sl5 numpy package is a newer version so should be preferred but the > name isn't the same. > > What does: > > rpm -q --whatrequires python-numpy > > report on your machines? > [r...@td132 ~]# rpm -q --whatrequires python-numpy no package requires python-numpy > If you can't remove these (obsolete) packages from your repos then the > package clashes will > do you mean removing python-numpy from dag? yep, that is possible. so this will solve numpy/python-numpy issue. On the other hand, scipy requires old numpy, despite it's obsolte by python-numeric. ok, clear now. sorry about the confusion on MY OWN question :-S .... Troy, should the sl5 numpy package provide a python-numpy feature and > obsolete/conflict python-numpy to avoid this problem for people who have > this dag version present in their active repos? (or perhaps ask dag to > remove python-numpy) > > -- Jon > Cheers, Arnau
