Issue #16729 has been updated by Michael Arnold.
As a home sysadmin (who does not mirror repos), I will be affected by this upgrade the next time I rebuild one of my test machines or patch one of my systems. I think using the approach of separate repos for major versions 2.x and 3.x might have been a better approach. It would let the end user have a finer control over which puppet version to use. Playing games with package names is horrible (just look at 10gen's mongodb packages for an example of what not to do). As an enterprise sysadmin (who mirrors repos), I am concerned with the shipment/upgrade of ruby 1.8.7 for EL5. I do understand that it is needed, but it is a replacement of an OS-shipped software which may well break support of third-part software. Yes, I could pin ruby but I never considered needing to do it before today. This leads to a point raised on the email thread (https://groups.google.com/d/msg/puppet-users/Q14kTSE0pvY/1AuBz13WGigJ): What is the PuppetLabs repository policy? Knowing that would be helpful. ---------------------------------------- Bug #16729: When using the puppetlabs repositories, `yum install puppet` should be safe. https://projects.puppetlabs.com/issues/16729#change-72507 Author: Robert Rothenberg Status: Unreviewed Priority: High Assignee: Category: package Target version: Affected Puppet version: 3.0.0 Keywords: Branch: I work for a small company that is not yet ready to upgrade Puppet to v3. This upgrade may or may not cause problems for us (especially since we use a masterless network), but the upgrade will require us to devote time to test the upgrade. It would be much better if there were separate names for the distributions, say, puppet2. Users who want to delay upgrades can install puppet2 and use that until they are ready. # Updates JJM - I changed the title because different package names are a prescribed solution. There is at least one other alternative proposal, which is to use different repositories for incompatible releases. Whatever we decide on, yum install puppet should be safe for the end user. Releasing incompatible packages to the repository makes this unsafe for end users. # References * [Puppet Users - Puppet 2.7 v 3.0 in the PuppetLabs yum repo](https://groups.google.com/forum/?fromgroups=#!topic/puppet-users/Q14kTSE0pvY) * [Puppet 3.0.0 Release Announcement](https://groups.google.com/d/topic/puppet-announce/lqmTBX9XDtw/discussion) * [Puppet 3.0.0 breaking changes relative to Puppet 2.7.x](http://links.puppetlabs.com/telly_breaking_changes) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
