On Wed, 2005-05-18 at 12:54 -0400, Jake Colman wrote: > Seth, > > So do I now have a catch-22 situation? Since 'apache' changed to 'httpd' the > squirrelmail package gets upset. But a newer squirrelmail will need httpd > which I don't yet have and cannot get! How do I break the circle? > > Once I do break this circle, will a 'yum upgrade' work without the issues > reported by my 'yum update'? I would hope so since the 'upgrade; knows > what's obsolete and should take care of itself, right? No, all you have to do is: 1. provide a new squirrelmail package in another repo or 2. remove squirrelmail temporarily, update your system, put back a squirrelmail rpm that works. -sv
