Hello,
I use the assistant to set up two repositories A and B synced using jabber. A third repository C on my server is used as rsync transfer. Syncing works fine between both repos when both are online.
But when either A or B is offline the sync does not happen when it comes online again, though the file was synced to C.
Is this because C is only a rsync repository and can't hold metadata? How can I achieve that the sync happens also when one of the repositories is offline?
I also tried using the static build of git annex on my server. It seemed to run fine but during the setup the assistant got an error about too many command line arguments. On A und B I use the ArchLinux AUR build (https://aur.archlinux.org/packages/git-annex-standalone/), on C I use the static build. Could it be a version mismatch?
Thanks!
Another try on the layout:
Hello,
I use the assistant to set up two repositories A and B synced using jabber. A third repository C on my server is used as rsync transfer. Syncing works fine between both repos when both are online.
But when either A or B is offline the sync does not happen when it comes online again, though the file was synced to C.
Is this because C is only a rsync repository and can't hold metadata? How can I achieve that the sync happens also when one of the repositories is offline?
I also tried using the static build of git annex on my server. It seemed to run fine but during the setup the assistant got an error about too many command line arguments. On A und B I use the ArchLinux AUR build (https://aur.archlinux.org/packages/git-annex-standalone/), on C I use the static build. Could it be a version mismatch?
Thanks!
Yes, the rsync repository is not a git repository and so does not hold metadata. If you can install git-annex on your server, you can add a regular git repository there, and then the clients can sync to it even when the other is offline.
This is also why I an working on adding support for gcrypt repositories, so you can have a fully encrypted git repository on the server and sync through that.
I have never heard about such a problem. You should file a bug report with the details.
Thanks for your reply. The bug report is at http://git-annex.branchable.com/bugs/git-annex:_Argument_list_too_long/
I'll be happy to provide any more help if I can!