- From: Jesse Nelson <
>
- To:
- Subject: [chef] Re: Re: Re: Re: Re: Chef 0.8.10 CentOS/RHEL 5 packages - testing
- Date: Wed, 14 Apr 2010 08:19:20 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=w6K6quoP/mT3h/kZY8JefmJaOC8/mAdPyb5aCinF0H2iuaAzwuLuz24boGUYkWlAol nSbFvzwj+jTqgY1UfdQjxjOY6MmwR9hMle7dGhwuUi9eYJYfbnW6Zq/RvjP6mcNYPKyx m9WB1pu5LEYzQdqobFUxnhCvnD+8bl35tgDRE=
was an upgrade that i hit the pure conflicts. not a huge deal as its just on
a test server, but if this happens on client too thats sorta a pain.
i did a clean install using rubygem-chef-server as well to test if init
scripts got in place with the result of no init scripts. seems weird i can
test again on a fresh install. i had just rpm -e'd all rubygem-* stuff to
clean up.
On Apr 13, 2010, at 10:23 PM, Matthew Kent wrote:
>
Jesse Nelson wrote:
>
> it appears that these rpm's are not installing init scripts (the gems
>
> still have them), but the rpm's are not putting them in the right spots.
>
> also theres some issues with json and json-pure co-existance, but i don't
>
> know if those are resolvable in the scope of chef.
>
>
Odd, I received pretty much the same email offlist from someone else.
>
>
json_pure shouldn't be required if you are starting from scratch as I've
>
patched it out for rubygem-json. Are you seeing it pulled in and which
>
version? Is this an upgrade?
>
>
Init scripts are in subpackages:
>
>
:~$
>
rpm -q --filesbypkg chef | grep init.d
>
chef /etc/rc.d/init.d/chef-client
>
>
Are you not seeing them?
>
>
For upgrades I don't have a nice way to force them in, you'll have to
>
install the subpackages outlined on the wiki page.
>
>
Need more details.
>
--
>
Matthew Kent | http://magoazul.com
Archive powered by MHonArc 2.6.16.