search

locomotivecms / engine

A platform to create, publish and edit sites
http://www.locomotivecms.com
Other
2.31k stars 626 forks source link

Bundler Update Fails #586

Closed greeneca closed 11 years ago

greeneca commented 11 years ago

Running bundle update on RC13 or master fails with the following error:

Bundler could not find compatible versions for gem "devise":
  In Gemfile:
    locomotive_cms (>= 0) ruby depends on
      devise (~> 2.1.2) ruby

    locomotive_cms (>= 0) ruby depends on
      devise (2.2.0)

I cannot find anywhere that devise 2.2.0 is required.

greeneca commented 11 years ago

So we figured it out. It seems it may be a bug with bundler. It is resolving the dependency for devise-encryptable first (>= 2.1.0.rc) and getting 2.2.0 and then resolving the devise dependency (~> 2.1.2). If you change the order of the dependencies so that devise is required first then it works. I will do a pull request.

greeneca commented 11 years ago

To get the bundle update working I had to do the following.

cantlin commented 11 years ago

Just as a heads up, this is currently happening on a fresh install following the instructions from your install page.

fcarrega commented 11 years ago

+1

Devise has been updated very recently. I installed a fresh instance of Locomotive two days ago without any issue. However I cannot run bundler today, experimenting the same Devise compatibility issue as the one stated above.

dugger commented 11 years ago

+1

My version numbers a little different, but same problem. I forked engine, but I've not found a solution yet.

Bundler could not find compatible versions for gem "devise":
In Gemfile:
  locomotive_cms (>= 0) ruby depends on
    devise (~> 2.1.2) ruby

  locomotive_cms (>= 0) ruby depends on
    devise (2.2.3)
dugger commented 11 years ago

I changed the devise requirement to 2.2.3 across the board and got bundle to run. Locomotive is running locally now, and I'm not seeing any problems locally yet. I'm not going to create a pull request until I've tested more throughly, but you can see my fork here: https://github.com/dugger/engine

did commented 11 years ago

thanks @dugger ! I just applied the instructions found here: https://github.com/plataformatec/devise/wiki/How-To:-Upgrade-to-Devise-2.2.

nonfungibletunji commented 11 years ago

u have double values for devise seem like a typo:

s.add_dependency 'devise', '~> 2.2.3' s.add_dependency 'devise-encryptable', '~> 0.1.1' s.add_dependency 'devise', '~> 2.2.3'

Bundler could not find compatible versions for gem "devise": In Gemfile: locomotive_cms (>= 0) ruby depends on devise (~> 2.1.2) ruby

locomotive_cms (>= 0) ruby depends on devise (2.2.3)

error still there

did commented 11 years ago

Hey S. Tunji (what is your first name btw :-) ) ! thanks for the double values. How does it behave if you run bundle update ?

nonfungibletunji commented 11 years ago

tunji alone is ok. but anyway i was able to make the changes by removing one of the values in the gemspec in my fork. and bundle update works.

asecondwill commented 11 years ago

What was the upshoot of this? I still get the error greeneca got with 2.0.0.rc12, I had to use 2.0.0.rc11 to get locomotive to install. Feels like im doing it wrong?

greeneca commented 11 years ago

This is a bug in bundler. The only sure fix right now that I have found is to fork devise-encryptabe and lock the version of devise at the same version locomotive uses and then fork locomotive and use your own version of devise-encryptable. This may be difficult if you are not running your own gem server and want to deploy to heroku. Charlie Greene 100088857

-----Original Message----- From: will notifications@github.com Date: Thu, 07 Feb 2013 14:48:06 To: locomotivecms/engineengine@noreply.github.com Reply-To: locomotivecms/engine reply@reply.github.com Cc: greenecagreeneca@gmail.com Subject: Re: [engine] Bundler Update Fails (#586)

What was the upshoot of this? I still get the error greeneca got with 2.0.0.rc12, I had to use 2.0.0.rc11 to get locomotive to install. Feels like im doing it wrong?

Reply to this email directly or view it on GitHub: https://github.com/locomotivecms/engine/issues/586#issuecomment-13266771

nonfungibletunji commented 11 years ago

My bundle update has no problems: My Loco gets rc13 also. Did you take out the double values for devise in your locomotive_cms.gemspec?

Using rake (10.0.3) Using RedCloth (4.2.9) Using i18n (0.6.1) Using multi_json (1.3.7) Using activesupport (3.2.11) Using builder (3.0.4) Using activemodel (3.2.11) Using erubis (2.7.0) Using journey (1.0.4) Using rack (1.4.4) Using rack-cache (1.2) Using rack-test (0.6.2) Using hike (1.2.1) Using tilt (1.3.3) Using sprockets (2.2.2) Using actionpack (3.2.11) Using mime-types (1.20.1) Using polyglot (0.3.3) Using treetop (1.4.12) Using mail (2.4.4) Using actionmailer (3.2.11) Using arel (3.0.2) Using tzinfo (0.3.35) Using activerecord (3.2.11) Using activeresource (3.2.11) Using bundler (1.3.0.pre.7) Using rack-ssl (1.3.3) Using json (1.7.6) Installing rdoc (3.12.1) Using thor (0.17.0) Using railties (3.2.11) Using rails (3.2.11) Using actionmailer-with-request (0.3.0) Using bcrypt-ruby (3.0.1) Using bson (1.5.2) Using bson_ext (1.5.2) Using cancan (1.6.7) Using carrierwave (0.6.2) Using mongo (1.5.2) Using mongoid (2.4.12) Using carrierwave-mongoid (0.2.1) Using cells (3.8.8) Using chunky_png (1.2.7) Using codemirror-rails (2.36) Using coffee-script-source (1.4.0) Using execjs (1.4.0) Using coffee-script (2.2.0) Using coffee-rails (3.2.2) Using fssm (0.2.10) Using sass (3.2.5) Using compass (0.12.2) Using compass-rails (1.0.3) Using custom_fields (2.1.0.rc2) Using daemons (1.1.9) Using orm_adapter (0.4.0) Using warden (1.2.1) Using devise (2.2.3) Using devise-encryptable (0.1.1) Using dragonfly (0.9.13) Using ejs (1.0.0) Using eventmachine (1.0.0) Using excon (0.13.4) Using flash_cookie_session (1.1.4) Using formatador (0.2.4) Installing net-ssh (2.6.5) Installing net-scp (1.0.6) Using nokogiri (1.5.6) Using ruby-hmac (0.4.0) Using fog (1.3.1) Using formtastic (2.2.1) Using haml (3.1.7) Using heroku-api (0.1.8) Using heroku-mongo-backup (0.4.3) Using highline (1.6.15) Using multi_xml (0.5.2) Using httparty (0.8.3) Using jquery-rails (2.1.4) Using kaminari (0.13.0) Using kgio (2.8.0) Installing locomotive-aloha-rails (0.20.1.5) Using locomotive-heroku (0.0.2) Using locomotive-mongoid-tree (0.6.2) Using locomotive-mongoid_migration (0.0.5) Installing locomotive-tinymce-rails (3.4.7.5) Using locomotive_liquid (2.4.2) Using mimetype-fu (0.1.2) Using rails-backbone (0.7.2) Using responders (0.9.3) Using rmagick (2.12.2) Using sanitize (2.0.3) Using stringex (1.5.1) Using locomotive_cms (2.0.0.rc13) from git://github.com/stunjiturner/engine.git (at master) Using raindrops (0.10.0) Using sass-rails (3.2.6) Using thin (1.5.0) Using uglifier (1.3.0) Installing unicorn (4.6.0) Your bundle is updated! Use bundle show [gemname] to see where a bundled gem is installed.

greeneca commented 11 years ago

It seems to be semi random whether it will fail or not. It has to do with the order in which bundler processes the gem dependencies. I have gotten it to work on sometimes but change some small thing (the version number of an unrlated gem ) breaks it again.
Charlie Greene 100088857

-----Original Message----- From: "S. Tunji Turner" notifications@github.com Date: Thu, 07 Feb 2013 17:02:01 To: locomotivecms/engineengine@noreply.github.com Reply-To: locomotivecms/engine reply@reply.github.com Cc: greenecagreeneca@gmail.com Subject: Re: [engine] Bundler Update Fails (#586)

My bundle update has no problems: My Loco gets rc13 also. Did you take out the double values for devise in your locomotive_cms.gemspec?

Using rake (10.0.3) Using RedCloth (4.2.9) Using i18n (0.6.1) Using multi_json (1.3.7) Using activesupport (3.2.11) Using builder (3.0.4) Using activemodel (3.2.11) Using erubis (2.7.0) Using journey (1.0.4) Using rack (1.4.4) Using rack-cache (1.2) Using rack-test (0.6.2) Using hike (1.2.1) Using tilt (1.3.3) Using sprockets (2.2.2) Using actionpack (3.2.11) Using mime-types (1.20.1) Using polyglot (0.3.3) Using treetop (1.4.12) Using mail (2.4.4) Using actionmailer (3.2.11) Using arel (3.0.2) Using tzinfo (0.3.35) Using activerecord (3.2.11) Using activeresource (3.2.11) Using bundler (1.3.0.pre.7) Using rack-ssl (1.3.3) Using json (1.7.6) Installing rdoc (3.12.1) Using thor (0.17.0) Using railties (3.2.11) Using rails (3.2.11) Using actionmailer-with-request (0.3.0) Using bcrypt-ruby (3.0.1) Using bson (1.5.2) Using bson_ext (1.5.2) Using cancan (1.6.7) Using carrierwave (0.6.2) Using mongo (1.5.2) Using mongoid (2.4.12) Using carrierwave-mongoid (0.2.1) Using cells (3.8.8) Using chunky_png (1.2.7) Using codemirror-rails (2.36) Using coffee-script-source (1.4.0) Using execjs (1.4.0) Using coffee-script (2.2.0) Using coffee-rails (3.2.2) Using fssm (0.2.10) Using sass (3.2.5) Using compass (0.12.2) Using compass-rails (1.0.3) Using custom_fields (2.1.0.rc2) Using daemons (1.1.9) Using orm_adapter (0.4.0) Using warden (1.2.1) Using devise (2.2.3) Using devise-encryptable (0.1.1) Using dragonfly (0.9.13) Using ejs (1.0.0) Using eventmachine (1.0.0) Using excon (0.13.4) Using flash_cookie_session (1.1.4) Using formatador (0.2.4) Installing net-ssh (2.6.5) Installing net-scp (1.0.6) Using nokogiri (1.5.6) Using ruby-hmac (0.4.0) Using fog (1.3.1) Using formtastic (2.2.1) Using haml (3.1.7) Using heroku-api (0.1.8) Using heroku-mongo-backup (0.4.3) Using highline (1.6.15) Using multi_xml (0.5.2) Using httparty (0.8.3) Using jquery-rails (2.1.4) Using kaminari (0.13.0) Using kgio (2.8.0) Installing locomotive-aloha-rails (0.20.1.5) Using locomotive-heroku (0.0.2) Using locomotive-mongoid-tree (0.6.2) Using locomotive-mongoid_migration (0.0.5) Installing locomotive-tinymce-rails (3.4.7.5) Using locomotive_liquid (2.4.2) Using mimetype-fu (0.1.2) Using rails-backbone (0.7.2) Using responders (0.9.3) Using rmagick (2.12.2) Using sanitize (2.0.3) Using stringex (1.5.1) Using locomotive_cms (2.0.0.rc13) from git://github.com/stunjiturner/engine.git (at master) Using raindrops (0.10.0) Using sass-rails (3.2.6) Using thin (1.5.0) Using uglifier (1.3.0) Installing unicorn (4.6.0) Your bundle is updated! Use bundle show [gemname] to see where a bundled gem is installed.

Reply to this email directly or view it on GitHub: https://github.com/locomotivecms/engine/issues/586#issuecomment-13271810

chandresh commented 11 years ago

Same problem for me with rc12

Bundler could not find compatible versions for gem "devise": In Gemfile: locomotive_cms (~> 2.0.0.rc12) ruby depends on devise (~> 2.1.2) ruby

locomotive_cms (~> 2.0.0.rc12) ruby depends on
  devise (2.2.3)
chandresh commented 11 years ago

Using rc11, I am able to run bundle.

nomasprime commented 11 years ago

Yep, confirm rc11 working but not rc12.

aledalgrande commented 11 years ago

Confirming rc12 broken and rc11 working.

nonfungibletunji commented 11 years ago

I have rc13 working

s. tunji turner sightuary :: firstsightmedia

On Mar 7, 2013, at 7:05 PM, Alessandro Dal Grande notifications@github.com wrote:

Confirming rc12 broken and rc11 working.

— Reply to this email directly or view it on GitHub.

aledalgrande commented 11 years ago

Is this rc13 you're talking about actually master?

nonfungibletunji commented 11 years ago

Yes

s. tunji turner sightuary :: firstsightmedia

On Mar 8, 2013, at 5:08 AM, Alessandro Dal Grande notifications@github.com wrote:

Is this rc13 you're talking about actually master?

— Reply to this email directly or view it on GitHub.

jasongonzales23 commented 11 years ago

The cake is a lie.

Jason Gonzales mobile and web development voice: 614.321.9690

On Fri, Mar 8, 2013 at 3:15 AM, S. Tunji Turner notifications@github.comwrote:

Yes

s. tunji turner sightuary :: firstsightmedia

On Mar 8, 2013, at 5:08 AM, Alessandro Dal Grande < notifications@github.com> wrote:

Is this rc13 you're talking about actually master?

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/locomotivecms/engine/issues/586#issuecomment-14614588 .

nonfungibletunji commented 11 years ago

Master

gem 'locomotive_cms', :git => 'git://github.com/stunjiturner/engine.git', :require => 'locomotive/engine'

this is how i am accessing the engine, but my fork is just a forked non-updated version of the original gem. My Bundle install pulls down rc13 of the engine and builds fine.

s. tunji turner sightuary :: firstsightmedia

On Mar 8, 2013, at 11:50 AM, Jason notifications@github.com wrote:

The cake is a lie.

Jason Gonzales mobile and web development voice: 614.321.9690

On Fri, Mar 8, 2013 at 3:15 AM, S. Tunji Turner notifications@github.comwrote:

Yes

s. tunji turner sightuary :: firstsightmedia

On Mar 8, 2013, at 5:08 AM, Alessandro Dal Grande < notifications@github.com> wrote:

Is this rc13 you're talking about actually master?

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/locomotivecms/engine/issues/586#issuecomment-14614588 .

— Reply to this email directly or view it on GitHub.