On Thu, Jan 5, 2012 at 8:14 PM, Jo Rhett <jrh...@netconsonance.com> wrote: > On Jan 5, 2012, at 4:53 PM, Michael Stahnke wrote: > > You can install rpmdev-tools and run rpmdev-setuptree and it will > > > Yes of course but I wasn't documenting that here. > > The http://centos.karan.org/el5/ruby187/ are basically a drop-in > replacement for how the EL5 ruby stack worked, just upgraded to 1.8.7. > > > No, it combines in a bunch of other stuff *AND* it will not compile on the > stock EL5 system. > > Mock assumes a group of packages is installed prior to building. That > list of packages is > … > > If you have those installed, they should build cleanly. > > > Nope. karan's build requires a newer version of autoconf than is available > in CentOS or EPEL. The rpm I quoted has patches so that it will work with > the autoconf included in EL5. > > wget ${EPEL_MIRROR_OF_CHOICE}/5/SRPMS/ruby-mysql-2.7.3-1.el5.src.rpm > > rpm -i ruby-mysql-2.7.3-1.el5.src.rpm > > rpmbuild -ba ~/rpmbuild/SPECS/ruby-mysql.spec > > > Next thing is that Puppet Dashboard requires a newer version of Ruby Gems, > > but it doesn't tell you this. Instead it just barfs weird error messages. > > They need to rewrite their Rakefile to explicitly define the minimum > > versions. > > > Really? We ship rubygems 1.3.7 in Puppet Enterprise and I haven't > > > Yep, but you use macros only supported since 1.3.6. EL5 has 1.3.1 from > EPEL. > > You should be able yum install rubygem-rake from epel. (unless the > rubygems version change prevents that) > > > That ruby gem requires ruby-1.8.5. It only worked for me after I installed > 0.9.2 straight from gems. > > FYI, I've found some other issues: > > * puppet-dashboard-workers init script uses RH6-specific functions: > rhstatus_q fails on EL5. I had to write a manifest to overwrite that file > with something that doesn't use that function. You could write that to be > agnostic to the version (or provide an EL5-specific RPM)
This is not surprising. I'll gladly take patches on this. > > * the monitors run, but the workers die. They create pid files and then > exit. I can't figure out why. Right now I have to run them using the "env…" > command in the bootstrapping.html documentation. I'll resume chasing down > that issue on Monday. > > -- > Jo Rhett > Net Consonance : consonant endings by net philanthropy, open source and > other randomness > > -- > 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. -- 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.
