gitlabhq/gitlabhq — Issue #224: Upgrading the VM to use gitolite is painful
Author: wmertens
Created: 2011-12-22 13:23:54+00:00
State: open

This is really a bunch of issues, sorry. Basically we're using the VM image with version 1.2 and we upgraded to 2.0, and then we wanted to upgrade to use gitolite. These are the issues I ran into:

* Gitolite doesn't get installed by the rake install and it's not a package in ubuntu
* I then used the gitlabhq_install.git repository to download the ubuntu_gitolite.sh script. This script has DOS line endings! There's no way that that works. I had to strip the line endings with `tr \\r < ubuntu_gitolite.sh > t.sh` and then run `bash t.sh`
* The install script should change the UMASK for the user instead of forcing the user to hunt for the setting. A simple `sed -i~ 's/0077/0007/'` or similar (I keep mixing up the -i behavior on different sed versions) should do the trick
* The gitolite install complained about the ssh key being in authorized_keys twice (I put it in there so `ssh git@localhost` works) and I had to manually remove the key I added
* Then I ran the `bundle exec rake gitolite_rebuild RAILS_ENV=production` and that kept warning about the project users not having pubkeys installed. Afterwards I looked at the authorized_keys and it did put all the users in there and it does seem to work so perhaps adding the user keys and upgrading the repositories has to be reversed.

Anyway now it works :-)