A better route would be to do 'rpm -Uvh --test kernel-*.rpm iptables-*.rpm' which would deal with the 'catch-22' situation. --nodeps should be a last resort.
Michael -- Michael Viron Registered Linux User #81978 Senior Systems & Administration Consultant Web Spinners, University of West Florida At 11:41 AM 11/20/2001 -0500, you wrote: >I've found that in situations like this the --nodeps option helps, which >causes any dependencies to be ignored. > >- Kathy > >"Mitchell, Edmund" wrote: > >> Hello all >> >> So I thought I'd be all Tom Brinkman-like, and get the latest kernel. :) >> Did an rpm -Uvh --test, and it says iptables <= 1.2.4-1 conflicts with >> the 2.4.13 kernel. >> So I got the latest iptables rpm, and --test 'ed it, too, and it says >> it needs the 2.4.13 kernel. >> >> So I'm stuck in a catch-22, and I'm wondering what's the >> proper voodoo to make everyone go home happy. >> >> All this is happening on a (more or less) stock LM 8.1. >> >> Thanks for any help >> >> Edmund >> >> >> ------------------------------------------------------------------------ >> Want to buy your Pack or Services from MandrakeSoft? >> Go to http://www.mandrakestore.com > >-- >For God has not given us a spirit of fear, but of power and of love and of a >sound mind. - 2 Timothy 1:7 > > > >Want to buy your Pack or Services from MandrakeSoft? >Go to http://www.mandrakestore.com >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
