Panaman
2011-May-24 15:40 UTC
[Puppet Users] problem with rack versions and puppet-dashboard
I get this error can''t activate rack (~> 1.0.1), already activated rack-1.2.2 It appears that puppet-dashboard uses rack 1.0.1 but passenger 3.0.7 needs to use rack1.2.2 Is there a way around this or make dashboard use rack 1.2.2? -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
David Klann
2011-May-24 15:48 UTC
Re: [Puppet Users] problem with rack versions and puppet-dashboard
On Tue, 24 May 2011 10:40:03 -0500, you said:> I get this error > can''t activate rack (~> 1.0.1), already activated rack-1.2.2 > > It appears that puppet-dashboard uses rack 1.0.1 but passenger 3.0.7 > needs to use rack1.2.2 > > Is there a way around this or make dashboard use rack 1.2.2? >Don''t know if it''s the "supported" way to do it, but I simply removed the "embedded" version of rack that ships with puppet-dashboard: cd <path-to-dashboard> git clone git://github.com/puppetlabs/puppet-dashboard.git rm -r vendor/gems/rack-1.0.1 sed -i -e ''s,~> 1.0.1,~> 1.2.2,'' vendor/rails/actionpack/lib/action_controller.rb cp <my-config-path>/config.ru . sudo service httpd start (or however you start apache/nginx). Is there a recommended way to resolve this conflict? ~David Klann
Panaman
2011-May-25 12:34 UTC
[Puppet Users] Re: problem with rack versions and puppet-dashboard
On May 24, 11:48 am, David Klann <kl...@wins.net> wrote:> On Tue, 24 May 2011 10:40:03 -0500, you said: > > > I get this error > > can''t activate rack (~> 1.0.1), already activated rack-1.2.2 > > > It appears that puppet-dashboard uses rack 1.0.1 but passenger 3.0.7 > > needs to use rack1.2.2 > > > Is there a way around this or make dashboard use rack 1.2.2? > > Don''t know if it''s the "supported" way to do it, but I simply removed > the "embedded" version of rack that ships with puppet-dashboard: > > cd <path-to-dashboard> > git clone git://github.com/puppetlabs/puppet-dashboard.git > rm -r vendor/gems/rack-1.0.1 > sed -i -e ''s,~> 1.0.1,~> 1.2.2,'' vendor/rails/actionpack/lib/action_controller.rb > > cp <my-config-path>/config.ru . > sudo service httpd start (or however you start apache/nginx). > > Is there a recommended way to resolve this conflict? > > ~David Klann > > signature.asc > < 1KViewDownloadHey David, thanks, worked like a charm. Don''t know if there is a recommended way to resolve this conflict... but your way works :-) -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Reasonably Related Threads
- rack problems
- dashboard/passenger not connecting on port 8140
- Puppet dashboard over passenger: The environment must be purely alphanumeric, not ''
- dashboard 1.1.1 with filebucket doesn't show contents of the new file
- puppet dashboard gui looks odd from apache2