instiki upgrade fails

Downloading http://rubyforge.org/frs/download.php/75325/instiki-0.19.3.zip .. Downloading http://files.rubyforge.vm.bytemark.co.uk/instiki/instiki-0.19.3.zip (23.98 MB) .. Received 1024 bytes (0 %) Received 2.40 MB (10 %) Received 4.80 MB (20 %) Received 7.20 MB (30 %) Received 9.59 MB (40 %) Received 11.99 MB (50 %) Received 14.39 MB (60 %) Received 16.79 MB (70 %) Received 19.19 MB (80 %) Received 21.58 MB (90 %) Received 23.98 MB (100 %) .. download complete.

Installing Ruby Gem test-spec .. .. done Installing Ruby Gem camping .. .. done

Installing Ruby Gem fcgi .. .. done

Installing Ruby Gem memcache-client .. .. done

Installing Ruby Gem ruby-openid .. .. done

Installing Ruby Gem rack .. .. done

Installing Ruby Gem rake .. .. done

Installing Ruby Gem mongrel .. .. done

Installing Ruby Gem sqlite3-ruby .. .. done

Applying web server configuration .. .. done

Now installing Instiki version 0.19.3 .. Failed to extract source : cp: cannot overwrite non-directory REDACTED/public_html/errol/vendor/rails/actionpack/test/fixtures/layout_tests/layouts/symlinked' with directory/home/.webmin/637178_3_script_install.cgi/instiki-0.19.3/vendor/rails/actionpack/test/fixtures/layout_tests/layouts/symlinked' .. failed! See the error message above for the reason why. Applying web server configuration .. .. done

Status: 
Active

Comments

Passing this one over to Jamie...

Is /home/seren/domains/lion.serengeti.com/public_html/errol/vendor/rails/actionpack/test/fixtures/layout_tests/layouts/symlinked a symbolic link on your system? If so, a work-around may be to just delete it ..

I did that and now when mongrel tries to start I get...

Found http://rubyforge.org:80/frs/download.php/75325/instiki-0.19.3.zip in cache ..

Installing Ruby Gem test-spec .. .. done Installing Ruby Gem camping .. .. done

Installing Ruby Gem fcgi .. .. done

Installing Ruby Gem memcache-client .. .. done

Installing Ruby Gem ruby-openid .. .. done

Installing Ruby Gem rack .. .. done

Installing Ruby Gem rake .. .. done

Installing Ruby Gem mongrel .. .. done

Installing Ruby Gem sqlite3-ruby .. .. done

Applying web server configuration .. .. done

Now installing Instiki version 0.19.3 .. Mongrel server did not start : NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /REDACTED/public_html/instiki/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21. instiki: invalid option: --prefix .. failed! See the error message above for the reason why. Applying web server configuration .. .. done

Hey, can I get an update on this? I pay for support and I haven't heard a response on this in 2 weeks. I just tried a straight up install of instiki through install scripts and it fails with...

Now installing Instiki version 0.19.3 .. Mongrel server did not start : NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /REDACTED/public_html/instiki/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21. instiki: invalid option: --prefix .. failed! See the error message above for the reason why. Applying web server configuration .. .. done

if I then go into the install directory and start instiki myself with

./instiki -p8443 NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from ./config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21. => Booting Mongrel => Rails 2.3.14 application starting on http://0.0.0.0:8443 ** Erubis 2.7.0 => Call with -d to detach => Ctrl-C to shutdown server

it works fine. If I add a --prefix flag I get...

./instiki --prefix NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from ./config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21. instiki: invalid option: --prefix => Booting Mongrel => Rails 2.3.14 application starting on http://0.0.0.0:2500 ** Erubis 2.7.0 => Call with -d to detach => Ctrl-C to shutdown server ^CExiting

instiki is a script that just call script/server. I assume the script installer is calling instiki itself and trying to pass a --prefix option. From what I can see --prefix is not a script/server option but a mongrel_rails option so I think there is a problem here with how we are starting instiki. I then tried running

public_html/instiki$ mongrel_rails start -e production -p 8443 -n 2 -c $PWD --prefix /instiki and it complained about activated versions of gems being wrong and suggested I use bundle exec. I tried that but they turned out to not be installed so I ran

bundle install vendor/bundle --binstubs Fetching source index for http://rubygems.org/ Installing rake (0.9.2.2) Installing RedCloth (4.2.8) with native extensions Installing daemons (1.0.10) Installing erubis (2.7.0) Installing gem_plugin (0.2.3) Installing itextomml (1.4.9) with native extensions Installing json (1.6.1) with native extensions Installing mongrel (1.2.0.pre2) with native extensions Installing nokogiri (1.5.0) with native extensions Installing rack (1.3.5) Installing rdoc (3.11) Installing rubyzip (0.9.4) Installing sqlite3 (1.3.4) with native extensions Installing sqlite3-ruby (1.3.3) Using bundler (1.0.21) Your bundle is complete! It was installed into ./vendor/bundle The path argument to bundle install is deprecated. It will be removed in version 1.1. Please use bundle install --path vendor/bundle instead.

following that I could start it successfully by doing the following... public_html/instiki$ bin/mongrel_rails start -e production -p 8443 --prefix /instiki NOTE: Gem::SourceIndex.from_installed_gems is deprecated with no replacement. It will be removed on or after 2011-10-01. Gem::SourceIndex.from_installed_gems called from /REDACTED/public_html/instiki/vendor/bundle/ruby/1.8/gems/gem_plugin-0.2.3/lib/gem_plugin.rb:109. NOTE: from_installed_gems(arg) is deprecated. From /usr/local/lib/site_ruby/1.8/rubygems/deprecate.rb:62:in send' NOTE: Gem::SourceIndex.from_gems_in is deprecated with no replacement. It will be removed on or after 2011-10-01. Gem::SourceIndex.from_gems_in called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:50. NOTE: Gem::SourceIndex#each is deprecated with no replacement. It will be removed on or after 2011-11-01. Gem::SourceIndex#each called from /REDACTED/public_html/instiki/vendor/bundle/ruby/1.8/gems/gem_plugin-0.2.3/lib/gem_plugin.rb:112. ** Starting Mongrel listening at 0.0.0.0:8443 ** Starting Rails with production environment... ** Mounting Rails at /instiki... NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /REDACTED/public_html/instiki/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21. ** Erubis 2.7.0 ** Rails loaded. ** Loading any Rails specific GemPlugins NOTE: Gem::SourceIndex.from_installed_gems is deprecated with no replacement. It will be removed on or after 2011-10-01. Gem::SourceIndex.from_installed_gems called from /REDACTED/public_html/instiki/vendor/bundle/ruby/1.8/gems/gem_plugin-0.2.3/lib/gem_plugin.rb:109. NOTE: from_installed_gems(arg) is deprecated. From /usr/local/lib/site_ruby/1.8/rubygems/deprecate.rb:62:insend' NOTE: Gem::SourceIndex.from_gems_in is deprecated with no replacement. It will be removed on or after 2011-10-01. Gem::SourceIndex.from_gems_in called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:50. NOTE: Gem::SourceIndex#each is deprecated with no replacement. It will be removed on or after 2011-11-01. Gem::SourceIndex#each called from /REDACTED/public_html/instiki/vendor/bundle/ruby/1.8/gems/gem_plugin-0.2.3/lib/gem_plugin.rb:112. ** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart). ** Rails signals registered. HUP => reload (without restart). It might not work well. ** Mongrel 1.2.0.pre2 available at 0.0.0.0:8443 ** Use CTRL-C to stop.

Please fix this so I don't have to do all this manually. One thing you could do immediately that would help would be to leave all the config for the install in place so once I fix it I can still use virtualmin to mange it. The install failed to start mongrel so it removed the balancer members from the apache config and did not register the script in the list of installed scripts so I can't start and stop it once I have fixed it. basically I don't think it makes sense to remove the entire configuration for the script because I can't start it after install. That just makes my life harder.

also please edit your reply to redact everything up to public_html from the path information.