I indeed have tried to run the Bundler install from the gitorious root 
directory (in our case, /var/www/gitorious) and that is the error message I 
get back.  I see the .git repo there for gitorious; but perhaps this was ran 
from the original user's directory -- how would I be able to tell?  I can 
run a 'git status' from /var/www/gitorious' and I do get information back. 
Very certain that the installation is there and was operating fine. I can 
tell you when I run the update, it says it updates, but then gives that 
message, are there any flags to give some more info?
 

=====

git:/var/www/gitorious# whoami ; date ; pwd ; gem install bundler && bundle 
install
root
Fri Sep 30 08:46:11 PDT 2011
/var/www/gitorious
Successfully installed bundler-1.0.20
1 gem installed
Installing ri documentation for bundler-1.0.20...
Installing RDoc documentation for bundler-1.0.20...
Could not locate Gemfile

git:/var/www/gitorious# locate Gemfile | grep bundler
/usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/templates/Gemfile
/usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/templates/newgem/Gemfile.tt
=====

I've checked with two other users who use the web interface, they're both 
fine, only my user's dashboard and ~<user> are broken. I'm guessing there 
was something DB related that is causing an issue, but I don't know what and 
I haven't made any changes to the DB as of yet.

As for any other DB changes - I had to rip out a repo which was partially 
initialized once... the activeMQ was wedged, so I removed the table 
associated in the Gitorious DB ... the repo in git never was created. It was 
working fine after that... as far as I recall but then again I don't often 
go through the web UI unless I'm showing code to other departments which is 
what spurred this problem. Not completely sure if this is related or not. 
These issues were before the upgrade (the upgrade was one of my attempts to 
solve this problem).

-- 
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]

Reply via email to