assistant does not interoperate with gitolite when adding a repository

The assistant does not allow adding an existing repo: I tried to add a "remote server", to enter the credits, and then I add to choose between "git-annex" or "rsync". Choosing "git-annex" tries to create a new repo and then fails. The repo on the server is a bare one, accessed via gitolite. Setting the remote manually ("git remote add origin git@example.org:my-annex.git" works (I can pull, push, ...))

Mac OS 10.7 version 2013-09-10

[2013-09-13 17:00:55 CEST] chat: ssh ["-p","22","git@example.org","sh -c 'mkdir -p '\"'\"'my-annex.git'\"'\"'&&cd '\"'\"'my-annex.git'\"'\"'&&if [ ! -d .git ]; then git init --bare --shared; fi&&git annex init'"]

RSS Atom

comment 1

I suppose the assistant could try to add a git remote and pull from it, and only if this pull fails go try to run shell commands to create it. This might work with gitolite, gitosis, github, etc. Although only partially for ones that don't support running git-annex-shell..

Comment by joeyh.name — Fri Sep 13 18:19:03 2013

Remove comment

Strategy for getting up and running

The following is the set of steps I use when setting assistant up on a new repository:

git clone user@host:repo.git
pushd repo
git annex init
    touch EMPTY
    git annex add EMPTY
    git commit -m 'Initial commit'
    git push --all
    git annex copy --to origin
    git annex direct
    git annex sync
    git annex untrust .
popd

Entering the folder path now lets the assistant take over.

For an existing repository:

git clone user@host:repo.git
pushd repo
    git annex get .
    git annex direct
    git annex sync
    git annex untrust .
popd

Not sure if this would be helpful for working out what the assistant behavior should be, but maybe it'll help others get to the point where the assistant works with a gitolite managed repo.

Comment by effigies — Mon Mar 9 17:32:19 2015

Remove comment

Add a comment