still just playing with this… Not sure if this is an actual bug or a stupid noob (and inclined to believe PEBKAC)
If I try to bootstrap a new VM w/ CentOS 5.6 and a barebones install, seems that the bootstrap doesn’t have a method to download and install rpm-gpg key for the aegisco repository (and not entirely eager to shut off rpm-gpg checking)…
centos GPG key retrieval failed: [Errno 5] OSError: [Errno 2] No such file or directory: ‘/etc/pki/rpm-gpg/RPM-GPG-KEY-aegisco’
centos --2011-05-20 10:36:12-- http://production.cf.rubygems.org/rubygems/rubygems-1.3.7.tgz
centos Resolving production.cf.rubygems.org…
centos 216.137.33.18, 216.137.33.27, 216.137.33.34, …
centos Connecting to production.cf.rubygems.org|216.137.33.18|:80…
centos connected.
centos HTTP request sent, awaiting response…
centos 200 OK
centos Length: 290986 (284K) [application/octet-stream]
centos Saving to: rubygems-1.3.7.tgz.3' centos 0% [ ] 0 --.-K/s 7% [==> ] 23,266 103K/s 51% [===================> ] 149,448 333K/s 100%[======================================>] 290,986 546K/s in 0.5s centos centos 2011-05-20 10:36:13 (546 KB/s) -rubygems-1.3.7.tgz.3’ saved [290986/290986]
centos
centos bash: line 11: ruby: command not found
centos bash: line 14: gem: command not found
centos bash: line 15: gem: command not found
centos bash: line 16: gem: command not found
centos bash: line 17: gem: command not found
centos bash: line 73: /usr/bin/chef-client: No such file or directory
If I try to bootstrap a new VM w/ CentOS 5.6 and a barebones install, seems that the bootstrap doesn't have a method to download and install rpm-gpg key for the aegisco repository (and not entirely eager to shut off rpm-gpg checking)...
What problem are you trying to solve, that you don't have the GPG key
for the repository?
If I try to bootstrap a new VM w/ CentOS 5.6 and a barebones install, seems that the bootstrap doesn't have a method to download and install rpm-gpg key for the aegisco repository (and not entirely eager to shut off rpm-gpg checking)...
What problem are you trying to solve, that you don't have the GPG key
for the repository?
Bryan
trying to bootstrap the initial packaging (ie ruby doesn't get installed - centos 5 has ruby 1.8.5 and it seems obvious why the aegisco repository has a much newer version. I would suppose that I could install ruby from centos packages first but that still doesn't solve the problem with the lack of an rpm-gpg key
You will need ruby 1.8.7 and rubygems 1.6.2, at least, which are both
available from rpm.aegisco.com. If you need a newer version of rubygems, you
can compile from source. We'll post some new RPMs for rubygems soon as well.
If I try to bootstrap a new VM w/ CentOS 5.6 and a barebones install,
seems that the bootstrap doesn't have a method to download and install
rpm-gpg key for the aegisco repository (and not entirely eager to shut off
rpm-gpg checking)...
What problem are you trying to solve, that you don't have the GPG key
for the repository?
Bryan
trying to bootstrap the initial packaging (ie ruby doesn't get installed -
centos 5 has ruby 1.8.5 and it seems obvious why the aegisco repository has
a much newer version. I would suppose that I could install ruby from centos
packages first but that still doesn't solve the problem with the lack of an
rpm-gpg key
You will need ruby 1.8.7 and rubygems 1.6.2, at least, which are both
available from rpm.aegisco.com. If you need a newer version of rubygems, you
can compile from source. We'll post some new RPMs for rubygems soon as well.
James
I'm using this method right now and I made a knife bootstrap template
to use the rpms instead of manually installed rubygems. The rpm
doesn't link the chef-client binary into /usr/bin/chef-client where
the init script looks for it, so I'm doing that manually. I also added
a profile.d snippet to add the rubygems bin directory to the default
path.
You will need ruby 1.8.7 and rubygems 1.6.2, at least, which are both
available from rpm.aegisco.com. If you need a newer version of rubygems,
you
can compile from source. We'll post some new RPMs for rubygems soon as
well.
James
I'm using this method right now and I made a knife bootstrap template
to use the rpms instead of manually installed rubygems. The rpm
doesn't link the chef-client binary into /usr/bin/chef-client where
the init script looks for it, so I'm doing that manually. I also added
a profile.d snippet to add the rubygems bin directory to the default
path.
I'm all for improvements to the packaging of Chef/ruby/etc for CentOS, but
the profile.d modification strikes me as being one step too far. Can't
really justify it, just doesn't feel right.
On Fri, May 20, 2011 at 3:40 PM, James js@aegisco.com wrote:
Does anyone object to Matt's changes being included in the RPMs?
You will need ruby 1.8.7 and rubygems 1.6.2, at least, which are both
available from rpm.aegisco.com. If you need a newer version of
rubygems, you
can compile from source. We'll post some new RPMs for rubygems soon as
well.
James
I'm using this method right now and I made a knife bootstrap template
to use the rpms instead of manually installed rubygems. The rpm
doesn't link the chef-client binary into /usr/bin/chef-client where
the init script looks for it, so I'm doing that manually. I also added
a profile.d snippet to add the rubygems bin directory to the default
path.
I'd agree. The solution is to stick/symlink the bin somewhere that is
in root's path. profile.d scripts are fine for my own stuff but I'm in
agreement with Ian on other apps sticking stuff in there.
I'm all for improvements to the packaging of Chef/ruby/etc for CentOS, but
the profile.d modification strikes me as being one step too far. Can't
really justify it, just doesn't feel right.
On Fri, May 20, 2011 at 3:40 PM, James js@aegisco.com wrote:
Does anyone object to Matt's changes being included in the RPMs?
You will need ruby 1.8.7 and rubygems 1.6.2, at least, which are both
available from rpm.aegisco.com. If you need a newer version of
rubygems, you
can compile from source. We'll post some new RPMs for rubygems soon as
well.
James
I'm using this method right now and I made a knife bootstrap template
to use the rpms instead of manually installed rubygems. The rpm
doesn't link the chef-client binary into /usr/bin/chef-client where
the init script looks for it, so I'm doing that manually. I also added
a profile.d snippet to add the rubygems bin directory to the default
path.
I'm all for improvements to the packaging of Chef/ruby/etc for CentOS, but
the profile.d modification strikes me as being one step too far. Can't
really justify it, just doesn't feel right.
I'd agree, it was just a quick fix for us now. I assumed that the
aegisco rpm would at some point link the needed binaries. I wasn't
suggesting the profile.d hack be added to the rpm.
On Fri, May 20, 2011 at 12:56 PM, John E. Vincent (lusis) <lusis.org+ chef-list@gmail.com> wrote:
I'd agree. The solution is to stick/symlink the bin somewhere that is
in root's path. profile.d scripts are fine for my own stuff but I'm in
agreement with Ian on other apps sticking stuff in there.
I'm all for improvements to the packaging of Chef/ruby/etc for CentOS,
but
the profile.d modification strikes me as being one step too far. Can't
really justify it, just doesn't feel right.
On Fri, May 20, 2011 at 3:40 PM, James js@aegisco.com wrote:
Does anyone object to Matt's changes being included in the RPMs?
You will need ruby 1.8.7 and rubygems 1.6.2, at least, which are both
available from rpm.aegisco.com. If you need a newer version of
rubygems, you
can compile from source. We'll post some new RPMs for rubygems soon
as
well.
James
I'm using this method right now and I made a knife bootstrap template
to use the rpms instead of manually installed rubygems. The rpm
doesn't link the chef-client binary into /usr/bin/chef-client where
the init script looks for it, so I'm doing that manually. I also added
a profile.d snippet to add the rubygems bin directory to the default
path.
I'd agree. The solution is to stick/symlink the bin somewhere that is
in root's path. profile.d scripts are fine for my own stuff but I'm in
agreement with Ian on other apps sticking stuff in there.
I'm all for improvements to the packaging of Chef/ruby/etc for CentOS,
but
the profile.d modification strikes me as being one step too far. Can't
really justify it, just doesn't feel right.
On Fri, May 20, 2011 at 3:40 PM, James js@aegisco.com wrote:
Does anyone object to Matt's changes being included in the RPMs?
You will need ruby 1.8.7 and rubygems 1.6.2, at least, which are
both
available from rpm.aegisco.com. If you need a newer version of
rubygems, you
can compile from source. We'll post some new RPMs for rubygems soon
as
well.
James
I'm using this method right now and I made a knife bootstrap template
to use the rpms instead of manually installed rubygems. The rpm
doesn't link the chef-client binary into /usr/bin/chef-client where
the init script looks for it, so I'm doing that manually. I also added
a profile.d snippet to add the rubygems bin directory to the default
path.
On Fri, May 20, 2011 at 2:58 PM, James js@aegisco.com wrote:
Suggestion on where to symlink the bin to?
James
In my bootstrap template I symlinked it to /usr/bin/chef-client since
the chef-client cookbook fills /etc/init.d/chef-client from
/usr/lib/ruby/gems/1.8/gems/chef-0.10.0/distro/redhat/etc/init.d/chef-client
and that is what is contained there.
I think /usr/sbin would be great but the init script in the gem
content would need to be changed as well.