Issue #2061 has been updated by Ryan Conway.
I'm not sure we would be - surely when you set ensure => to a specific version,
that is the version you want to be running? Currently it is possible for a
version you are not ensuring to be present and to be running. Puppet will
report that it successfully downgraded the gem to the version you have set,
despite the newer version still being in use by the system?
I understand it's a tricky one, but maybe the Package provider could be updated
to be aware of this RubyGems specific behaviour, maybe by adding another
attribute to tell Puppet to purge other versions, for example:
package{ "puppet":
provider => gem,
ensure => "1.7.1",
purgeothers => true
}
----------------------------------------
Bug #2061: uninstall specific packages that are versionable
https://projects.puppetlabs.com/issues/2061
Author: Lawrence Ludwig
Status: Accepted
Priority: Normal
Assignee:
Category: package
Target version: unplanned
Affected Puppet version: 0.24.7
Keywords:
Branch:
While you can install specific versions via the 'ensure' option, you cannot
uninstall (remove) specific packages. Use case with Hudson issue:
Ruby's rake gem 0.8.4 was buggy with Hudson and had to downgrade to 0.8.3.
While I can specify to install 0.8.3 via Puppet, I could not make sure 0.8.4
was removed via puppet. Both versions existed.
The current workaround is using exec hack.
--
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.
