Switching provider to 'rpm' fixes the issue reported above, BUT creates 
another issue in its place. Mind you, now the issue is with installing 
OpenSSL and OpenSSL-Devel rpms that were patched against Heartbleed and 
getting a mess of dependency errors. Any suggestions?

On Tuesday, July 8, 2014 9:27:19 AM UTC-4, jcbollinger wrote:
>
>
>
> On Monday, July 7, 2014 3:54:50 PM UTC-5, Jonathan Rose wrote:
>>
>> I tried fiddling around with a puppet module I am writing to install 
>> RPM's both from repository as well as local resources (e.g. http) and tried 
>> the advise noted by David Caro, but I'm still getting error messages:
>>
>> Skipping.
>> Error: Nothing to do
>> returned 1: Cannot open: 
>>
>>
>
> David's advice is unfortunately un-sound.  You do not normally need to use 
> the "name" parameter with the 'yum' package provider, because yum normally 
> uses the package name as the desired RPM name.  That is, simply:
>
> package { 'my-package-name':
>     ensure => 'installed',
> }
>
> Note that that's normally just the *package* name as it will be recorded 
> in the RPM database, not the RPM filename.  But that only works if the 
> specified package is in one of the yum package repositories that your 
> system is already configured to use.  Your objective here appears to be to 
> configure a package repository that may not already be configured, and for 
> that you cannot use the 'yum' provider at all -- it's simply not the way 
> Yum works.
>
> If you want to manage an RPM package from a specific local or http[s] 
> source that you specify, then you need to ensure that the 'rpm' provider be 
> used.  On most systems that use RPMs, the default provider is something 
> more flexible, such as 'yum', so you need to declare the 'rpm' provider 
> specifically if you want to use it (i.e. what Mark wrote).  Note also 
> Jonathan's comments about package dependencies, which are the reason other 
> providers are preferred to the plain 'rpm' provider for most purposes.  
> Dependencies should not be an issue for your particular case, so probably 
> this will work:
>
> package { 'puppetlabs-release':
>   ensure => 'installed',
>   source => 'https://yum.puppetlabs.com/el/6/products/x86_64/puppetlabs-
> release-6-5.noarch.rpm',
>   provider => 'rpm'
> }
>
>
> John
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/79812e54-f736-4dd6-bb0c-022bb85ee0be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to