Jira (PUP-5633) gem provider doesn't remove old gem version

[Daniel Parks (JIRA)]

Daniel Parks created an issue

Puppet / PUP-5633 gem provider doesn't remove old gem version Issue Type: Bug Affects Versions: PUP 4.2.3 Assignee: Unassigned Created: 2015/12/22 11:07 AM Priority: Normal Reporter: Daniel Parks Run the following Puppet code one after another: package { 'autosign': ensure => '0.0.10', provider => 'gem', } package { 'autosign': ensure => '0.1.1', provider => 'gem', } Result: $ gem list | fgrep autosign autosign (0.1.1, 0.0.10) Expected result: $ gem list | fgrep autosign autosign (0.1.1) This gets in the way of all kinds of stuff that expect only one version of a gem installed. This also affects pe_gem. Add Comment

This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

[Daniel Parks (JIRA)]

Daniel Parks commented on PUP-5633

Re: gem provider doesn't remove old gem version Other people have run into this. For example: http://stackoverflow.com/questions/17763569/puppet-controlling-installed-package-version

Add Comment

[Henrik Lindberg (JIRA)]

Henrik Lindberg updated an issue

Puppet / PUP-5633

gem provider doesn't remove old gem version

Change By: Henrik Lindberg Component/s: Types and Providers

Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Henrik Lindberg (JIRA)]

Henrik Lindberg updated an issue

Puppet / PUP-5633 gem provider doesn't remove old gem version

Change By: Henrik Lindberg Team: Agent

Add Comment

[Henrik Lindberg (JIRA)]

Henrik Lindberg updated an issue

Puppet / PUP-5633 gem provider doesn't remove old gem version

Change By: Henrik Lindberg Labels: triaged

Add Comment

[Branan Riley (JIRA)]

Branan Riley updated an issue

Puppet / PUP-5633 gem provider doesn't remove old gem version

Change By: Branan Riley Labels: gem package triaged type_and_provider

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Josh Cooper (Jira)]

Josh Cooper commented on PUP-5633

Re: gem provider doesn't remove old gem version The gem version isn't part of the "name" so when a new version is specified, puppet interprets that to mean install the 2nd version, not uninstall the old version and install the new version. To do that we'd need a parameter that indicates only the specified version(s) should be installed, and any version not listed should be uninstalled. It's similar to how the auth_membrership property controls members of a group. That said we're unlikely to fix this anytime soon. Please reopen if it's still a concern.

Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)