On Wed, 2005-09-07 at 23:21 -0500, Les Mikesell wrote: > On Wed, 2005-09-07 at 22:39, Greg Knaddison wrote: > > > > > Or better yet, > > > a way to tell it that you don't _want_ it to consider anything > > > that changed since you did an update on a different machine > > > and you want it now to apply exactly the same changes on > > > an important machine that you tested elsewhere (preferably > > > pulling from exactly the same repository mirror or using some > > > transaction checkpoint to ensure an identical operation). > > > > As long as you use specific instructions to yum like "yum install > > foo.1-3.386" and you have a clean and simple set of conf/repos files, > > then yum will do a very specific thing. If you have multiple > > repositories in your configuration and you just say "yum update" then > > it might not behave exactly as you desire. > > If you managed a set of servers running homegrown code that > may or may not be sensitive to library and utility program > versions, what steps would you use to keep a test server > up to date, then after performing any needed application > testing, to roll out the same changes to the production > servers in various different locations? The object is to > install exactly the updates you just tested in spite of any > subsequent repository changes or out-of-sync mirrors. > You would run a local mirror that only had the updates you tested on it :) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.centos.org/pipermail/centos/attachments/20050908/f482d212/attachment-0005.sig>