Package: git-annex Version: 4.20130405 Severity: wishlist ATM if I add a "remote server using ssh" in webapp it generates a bare repository on the remote end. I have tried both 'client' , 'full backup' and few other modes -- all seems to initiate a bare repository.
What I wanted is just to replicate my existing repository to other boxes where I have access to, so they become readily available/synced there as well. I guess currently I would need to go to each remote box, initiate annexed (non-bare) repository there, start assistant, register it with jabber, and only then "Share with your other devices" -- is that right? wouldn't it be sensible/possible to have a mode where such remote configuration steps are carried out from my current git-annex instance, and remote repository is non-bare so could readily be used whenever I login to those boxes? -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages git-annex depends on: ii curl 7.26.0-1+wheezy1 ii git 1:1.8.2~rc3-1 ii libc6 2.13-38 ii libffi5 3.0.10-3 ii libgmp10 2:5.0.5+dfsg-2 ii libgnutls26 2.12.20-4 ii libgsasl7 1.8.0-2 ii libidn11 1.25-2 ii libxml2 2.8.0+dfsg1-7+nmu1 ii libyaml-0-2 0.1.4-2 ii openssh-client 1:6.0p1-4 ii rsync 3.0.9-4 ii uuid 1.6.2-1.3 ii wget 1.13.4-3 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages git-annex recommends: ii bind9-host 1:9.8.4.dfsg.P1-6 ii gnupg 1.4.12-7 ii lsof 4.86+dfsg-1 Versions of packages git-annex suggests: ii bup 0.25~git20130303-1 ii graphviz 2.26.3-14 ii libnss-mdns 0.10-3.2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
