Upgrade to 1.1.1

Subscribe to Upgrade to 1.1.1 7 post(s), 2 voice(s)

 
Avatar Jeff Smith 8 post(s)

I had tried to upgrade my 1.0.4 installs this morning to 1.1.1, but I’m running into some issues. I’ve got my warehouse install set up with the shared directory, so I untarred the new version to my releases directory and ran rake warehouse:upgrade from within that new directory, but I ran into this:

rake warehouse:upgrade (in /var/www/rails/warehouse/releases/warehouse-1.1.1) rake aborted! No such file or directory - /var/www/rails/warehouse/shared/config/initializers/svn.rb or releases/warehouse-1.1.0/config/initializers

And a note on this error, the svn.rb file does in fact exist in my shared/config/initializers directory…

I was able to easily revert to my 1.0.4 install thanks to this structure, but I’d really like to be able to upgrade to the latest version. Thanks.

 
Avatar rick Administator 546 post(s)

I don’t know, permissions? It’s trying to symlink the files probably. rake warehouse:upgrade—trace should tell you where exactly it’s failing. I’ll upgrade my personal instance today and see how that works out.

 
Avatar Jeff Smith 8 post(s)

Not sure, but wondering if this might be an issue with the upgrade:

releases/warehouse-1.1.0/config/initializers

Seems to be referencing the previous build rather than the current 1.1.1.

I’m pretty sure it’s not permissions. I double-checked and my user has permission to write all the necessary symlinks. Here’s the output from my trace:

rake warehouse:upgrade --trace (in /var/www/rails/warehouse/releases/warehouse-1.1.1) ** Invoke warehouse:upgrade (first_time) ** Invoke warehouse:check_structure (first_time) ** Invoke warehouse:init_highline (first_time) ** Execute warehouse:init_highline ** Execute warehouse:check_structure ** Execute warehouse:upgrade rake aborted! No such file or directory - /var/www/rails/warehouse/shared/config/initializers/svn.rb or releases/warehouse-1.1.0/config/initializers /usr/local/lib/ruby/1.8/fileutils.rb:338:in `symlink' /usr/local/lib/ruby/1.8/fileutils.rb:338:in `ln_s' /usr/local/lib/ruby/1.8/fileutils.rb:1411:in `fu_each_src_dest0' /usr/local/lib/ruby/1.8/fileutils.rb:336:in `ln_s' /usr/local/lib/ruby/1.8/fileutils.rb:359:in `ln_sf' /var/www/rails/warehouse/releases/warehouse-1.1.1/lib/tasks/bootstrap.rake:16 /var/www/rails/warehouse/releases/warehouse-1.1.1/lib/tasks/bootstrap.rake:12:in `each' /var/www/rails/warehouse/releases/warehouse-1.1.1/lib/tasks/bootstrap.rake:12 /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `call' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:362:in `invoke' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in `synchronize' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in `invoke' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in `each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:in `standard_exception_handling' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1733:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1711:in `run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:in `standard_exception_handling' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1708:in `run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/bin/rake:7 /usr/local/bin/rake:16:in `load' /usr/local/bin/rake:16
 
Avatar rick Administator 546 post(s)

Oh, I bet I didn’t change the version number. Look in lib/warehouse.rb. I guess I’ll have a re-release to put out then. I need to put that into my release rake task somehow.

 
Avatar rick Administator 546 post(s)

Line 106, or wait a bit for the new release :)

It’s ready, just redownload v1.1.1. Thanks for pointing this out.

 
Avatar Jeff Smith 8 post(s)

Excellent, thanks for jumping on this so quickly Rick.

 
Avatar rick Administator 546 post(s)

No worries, it was a lame newbie mistake anyway.