Upgrading Gitorious git error

109 views
Skip to first unread message

Felipe Sere

unread,
Jun 6, 2012, 5:36:27 PM6/6/12
to gito...@googlegroups.com
Hi everyone,

I was trying to upgrade my 2.0.x Gitorious install to 2.1.0 to then continue onwards to 2.2.0 but I got the error below:

s15927153:/var/www/gitorious# bundle install
error: The requested URL returned error: 403
fatal: Could not parse object 'babb5559aae8914556da528147b6649b9c48f48c'.
Git error: command `git reset --hard babb5559aae8914556da528147b6649b9c48f48c` in directory /opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/bundler/gems/rots-babb5559aae8 has failed.
If this error persists you could try removing the cache directory '/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/cache/bundler/git/rots-89de66268344e64f1e3b64de0635f51e857c6bdb'

The following is presented when I try to access the main Gitorious site:

0/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/bundler-1.0.21/lib/bundler/spec_set.rb88in `materialize'
1/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/bundler-1.0.21/lib/bundler/spec_set.rb82in `map!'
2/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/bundler-1.0.21/lib/bundler/spec_set.rb82in `materialize'
3/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/bundler-1.0.21/lib/bundler/definition.rb90in `specs'
4/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/bundler-1.0.21/lib/bundler/definition.rb135in `specs_for'
5/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/bundler-1.0.21/lib/bundler/definition.rb124in `requested_specs'
6/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/bundler-1.0.21/lib/bundler/environment.rb23in `requested_specs'
7/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/bundler-1.0.21/lib/bundler/runtime.rb11in `setup'
8/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/bundler-1.0.21/lib/bundler.rb110in `setup'
9/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/lib/phusion_passenger/utils.rb326in `prepare_app_process'
10/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/lib/phusion_passenger/classic_rails/application_spawner.rb176in `initialize_server'
11/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/lib/phusion_passenger/utils.rb572in `report_app_init_status'
12/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/lib/phusion_passenger/classic_rails/application_spawner.rb174in `initialize_server'
13/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/lib/phusion_passenger/abstract_server.rb204in `start_synchronously'
14/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/lib/phusion_passenger/abstract_server.rb180in `start'
15/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/lib/phusion_passenger/classic_rails/application_spawner.rb149in `start'
16/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/lib/phusion_passenger/spawn_manager.rb219in `spawn_rails_application'
17/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/lib/phusion_passenger/abstract_server_collection.rb132in `lookup_or_add'
18/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/lib/phusion_passenger/spawn_manager.rb214in `spawn_rails_application'
19/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/lib/phusion_passenger/abstract_server_collection.rb82in `synchronize'
20/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/lib/phusion_passenger/abstract_server_collection.rb79in `synchronize'
21/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/lib/phusion_passenger/spawn_manager.rb213in `spawn_rails_application'
22/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/lib/phusion_passenger/spawn_manager.rb132in `spawn_application'
23/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/lib/phusion_passenger/spawn_manager.rb275in `handle_spawn_application'
24/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/lib/phusion_passenger/abstract_server.rb357in `__send__'
25/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/lib/phusion_passenger/abstract_server.rb357in `server_main_loop'
26/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/lib/phusion_passenger/abstract_server.rb206in `start_synchronously'
27/opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.10/helper-scripts/passenger-spawn-server99



Thanks in advance,

Felipe

sriharsha.hs

unread,
Jun 26, 2012, 3:02:15 AM6/26/12
to gito...@googlegroups.com
I am also facing the same issue any help isĀ appreciated.

Thanks,
Sri Harsha

Thomas Kjeldahl Nilsson

unread,
Jun 26, 2012, 3:59:59 AM6/26/12
to gito...@googlegroups.com
I see that the rots submodule is involved. Have you updated the rots submodule? E.g,

git submodule update --init


regards,
Thomas @ Gitorious
--
To post to this group, send email to gito...@googlegroups.com
To unsubscribe from this group, send email to
gitorious+...@googlegroups.com


-- 
best regards,
Thomas Kjeldahl Nilsson
http://gitorious.com

sriharsha.hs

unread,
Jun 26, 2012, 5:03:54 AM6/26/12
to gito...@googlegroups.com, tho...@gitorious.com
Hi Thomas,

I updated the submodules, but it does not resolve the bundle error. I still see:

-------
fatal: Could not parse object 'babb5559aae8914556da528147b6649b9c48f48c'.
Git error: command `git reset --hard babb5559aae8914556da528147b6649b9c48f48c` in directory /usr/lib/ruby/gems/1.8/bundler/gems/rots-babb5559aae8 has failed.
If this error persists you could try removing the cache directory '/usr/lib/ruby/gems/1.8/cache/bundler/git/rots-89de66268344e64f1e3b64de0635f51e857c6bdb'
--------

Any other ideas?

Thanks,
Sri Harsha

Thomas Kjeldahl Nilsson

unread,
Jun 26, 2012, 5:05:40 AM6/26/12
to sriharsha.hs, gito...@googlegroups.com
Not off the top of my head, sorry. Did you try the suggested cache purge from the error message?
Reply all
Reply to author
Forward
0 new messages