On Wed, 2006-08-30 at 14:22 -0400, Jim Perrin wrote: > > Is there any thought to a parameter to tell yum to not look at object more > > recent than xx days. Often times (as exemplified by a recent bad patch with > > UBUNTU and with Fedora Core6), severe implications occurred. In the UBUNTU > > case, the patch broke the GUI, while with Core6, it broke YUM and hence > > YUMEX. > > > > So, the new option could be set to only accept patches that are more than xx > > days old. > > > > What say you? > > This strikes me as a function of the distribution/repository > maintainer, and not of yum. Ummm, yeah... Nobody should ever make a mistake. Then we wouldn't need most of these updates anyway... > For a distro like centos, most of the > 'new' packages in the repository are security/bugfix updates, and > should be applied without delay. > > There's a difference between a bugfix/security fix package and a > bleeding edge release that may or may not be stable. This idea seems > to be working around breakage by breaking more things. Bad mojo. Any change can break things, even if it is intended as a bug/security fix, and there are some machines where you really want someone else to do the testing first. I've always thought that yum should have an option to ignore anything newer than a specified timestamp just to make updates repeatable across a set of machines, but it is another good point that you may just want to be sure you have a few days to watch for problems that others mention on the mailing list before updating a critical server. I think the only way to have that kind of control now is to mirror a complete copy of all the repositories you use locally so they can age a bit. -- Les Mikesell lesmikesell@xxxxxxxxx
