Issue #18427 has been updated by Charlie Sharpsteen.

Status changed from Needs More Information to Investigating
Keywords changed from gems provider to gem server

Thanks a bunch for the clarification Luke. It looks like the gem server is 
indeed deciding to append the string " ruby" to the version numbers it is 
reporting. I was unable to re-produce this behavior with a quick test, I'll try 
to dig deeper.

A couple more questions:

  - Which operating system is hosting the gem server?

  - What version of Ruby is the gem server using? Is there any ruby version 
manager such as RVM or RBenv in use or was ruby installed through the system 
package manager?

  - Is the gem server from rubygems 1.4.0 or another version?

----------------------------------------
Bug #18427: gem package provider updates gems even if the gem is already at the 
latest revision
https://projects.puppetlabs.com/issues/18427#change-89232

* Author: Luke M
* Status: Investigating
* Priority: Normal
* Assignee: Charlie Sharpsteen
* Category: package
* Target version: 
* Affected Puppet version: 2.7.20
* Keywords: gem server
* Branch: 
----------------------------------------
Using: 

    package{'facter':
      ensure          => latest,
      provider        => 'gem',
      source          => "http://puppet:8808";,
    }

Produces:


    notice: /Stage[main]/Common_puppet::Hpux/Package[facter]/ensure: ensure 
changed '1.6.17' to '1.6.17 ruby'

This happens on every puppet run. 



-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to