Bug #3127
gem provider will incorrectly consider gem with similar name is installed
| Status: | Closed | Start date: | 01/29/2010 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | package | |||
| Target version: | 2.6.8 | |||
| Affected Puppet version: | 0.25.4 | Branch: | https://github.com/jamtur01/puppet/tree/tickets/2.6.x/3127 | |
| Keywords: | ||||
| Votes: | 2 |
Description
If I have:
package { “json”:
ensure => installed,
provider => gem,
require => Exec["ruby setup.rb"]
}
while a gem called “json_pure” is installed, the “json” gem will not be installed since there is already a gem starting with the same name.
Related issues
History
Updated by Markus Roberts over 2 years ago
- Status changed from Unreviewed to Investigating
- Affected Puppet version changed from 0.24.5 to 0.25.4
This is much more likely to be 0.25.4 than 0.24.5
Updated by Peter Meier about 2 years ago
I can confirm that behavior with trying to install @mail@ when @maildir@ is installed
Updated by Piotr Stolc over 1 year ago
This bug is also present in 2.6.2
Here is my quick fix for this bug. I don’t know whether this fix doesn’t break something else in the provider ;)
Updated by Robin Powell about 1 year ago
Still present in 2.6.4
-Robin
Updated by James Turnbull about 1 year ago
- Status changed from Investigating to In Topic Branch Pending Review
- Target version set to 2.6.8
- Branch set to https://github.com/jamtur01/puppet/tree/tickets/2.6.x/3127
Updated by James Turnbull about 1 year ago
- Category set to package
- Status changed from In Topic Branch Pending Review to Merged - Pending Release
- Priority changed from Normal to Low
available in 2.6.next in commit:d2bacd308ea214151f5c1f43ec62aad8075da41b
Updated by Nick Lewis about 1 year ago
- Status changed from Merged - Pending Release to Closed