On Mon, Sep 12, 2011 at 1:17 PM, Douglas Garstang
<doug.garst...@gmail.com> wrote:
> On Mon, Sep 12, 2011 at 1:08 PM, Ken Barber <k...@puppetlabs.com> wrote:
>>> The RPM for the puppet client came from the Puppet Labs website. I
>>> downloaded the source for 2.7.3, and had to make a few changes to the
>>> SPEC file
>>
>> (I keep asking this but ...) What OS are you running and version?
>> Where did you get the RPM's for 0.25?
>
> O/S on server is CentOS 5.4. O/S on client(s) is CentOS 5.5
>
> I answered this one in the previous message, but I got the source from
> Puppet Labs, modified the RPM spec file to make it work, and built the
> RPM's from that,.
>
>>
>> Also ... why don't you try these RPM's for 2.7.x:
>>
>> http://yum.puppetlabs.com/el/5/products
>
> Well, didn't know that existed. Maybe due to lack of documentation.
> Every time I've complained about the spec files not being maintained
> in the source code, Puppet labs people have said it wasn't their job
> to maintain the spec file. Given that there are pre-build RPM's on the
> puppet labs web site, I guess it's someone's job to maintain the spec
> file.
>
>>
>> I think Mike just updated these.
>
> I'll give the client a try first. Little more worried about updating the 
> server.

Uhm... what am I missing here?

[root@hproxy11 tmp]# rpm -i facter-1.6.0-1.x86_64.rpm
error: facter-1.6.0-1.x86_64.rpm: Header V4 RSA/SHA1 signature: BAD,
key ID 4bd6ec30
error: facter-1.6.0-1.x86_64.rpm cannot be installed

[root@hproxy11 tmp]# rpm -i puppet-2.7.3-1.el5.noarch.rpm
error: puppet-2.7.3-1.el5.noarch.rpm: Header V4 RSA/SHA1 signature:
BAD, key ID 4bd6ec30
error: puppet-2.7.3-1.el5.noarch.rpm cannot be installed

Doug

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to