Re: odd issue with bundler, rails3, on bamboo 1.9.2
remove mongrel from your Gemfile. It introduces the dependency to the older daemon. On 5 Nov, 18:19, Keenan Brock wrote: > I'd move the requirement for daemons closer to the beginning in your Gemfile. > So it will trump the other gem that requires a lower version. > > On Nov 5, 2010, at 1:04 PM, Steve Smith wrote: > > > No sorry it is good practice I wanted to make sure that it was included > > sorry, but if you open up the lock file locally you should be able to see > > what is requiring daemons 1.1.0. or at least what may be requiring daemons. > > Do you need that specific version of daemons or would 1.1.0 work for you? > > > I actually thought this was what the lock file is supposed to be solving > > though. Does anyone else know why it may not be being used? > > > Steve > > > On 5 Nov 2010, at 16:56, Kyle Bragger wrote: > > >> Yes lockfile is Commited. Read that was good practice. Not so? > > >> On 5 Nov., 12:52, Steve Smith wrote: > >>> I have a feeling daemons 1.1.0 is included as a requirement of something > >>> else, are you also committing the lock file? The lock file should also > >>> show you what is requiring what. > > >>> Steve > > >>> --http://cloudmailin.com > >>> @cloudmailin > >>> Incoming email for your web app > > >>> On 5 Nov 2010, at 16:45, Kyle Bragger wrote: > > Hey all — setting up a vanilla Rails 3 app on the bamboo 1.9.2 stack > and getting the following: > > You have already activated daemons 1.1.0, but your Gemfile > requires daemons 1.0.10. Consider using bundle exec. > > Maybe I'm missing something obvious, but if the gemfile specifies the > daemons version, why would Heroku barf? > > Thanks for the help! > > Here is my Gemfile: > > source 'http://rubygems.org' > > gem 'rails', '3.0.1' > > # Bundle edge Rails instead: > # gem 'rails', :git => 'git://github.com/rails/rails.git' > > gem 'pg' > gem 'devise' > gem 'paperclip' > > gem 'daemons', '1.0.10' > > group :development do > #gem 'test-unit' > #gem 'redgreen' > gem 'mongrel' > gem 'heroku_san' > end > > -- > You received this message because you are subscribed to the Google > Groups "Heroku" group. > To post to this group, send email to her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://groups.google.com/group/heroku?hl=en. > > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "Heroku" group. > >> To post to this group, send email to her...@googlegroups.com. > >> To unsubscribe from this group, send email to > >> heroku+unsubscr...@googlegroups.com. > >> For more options, visit this group > >> athttp://groups.google.com/group/heroku?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to her...@googlegroups.com. > > To unsubscribe from this group, send email to > > heroku+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: odd issue with bundler, rails3, on bamboo 1.9.2
I'd move the requirement for daemons closer to the beginning in your Gemfile. So it will trump the other gem that requires a lower version. On Nov 5, 2010, at 1:04 PM, Steve Smith wrote: > No sorry it is good practice I wanted to make sure that it was included > sorry, but if you open up the lock file locally you should be able to see > what is requiring daemons 1.1.0. or at least what may be requiring daemons. > Do you need that specific version of daemons or would 1.1.0 work for you? > > I actually thought this was what the lock file is supposed to be solving > though. Does anyone else know why it may not be being used? > > Steve > > > On 5 Nov 2010, at 16:56, Kyle Bragger wrote: > >> Yes lockfile is Commited. Read that was good practice. Not so? >> >> On 5 Nov., 12:52, Steve Smith wrote: >>> I have a feeling daemons 1.1.0 is included as a requirement of something >>> else, are you also committing the lock file? The lock file should also show >>> you what is requiring what. >>> >>> Steve >>> >>> --http://cloudmailin.com >>> @cloudmailin >>> Incoming email for your web app >>> >>> On 5 Nov 2010, at 16:45, Kyle Bragger wrote: >>> >>> >>> Hey all — setting up a vanilla Rails 3 app on the bamboo 1.9.2 stack and getting the following: >>> You have already activated daemons 1.1.0, but your Gemfile requires daemons 1.0.10. Consider using bundle exec. >>> Maybe I'm missing something obvious, but if the gemfile specifies the daemons version, why would Heroku barf? >>> Thanks for the help! >>> Here is my Gemfile: >>> source 'http://rubygems.org' >>> gem 'rails', '3.0.1' >>> # Bundle edge Rails instead: # gem 'rails', :git => 'git://github.com/rails/rails.git' >>> gem 'pg' gem 'devise' gem 'paperclip' >>> gem 'daemons', '1.0.10' >>> group :development do #gem 'test-unit' #gem 'redgreen' gem 'mongrel' gem 'heroku_san' end >>> -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/heroku?hl=en. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Heroku" group. >> To post to this group, send email to her...@googlegroups.com. >> To unsubscribe from this group, send email to >> heroku+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/heroku?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: odd issue with bundler, rails3, on bamboo 1.9.2
No sorry it is good practice I wanted to make sure that it was included sorry, but if you open up the lock file locally you should be able to see what is requiring daemons 1.1.0. or at least what may be requiring daemons. Do you need that specific version of daemons or would 1.1.0 work for you? I actually thought this was what the lock file is supposed to be solving though. Does anyone else know why it may not be being used? Steve On 5 Nov 2010, at 16:56, Kyle Bragger wrote: > Yes lockfile is Commited. Read that was good practice. Not so? > > On 5 Nov., 12:52, Steve Smith wrote: >> I have a feeling daemons 1.1.0 is included as a requirement of something >> else, are you also committing the lock file? The lock file should also show >> you what is requiring what. >> >> Steve >> >> --http://cloudmailin.com >> @cloudmailin >> Incoming email for your web app >> >> On 5 Nov 2010, at 16:45, Kyle Bragger wrote: >> >> >> >>> Hey all — setting up a vanilla Rails 3 app on the bamboo 1.9.2 stack >>> and getting the following: >> >>>You have already activated daemons 1.1.0, but your Gemfile >>> requires daemons 1.0.10. Consider using bundle exec. >> >>> Maybe I'm missing something obvious, but if the gemfile specifies the >>> daemons version, why would Heroku barf? >> >>> Thanks for the help! >> >>> Here is my Gemfile: >> >>> source 'http://rubygems.org' >> >>> gem 'rails', '3.0.1' >> >>> # Bundle edge Rails instead: >>> # gem 'rails', :git => 'git://github.com/rails/rails.git' >> >>> gem 'pg' >>> gem 'devise' >>> gem 'paperclip' >> >>> gem 'daemons', '1.0.10' >> >>> group :development do >>> #gem 'test-unit' >>> #gem 'redgreen' >>> gem 'mongrel' >>> gem 'heroku_san' >>> end >> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Heroku" group. >>> To post to this group, send email to her...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> heroku+unsubscr...@googlegroups.com. >>> For more options, visit this group >>> athttp://groups.google.com/group/heroku?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: odd issue with bundler, rails3, on bamboo 1.9.2
Yes lockfile is Commited. Read that was good practice. Not so? On 5 Nov., 12:52, Steve Smith wrote: > I have a feeling daemons 1.1.0 is included as a requirement of something > else, are you also committing the lock file? The lock file should also show > you what is requiring what. > > Steve > > --http://cloudmailin.com > @cloudmailin > Incoming email for your web app > > On 5 Nov 2010, at 16:45, Kyle Bragger wrote: > > > > > Hey all — setting up a vanilla Rails 3 app on the bamboo 1.9.2 stack > > and getting the following: > > > You have already activated daemons 1.1.0, but your Gemfile > > requires daemons 1.0.10. Consider using bundle exec. > > > Maybe I'm missing something obvious, but if the gemfile specifies the > > daemons version, why would Heroku barf? > > > Thanks for the help! > > > Here is my Gemfile: > > > source 'http://rubygems.org' > > > gem 'rails', '3.0.1' > > > # Bundle edge Rails instead: > > # gem 'rails', :git => 'git://github.com/rails/rails.git' > > > gem 'pg' > > gem 'devise' > > gem 'paperclip' > > > gem 'daemons', '1.0.10' > > > group :development do > > #gem 'test-unit' > > #gem 'redgreen' > > gem 'mongrel' > > gem 'heroku_san' > > end > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to her...@googlegroups.com. > > To unsubscribe from this group, send email to > > heroku+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: odd issue with bundler, rails3, on bamboo 1.9.2
I have a feeling daemons 1.1.0 is included as a requirement of something else, are you also committing the lock file? The lock file should also show you what is requiring what. Steve -- http://cloudmailin.com @cloudmailin Incoming email for your web app On 5 Nov 2010, at 16:45, Kyle Bragger wrote: > Hey all — setting up a vanilla Rails 3 app on the bamboo 1.9.2 stack > and getting the following: > >You have already activated daemons 1.1.0, but your Gemfile > requires daemons 1.0.10. Consider using bundle exec. > > Maybe I'm missing something obvious, but if the gemfile specifies the > daemons version, why would Heroku barf? > > Thanks for the help! > > Here is my Gemfile: > > source 'http://rubygems.org' > > gem 'rails', '3.0.1' > > # Bundle edge Rails instead: > # gem 'rails', :git => 'git://github.com/rails/rails.git' > > gem 'pg' > gem 'devise' > gem 'paperclip' > > gem 'daemons', '1.0.10' > > group :development do > #gem 'test-unit' > #gem 'redgreen' > gem 'mongrel' > gem 'heroku_san' > end > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
odd issue with bundler, rails3, on bamboo 1.9.2
Hey all — setting up a vanilla Rails 3 app on the bamboo 1.9.2 stack and getting the following: You have already activated daemons 1.1.0, but your Gemfile requires daemons 1.0.10. Consider using bundle exec. Maybe I'm missing something obvious, but if the gemfile specifies the daemons version, why would Heroku barf? Thanks for the help! Here is my Gemfile: source 'http://rubygems.org' gem 'rails', '3.0.1' # Bundle edge Rails instead: # gem 'rails', :git => 'git://github.com/rails/rails.git' gem 'pg' gem 'devise' gem 'paperclip' gem 'daemons', '1.0.10' group :development do #gem 'test-unit' #gem 'redgreen' gem 'mongrel' gem 'heroku_san' end -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
