On 04.02.2013 12:55, Chux wrote:
Nick,
This is not looking promising .. dapper is on ruby 1.8.4, and the
nearest ubuntu version that could get me up to ruby 1.8.5 is feisty ..
So, I modified apt preferences, to try and pull in the right versions of
ruby from feisty (had to do the same for puppet and facter) .. However,
the major show-stopper in this direction is glibc ...
I need glibc >= 2.5, but the highest possible for dapper (without
risking bricking the system) is glibc 2.3.6 ...
Can http://rvm.io build a "local" ruby for you on that system?
Regards, D.
So, I am afraid this is a no go .. Thanks for the insight you have provided.
best regards ..
On Saturday, 2 February 2013 01:51:03 UTC, Nick Fagerlund wrote:
You're in a gnarly situation. DistroWatch is telling me that you're
probably running Ruby 1.8.4, which, damn.
I think your best bet is:
* Find or build a newer Ruby, preferably 1.8.7.
* Either install Puppet from source
(http://docs.puppetlabs.com/guides/from_source.html
<http://docs.puppetlabs.com/guides/from_source.html>) or force apt
to install a Puppet package meant for a newer distro. I... THINK the
packages from the Puppet Labs repo ought to limp along just fine if
the Ruby is new enough, but I've never heard of it being tried with
Dapper.
Good luck with that.
On Friday, February 1, 2013 10:18:49 AM UTC-8, Chux wrote:
Hi,
I have a client that I cannot upgrade from ubuntu 6.06 (due to
application dependency issues) ... I have been able to get
puppet/facter installed on it, but it seems unable to make
certificate requests ..
============
#/usr/sbin/puppetd -d -t -v
err: No certificate; running with reduced functionality.
info: Creating a new certificate request for
cofkedit.bodleian.ox.ac.uk <http://cofkedit.bodleian.ox.ac.uk>
info: Requesting certificate
warning: peer certificate won't be verified in this SSL session
err: Could not call puppetca.getcert: #<RuntimeError:
HTTP-Error: 400 Bad Request>
err: Could not request certificate: Certificate retrieval
failed: HTTP-Error: 400 Bad Request
==================
I have seem a few admonitions against using clients that are
old, but I have no choice in this one if I hope to deploy puppet
on it .. or are there work arounds I can attempt ?
--
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.