We have gitolite and it keeps complaining an existing repository doesn't exist.
Even after I edited gitolite.conf and removed that repo from the config.
So I'm wondering why it 'remembers' that repo?
I checked my changes were pushed correctly.
The $gituser/.gitolite/conf/gitolite.conf is equal to my local one.
The message doesn't come from the gitolite.pm script, the exact error message is
remote: fatal: Not a git repository: '/Users/git/repositoires/IJslander.git'
For example when committing the gitolite-admin repo:
$ git commit -a -m "bogus space"
[master 675b4e1] bogus space
1 files changed, 2 insertions(+), 2 deletions(-)
$ git push
Counting objects: 7, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (4/4), 360 bytes, done.
Total 4 (delta 1), reused 0 (delta 0)
remote: fatal: Not a git repository: '/Users/git/repositoires/IJslander.git'
To git@redacted.com:gitolite-admin
935c304..675b4e1 master -> master
And I have greped the whole HDD and nowhere does it mention that repo (but it did mention a new one we tried to make to replace it):
~ git$ grep -ilR "IJslander" . 2> /dev/null
./.bash_history
./.gitolite/conf/gitolite.conf
./.gitolite/conf/gitolite.conf-compiled.pm
./.gitolite/logs/gitolite-2011-07.log
./.gitolite/logs/gitolite-2011-08.log
And this is from the conf:
~ git$ grep -iR "IJslander" .gitolite/conf/gitolite.conf 2> /dev/null
repo ijslander-ios
//the compiled conf file
~ git$ grep -iR "IJslander" .gitolite/conf/gitolite.conf-compiled.pm 2> /dev/null
'ijslander-ios' => {
All repos are under git's ~
I had the same problem.. just backup my repository at server-side, uninstall gitolite completely, ref here and re-install gitolite