Unfortunately not :( root@chimera-server:/var/www/gitorious# rm /usr/lib/ruby/gems/1.8/ cache/* root@chimera-server:/var/www/gitorious# bundle --without development test Fetching source index for http://rubygems.org/ Using rake (0.8.7) Using activesupport (2.3.8) Using activerecord (2.3.8) /usr/local/lib/site_ruby/1.8/rubygems/package/tar_input.rb:218:in `finish': invalid distance code (Zlib::DataError) from /usr/local/lib/site_ruby/1.8/rubygems/package/ tar_input.rb:218:in `zipped_stream' from /usr/local/lib/site_ruby/1.8/rubygems/package/ tar_input.rb:125:in `each' from /usr/local/lib/site_ruby/1.8/rubygems/package/ tar_reader.rb:64:in `each' from /usr/local/lib/site_ruby/1.8/rubygems/package/ tar_reader.rb:55:in `loop' from /usr/local/lib/site_ruby/1.8/rubygems/package/ tar_reader.rb:55:in `each' from /usr/local/lib/site_ruby/1.8/rubygems/package/ tar_input.rb:123:in `each' from /usr/local/lib/site_ruby/1.8/rubygems/format.rb:63:in `from_io' from /usr/local/lib/site_ruby/1.8/rubygems/package/ tar_input.rb:22:in `open' from /usr/local/lib/site_ruby/1.8/rubygems/package.rb:53:in `open' from /usr/local/lib/site_ruby/1.8/rubygems/format.rb:59:in `from_io' from /usr/local/lib/site_ruby/1.8/rubygems/format.rb:47:in `from_file_by_path' from /usr/lib/ruby/1.8/open-uri.rb:32:in `open_uri_original_open' from /usr/lib/ruby/1.8/open-uri.rb:32:in `open' from /usr/local/lib/site_ruby/1.8/rubygems/format.rb:46:in `from_file_by_path' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ rubygems_integration.rb:97:in `spec_from_gem' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ source.rb:77:in `fetch' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ installer.rb:50:in `run' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ spec_set.rb:12:in `each' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ spec_set.rb:12:in `each' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ installer.rb:49:in `run' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ installer.rb:8:in `install' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ cli.rb:222:in `install' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ vendor/thor/task.rb:22:in `send' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ vendor/thor/task.rb:22:in `run' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ vendor/thor/invocation.rb:118:in `invoke_task' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ vendor/thor.rb:246:in `dispatch' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ vendor/thor/base.rb:389:in `start' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/bin/bundle:13 from /usr/bin/bundle:19:in `load' from /usr/bin/bundle:19
On May 12, 3:54 pm, Rodrigo Rosenfeld Rosas <[email protected]> wrote: > Try removing your gems cache with "rm /usr/lib/ruby/gems/1.8/cache/*": > > https://github.com/carlhuda/bundler/issues/355 > > Did it work? > > Em 12-05-2011 10:40, rendered escreveu: > > > > > > > > > I ran it again: chef-solo and it produced the same. > > > I ran it manually: > > > root@localhost:/var/www/gitorious# bundle --without development test > > Fetching source index forhttp://rubygems.org/ > > Using rake (0.8.7) > > Using activesupport (2.3.8) > > Using activerecord (2.3.8) > > /usr/local/lib/site_ruby/1.8/rubygems/package/tar_input.rb:218:in > > `finish': invalid distance code (Zlib::DataError) > > from /usr/local/lib/site_ruby/1.8/rubygems/package/ > > tar_input.rb:218:in `zipped_stream' > > from /usr/local/lib/site_ruby/1.8/rubygems/package/ > > tar_input.rb:125:in `each' > > from /usr/local/lib/site_ruby/1.8/rubygems/package/ > > tar_reader.rb:64:in `each' > > from /usr/local/lib/site_ruby/1.8/rubygems/package/ > > tar_reader.rb:55:in `loop' > > from /usr/local/lib/site_ruby/1.8/rubygems/package/ > > tar_reader.rb:55:in `each' > > from /usr/local/lib/site_ruby/1.8/rubygems/package/ > > tar_input.rb:123:in `each' > > from /usr/local/lib/site_ruby/1.8/rubygems/format.rb:63:in > > `from_io' > > from /usr/local/lib/site_ruby/1.8/rubygems/package/ > > tar_input.rb:22:in `open' > > from /usr/local/lib/site_ruby/1.8/rubygems/package.rb:53:in > > `open' > > from /usr/local/lib/site_ruby/1.8/rubygems/format.rb:59:in > > `from_io' > > from /usr/local/lib/site_ruby/1.8/rubygems/format.rb:47:in > > `from_file_by_path' > > from /usr/lib/ruby/1.8/open-uri.rb:32:in > > `open_uri_original_open' > > from /usr/lib/ruby/1.8/open-uri.rb:32:in `open' > > from /usr/local/lib/site_ruby/1.8/rubygems/format.rb:46:in > > `from_file_by_path' > > from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ > > rubygems_integration.rb:97:in `spec_from_gem' > > from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ > > source.rb:77:in `fetch' > > from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ > > installer.rb:50:in `run' > > from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ > > spec_set.rb:12:in `each' > > from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ > > spec_set.rb:12:in `each' > > from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ > > installer.rb:49:in `run' > > from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ > > installer.rb:8:in `install' > > from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ > > cli.rb:222:in `install' > > from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ > > vendor/thor/task.rb:22:in `send' > > from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ > > vendor/thor/task.rb:22:in `run' > > from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ > > vendor/thor/invocation.rb:118:in `invoke_task' > > from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ > > vendor/thor.rb:246:in `dispatch' > > from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/ > > vendor/thor/base.rb:389:in `start' > > from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/bin/bundle:13 > > from /usr/bin/bundle:19:in `load' > > from /usr/bin/bundle:19 > > > This seems to be the same error as I got doing everything manually. > > > On May 12, 1:48 pm, Rodrigo Rosenfeld Rosas<[email protected]> > > wrote: > >> Don't worry about wasting my time. If I feel like so, I'll let you know... > > >> This says that while trying to run "bundle --without development test", > >> it returned an error. > > >> Maybe this is a problem with your network that happens sometimes. This > >> explains why I had an error cloning my repository as well as why bundle > >> could fail while trying to fetch the dependencies... > > >> You may try to run "chef-solo" again if that is the case. Otherwise, you > >> can try to run the above command manually under the /var/www/gitorious > >> directory. Then you will have better hints why Bundler is failing to > >> install the dependencies. > > >> Hope it helps, > > >> Rodrigo. > > >> Em 12-05-2011 08:34, rendered escreveu: > > >>> Ok, re-ran it and the only errors are: > >>> Installing activerecord (2.3.8) > >>> [Thu, 12 May 2011 13:17:10 +0200] ERROR: execute[bundle --without > >>> development test] (gitorious::default line 88) has had an error > >>> [Thu, 12 May 2011 13:17:10 +0200] ERROR: Running exception handlers > >>> [Thu, 12 May 2011 13:17:10 +0200] ERROR: Exception handlers complete > >>> [Thu, 12 May 2011 13:17:10 +0200] FATAL: Stacktrace dumped to /root/ > >>> chef-solo/chef-stacktrace.out > >>> [Thu, 12 May 2011 13:17:10 +0200] FATAL: > >>> Chef::Exceptions::ShellCommandFailed: execute[bundle --without > >>> development test] (gitorious::default line 88) had an error: Expected > >>> process to exit 0, but it exited with 1 > >>> ---- Begin output of bundle --without development test ---- > >>> Thanks again for all your trouble - I really don't want to waste your > >>> time. > >>> On May 12, 11:58 am, Rodrigo Rosenfeld Rosas<[email protected]> > >>> wrote: > >>>> Em 12-05-2011 04:27, rendered escreveu: > >>>>> Hi, > >>>>> Thanks. Ok so I followed the instructions at: > >>>>>https://github.com/rosenfeld/gitorious-cookbooks. These were the only > >>>>> errors I found: > >>>>> ... > >>>>> [Wed, 11 May 2011 20:58:18 +0200] INFO: git[/var/www/gitorious] > >>>>> cloning repo > >>>>> git://gitorious.org/~rosenfeld/gitorious/rosenfeld-gitorious.git > >>>>> to /var/www/gitorious > >>>>> [Wed, 11 May 2011 20:58:18 +0200] INFO: git[/var/www/gitorious] sh(git > >>>>> clone git://gitorious.org/~rosenfeld/gitorious/rosenfeld-gitorious.git > >>>>> /var/www/gitorious) > >>>>> Initialized empty Git repository in /var/www/gitorious/.git/ > >>>>> [Wed, 11 May 2011 21:09:40 +0200] ERROR: git[/var/www/gitorious] > >>>>> (gitorious::default line 58) has had an error > >>>>> [Wed, 11 May 2011 21:09:40 +0200] ERROR: Running exception handlers > >>>>> [Wed, 11 May 2011 21:09:40 +0200] ERROR: Exception handlers complete > >>>>> [Wed, 11 May 2011 21:09:40 +0200] FATAL: Stacktrace dumped to /root/ > >>>>> chef-solo/chef-stacktrace.out > >>>>> [Wed, 11 May 2011 21:09:40 +0200] FATAL: > >>>>> Chef::Exceptions::CommandTimeout: git[/var/www/gitorious] > >>>>> (gitorious::default line 58) had an error: command timed out: > >>>> This tells us that there was a timeout while git cloning my repository. > >>>> You can also remove the url and branch options of your node.js for using > >>>> master from mainline gitorious instead of my repository. My repository > >>>> includes an extra feature, which can be seen in the image here: > >>>>http://rosenfeld.heroku.com/en/articles/2011-03-06-installing-gitorio... > >>>> If you don't want it, just remove these lines from node.js: > >>>> "git": { > >>>> "url": > >>>> "git://gitorious.org/~rosenfeld/gitorious/rosenfeld-gitorious.git", > >>>> "reference": "bundler" > >>>> }, > >>>> Anyway, that wasn't the problem when you ran Chef. Just run it again > >>>> when these timeout errors occur. Gitorious is notoriously slow sometimes > >>>> and I'm not sure if it is due its architecture or lack of bandwidth > >>>> infrastructure, but my clones on Github are much faster than on > >>>> Gitorious... I also feel it is a bit slow in our internal installation, > >>>> so maybe there's something we could improve on its performance... > >>>> I guess just running "chef-solo" again will fix it for you. Chef knows > >>>> what is missing and won't do everything again, don't worry. > >>>> Best regards, Rodrigo. > >>>>> ---- Begin output of git clone > >>>>> git://gitorious.org/~rosenfeld/gitorious/rosenfeld-gitorious.git > >>>>> /var/www/gitorious ---- > >>>>> STDOUT: Initialized empty Git repository in /var/www/gitorious/.git/ > >>>>> STDERR: > >>>>> ---- End output of git clone > >>>>> git://gitorious.org/~rosenfeld/gitorious/rosenfeld-gitorious.git > >>>>> /var/www/gitorious ---- > >>>>> Do you need me to do anything else? > >>>>> On May 11, 2:06 pm, Rodrigo Rosenfeld Rosas<[email protected]> > >>>>> wrote: > >>>>>> I tested against an empty installation of Debian in a virtual machine. > >>>>>> I think you should remove the rubygems package distributed with Ubuntu: > >>>>>> "apt-get remove rubygems*" > >>>>>> Then you can try run the instructions there. If you have any problem, > >>>>>> post it here and I'll try to help you. > >>>>>> Regards, Rodrigo. > >>>>>> Em 11-05-2011 08:57, Garth escreveu: > >>>>>>> Must I remove everything from the previous install of gitorious -- > >>>>>>> what would you recommend? > >>>>>>> *From:*[email protected] [mailto:[email protected]] > >>>>>>> *On Behalf Of *Rodrigo Rosenfeld Rosas > >>>>>>> *Sent:* 11 May 2011 13:33 > >>>>>>> *To:* [email protected] > >>>>>>> *Subject:* Re: [gitorious] Re: Ubuntu Server 10.10 Error > >>>>>>> Em 11-05-2011 08:23, Garth escreveu: > >>>>>>> I think I give up or I must start all over again -- I have been using > >>>>>>> this tutorial: > >>>>>>>http://www.silly-science.co.uk/2010/12/12/installing-gitorious-on-ubu.... > >>>>>>> Maybe I'm not following the instructions correctly. I still get the > >>>>>>> same error. > >>>>>>> Please, give a try on this automated install recipe of Gitorious using > >>>>>>> Opscode Chef: > >>>>>>>https://github.com/rosenfeld/gitorious-cookbooks > >>>>>>> I tested it on Debian, but I think it also works on Ubuntu... -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected]
