Recent comments posted to this site:

comment 23 70dcb7e7ffdd14351adaf4c40ee7fdd0
[[!comment Error: unsupported page format hs]]
Mon Aug 24 21:18:02 2015

I just created the same setup again that I attempted 1-2 years ago, with the latest self-contained git-annex build. Two clients, one SSH server, using gcrypt. Setup worked flawless now (although the process of having to manually export the generated GPG key and import it into all clients is still very awkward); changes made on a client are immediately detected and synced with the server. However, the changes made on client A are never automatically propagated to client B. They are picked up when I restart the annex assistant on client B, but never automatically.

Is this a bug or simply not supported? I read about XMPP being deprecated in favor of notifications via the annex-shell, but I couldn't find a post detailing these changes.

Comment by tanen Sun Aug 23 20:34:20 2015

@darkfeline, setting buprepo= causes git-annex to run bup with -r. You can verify this by using the --debug switch.

IIRC, bup still creates ~/.bup when used this way, but doesn't store the contents of annexed files there. It uses it only to store some small index files, which are also stored in the repo specified with -r. This seems weird, but I don't think this is a bug on bup's part; it seems to intentionally do that, using path names in ~/.bup that are constructed to not conflict when -r is used with different repositories. I suppose bup has a good reason to do this, though I don't know what the reason is.

I can blow ~/.bup away, run "bup init" to make a fresh clean ~/.bup, and then git-annex can still get the content of files from the buprepo= repository. So, it seems that buprepo= is working ok.

Comment by joey Wed Aug 19 18:30:16 2015

@forbesmyester, I think that the "glacier" program you have installed is the one from boto, not the one from glacier-cli. git-annex only supports the glacier-cli one.

Note that, since version 5.20150219, git-annex probes to see if the "glacier" program in PATH is the one from boto, and fails with a nicer error message.

Comment by joey Wed Aug 19 18:27:53 2015
just to clarify: this is not implemented yet, as far as i know.
Comment by https://id.koumbit.net/anarcat Tue Aug 18 19:02:30 2015

Have done a full setup as much as I can, with all the GPG / AWS stuff but it keeps doing non stop...

copy 201/2011/05/20/P1010044.RW2 (checking familypictures-glacier...) [2015-08-18 08:37:05 BST] read: glacier ["--region=us-east-1","archive","checkpresent","familypictures","--quiet","GPGHMACSHA1--[SOME_HASH]"]
(to familypictures-glacier...) 
[2015-08-18 08:37:05 BST] feed: glacier ["--region=us-east-1","archive","upload","--name","GPGHMACSHA1--[SOME_HASH]","familypictures","-"]
[2015-08-18 08:37:05 BST] chat: gpg ["--quiet","--trust-model","always","--batch","--passphrase-fd","40","--symmetric","--force-mdc","--no-textmode"]
0%            0.0 B/s 0s
glacier <command> [args]

    Commands
        vaults    - Operations with vaults
        jobs      - Operations with jobs
        upload    - Upload files to a vault. If the vault doesn't exits, it is
                    created

    Common args:
        --access_key - Your AWS Access Key ID.  If not supplied, boto will
                       use the value of the environment variable
                       AWS_ACCESS_KEY_ID
        --secret_key - Your AWS Secret Access Key.  If not supplied, boto
                       will use the value of the environment variable
                       AWS_SECRET_ACCESS_KEY
        --region     - AWS region to use. Possible values: us-east-1, us-west-1,
                       us-west-2, ap-northeast-1, eu-west-1.
                       Default: us-east-1

    Vaults operations:

        List vaults:
            glacier vaults 

    Jobs operations:

        List jobs:
            glacier jobs <vault name>

    Uploading files:

        glacier upload <vault name> <files>

        Examples : 
            glacier upload pics *.jpg
            glacier upload pics a.jpg b.jpg

gpg: [stdout]: write error: Broken pipe
gpg: DBG: deflate: iobuf_write failed
gpg: build_packet failed: file write error
gpg: [stdout]: write error: Broken pipe
gpg: iobuf_flush failed on close: file write error
gpg: [stdout]: write error: Broken pipe
gpg: iobuf_flush failed on close: file write error
gpg: symmetric encryption of `[stdin]' failed: file write error
git-annex: fd:46: hPutBuf: resource vanished (Broken pipe)
failed
Comment by forbesmyester Tue Aug 18 07:42:38 2015
Joey Hess is using xmonad.
Comment by https://woid.cryptobitch.de/foobar Mon Aug 17 13:42:26 2015

The buprepo parameter doesn't seem to work properly, at least for local repos. For example, I added a bup remote with buprepo=/media/hdd/bup, yet when I try to move files onto it, it still tries to use /home/foo/.bup (the default path). I suppose git-annex should be setting the envvar BUP_DIR before calling bup?

I can do it manually like BUP_DIR=/media/hdd/bup git annex move --to hdd foo, but that almost seems to defeat the purpose...

Comment by darkfeline Mon Aug 17 12:59:25 2015

@sanket you need to get your git repositories on the two systems connected in some way (ie, push one to github, pull in the other one). Once the git repositories are in sync, git annex get can be run in the second repository and will know how to download files that were uploaded to tahoe from the first repository.

Nothing tahoe specific here, that's how any git-annex special remote works..

Comment by joey Fri Aug 14 18:03:52 2015
I am trying to integrate Git annex and Tahoe filesystem with each other using special remote. We have 2 systems connected to same Tahoe grid and we managed to upload the file on Tahoe from 1 file system using Git annex and special remote. Now I need to download same file from other system. But for downloading the file from other system we will need the key which was generated when we uploaded the file from first system which was handled by Git annex on first system. We tried to sync only git annex repositories but we did not get the key.( We can not use Sync content because that will kill the purpose of using Tahoe, we need to somehow transfer only keys between 2 git annex systems). Is there any way using which we can share the keys of files uploaded on Tahoe between 2 systems using Git annex or is there any way to share the file between 2 systems on Tahoe grids using git annex and special remote?
Comment by sanket Wed Aug 12 00:00:09 2015