I'd also recommend (based on previous shooting myself in the foot) that all of your servers talk to your own internal yum repo if possible, and not directly to EPEL. Mirror EPEL if you want, but pull in updates in some process that lets you review them before putting them into your internal repo. This might help minimise surprises like this. I don't think there's a great way for the EPEL folks to know that for puppet going from 0.24.8 to 0.25 is a big deal, but for some other app going from version 0.x.y to version 0.z is a very minor deal.
Pete On Thu, Mar 4, 2010 at 12:24 PM, Matthew Macdonald-Wallace <mattmacw...@gmail.com> wrote: > On 4 March 2010 20:19, James Turnbull <ja...@lovedthanlost.net> wrote: >>> I am concerned that Epel jumped a major version that enforced so many >>> major changes, but I guess that's our fault for trusting that things >>> would stay the same! :P >>> >> >> I'll let the EPEL guys respond here but they only increment releases >> after extensive testing. > > Yeah, please don't misunderstand me, I'm not blaming EPEL on this one > at all. We should have checked that we were pinned to a version on > Puppet that we knew worked. > > Another one to add to the "Somebody else should learn from my mistakes" list! > :D > > M. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
