On 6/10/05, David Kewley <kewley@xxxxxxxxxxxxxxx> wrote: > Jeff gave a nice long reply on this, which I didn't totally > understand. :) I know enough about the yum/rpm/update/upgrade process > to do it on my own & handle unexpected outcomes as they crop up; I'll > not be following Jeff's guide, personally. I don't follow that guide either.. for system I'm actually going to use. It is however the best way I know to catelog problems that other more foolishly brave souls run into on the attempt. So when i see them complaining in public channels about it, casting stones and demanding help, I know with high confidence that they have attempted to do the live test to final upgrade and i lecture them accordingly. Not that you are going to be one of those people. I absolutely don't recommend doing live upgrades across the test to final release boundary...ever. But if I can't prevent someone from attempting it, at least I can do is help them try to avoid problems. > Regarding .rpmnew or .rpmsave files, I generally check those *whenever* > I update rpms, not just when I update from a last test version to an > actual final release. I really would like this problem solved in a more general way. I don't know of any way that the common self-adminning hobbiest/home user is going to know about the rpmnew/rpmsave files at all. There is no centralized way of being made aware of the creation of these files nor instructions on how to deal with them. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=158575 -jef