The packages you need should be in EPEL. Have you tried the instructions
for CentOS 5.5 in the README[1]?
[1] http://github.com/puppetlabs/puppet-dashboard/blob/master/README.markdown
--
Rein Henrichs
http://puppetlabs.com
Thanks for detailing your installation procedure. We'll add it to the
Dashboard instructions.
If you or others have other OS-specific instructions, please feel free
to submit a patch against the docs.
> augeas-0.7.2-1
> augeas-libs-0.7.2-1
> facter-1.5.7
> ruby-augeas-0.3.0.1
>
The Puppet Dashboard doesn't require these packages -- I suspect these
were required as part of installing Puppet.
> From the Extra Packages for Enterprise Linux repository:
> ruby-mysql-2.7.3-1
> [...]
> I tried to install the mysql gem the same way, but got errors because
> ruby needed to be a higher revision.
> [...]
> [Instead installed from]
> http://rubyworks.rubyforge.org/redhat/4.9/RPMS/x86_64/rubygem-mysql-2.7-2
The "ruby-mysql" package from EPEL is recommended by the documentation
for newer versions of CentOS and provides a pre-compiled library that's
tricky to to build otherwise. Did the EPEL package work for you? If so,
there shouldn't have been a need to install it via `gem install
ruby-mysql` or from rubyworks. If not, can you please summarize what
happened?
> Finally install puppet-dashboard from rpm:
>
> http://yum.puppetlabs.com/base/puppet-dashboard-1.0.3-3.norarch.rpm
>
> --nodeps required. The package appears to use an rpm query to check
> dependencies, the rake gem wasn�t installed as an RPM, neither was
> rubygems so it fails.
>
> rpm �Uvh --nodeps puppet-dashboard-1.0.3-3.norarch.rpm
>
The packages assume you're running a newer version of CentOS. Your
`--nodeps` workaround for this is fine. Another approach would have been
to use a source-only version of the software downloaded from github.
Anyway, thank you for working through this and describing your experiences.
-igal
The rubyworks Ruby package probably reads libraries from different
directories than the EPEL ruby-mysql package is installed into and thus
can't be loaded, so your approach of installing the rubyworks version of
rubygems-mysql seems correct and necessary.
Thank you for the details, this will make it easier to write the
installation instructions for these older RHEL and CentOS releases.
-igal