Thanks for your feedback, Chet. Looks like none of the old RPMs are available anymore. The environment is an undocumented bunch of small boxes, most of them running some web environment on top of RHEL ranging from 2.1 to 5.1. No two boxes are the same. Unless someone knows how to rebuild packages based on the binaries on the system, I guess I'll just have to risk it. Thanks, Alec > -----Original Message----- > From: chet.nichols@xxxxxxxxx > Sent: Fri, 2 May 2008 01:22:36 -0400 > To: redhat-list@xxxxxxxxxx > Subject: Re: rollback yum update for a single package? > > Hey Alec- > I'd say have as many of the old RPMs as you can available (especially the > RPM you're upgrading, for rolling back), do only a few at a time, check > what > dependencies it has, and make sure you have the older dependency RPMs as > well for rolling back. It kinda sucks, but in any rollback you'd need the > software packages to roll back to. > > Personally, we run huge clusters of the same server, so we'll update one, > and if nothing breaks, we'll roll it out to a subset of a cluster, and if > that looks good, then we'll roll it out everywhere. > > What types of services are running on the box? If it's stuff like httpd, > sshd, and other things that have updates, I'd strongly suggest updating > (and > not worry), since those packages probably contain somewhat important > security updates :D Along with that, basic daemons like that will include > updates that won't really affect any major functionality- just bug fixes. > If > it was something that was going to affect other parts of the system on an > upgrade, then there would be problems and people wouldn't schedule > regular > patching exercises. > > Then again, it all depends on your system(s) and what you're running- > feel > free to give some more info as to what the boxes run, what updates are > available, and what version(s) of RH you're running, and see if you can > get > some feedback. > > Good luck! > > Chet > > On Mon, Apr 28, 2008 at 6:17 AM, Alec O'Neill <alec.oneill@xxxxxxxxx> > wrote: > >> redhat-list@xxxxxxxxxx >> >> I have inherited a number of servers with various releases of Red Hat >> which look like they've been installed and then never been upgraded. >> I'd >> like to upgrade them all to the latest patch revisions, but in case >> something breaks, I want to be able to reverse the upgrade for a single >> package. Is there a way to do that? >> >> Thanks, >> >> Alec >> >> ____________________________________________________________ >> Receive Notifications of Incoming Messages >> Easily monitor multiple email accounts & access them with a click. >> Visit http://www.inbox.com/notifier and check it out! >> >> -- >> redhat-list mailing list >> unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe >> https://www.redhat.com/mailman/listinfo/redhat-list >> > > > > -- > /* > Chet Nichols III > mail: chet.nichols@xxxxxxxxx > (aim: chet / twitter: chet) > */ > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list ____________________________________________________________ FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop! Check it out at http://www.inbox.com/earth -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
