Recent comments posted to this site:

comment 23 70dcb7e7ffdd14351adaf4c40ee7fdd0
[[!comment Error: unsupported page format hs]]
Fri Sep 30 18:31:54 2016

git-annex will probe to detect if the filesystem does not support FIFOs and disables annex.sshcaching in that case. It's done so since 2013. So I would be surprised if NFS had any problems with annex.sshcaching.

git config annex.pidlock true will make git-annex avoid FCNTL locking, and so work on filesystems that don't support that. It should also avoid the ".nfs" files.

It's not enabled by default on NFS because I don't currently have a good way to probe if a given directory is on NFS.

Also, annex.pidlock makes git-annex significantly slower and less safe. But if you're using NFS, speed and safety must have already been de-prioritized.

Seriously, my main advice for using git-annex on NFS is: Don't. Make local clones of repositories and use git-annex to distribute the files around. Unless your institution forces you to use a networked filesystem to access gobs of disk space, and you need to have more files present in a repository than will fit locally.

Comment by joey Wed Sep 21 19:28:36 2016

@kartynnik, that's a bug: sync uses conflicting names for deep branches

Please file bugs there and not as comments here, it's too easy to lose track of a comment deep in a thread.

Comment by joey Wed Sep 21 18:56:22 2016

In the meantime, the stack.yaml has been updated to use lts-7.0, which includes concurrent-output-1.7.7, so that should solve that.

Comment by joey Wed Sep 21 17:21:58 2016
Hi. concurrent-output-1.7.7 is not present in resolver lts-5.18.
Comment by dave Thu Sep 8 17:41:28 2016
https://git.joeyh.name/?p=concurrent-output.git;a=blobdiff;f=System/Console/Concurrent.hs;h=d8cea13a3816eba44f8d70a855db21e2dd58a27d;hp=124476379264a94e44b51eb1407fd7d80d0348e7;hb=HEAD;hpb=021358c5a033335e05ec9cff72107ab401217c30
Comment by dave Wed Sep 7 20:27:48 2016

I cloned the git-annex repo from github.com and checked out the 6.20160907 tag.

Then I invoked stack install and that ended with the following. Note, this is on Windows.

Configuring concurrent-output-1.7.6...
Building concurrent-output-1.7.6...
Preprocessing library concurrent-output-1.7.6...
[1 of 7] Compiling Utility.Data     ( Utility\Data.hs, .stack-work\dist\2672c1f3\build\Utility\Data.o )
[2 of 7] Compiling Utility.Exception ( Utility\Exception.hs, .stack-work\dist\2672c1f3\build\Utility\Exception.o )
[3 of 7] Compiling Utility.Monad    ( Utility\Monad.hs, .stack-work\dist\2672c1f3\build\Utility\Monad.o )
[4 of 7] Compiling System.Console.Concurrent.Internal ( System\Console\Concurrent\Internal.hs, .stack-work\dist\2672c1f3\build\System\Console\Concurrent\Internal.o )
[5 of 7] Compiling System.Console.Concurrent ( System\Console\Concurrent.hs, .stack-work\dist\2672c1f3\build\System\Console\Concurrent.o )
[6 of 7] Compiling System.Console.Regions ( System\Console\Regions.hs, .stack-work\dist\2672c1f3\build\System\Console\Regions.o )

System\Console\Regions.hs:559:46: Warning:
    Defined but not used: `oldt'

System\Console\Regions.hs:719:1: Warning:
    Defined but not used: `calcLineUpdate'

System\Console\Regions.hs:746:1: Warning:
    Defined but not used: `advanceLine'

System\Console\Regions.hs:773:1: Warning:
    Defined but not used: `isSGR'

System\Console\Regions.hs:777:1: Warning:
    Defined but not used: `genLineUpdate'

System\Console\Regions.hs:791:1: Warning:
    Defined but not used: `optimiseLineUpdate'

System\Console\Regions.hs:807:1: Warning:
    Defined but not used: `combineSGR'

System\Console\Regions.hs:817:1: Warning:
    Defined but not used: `combineSGRCodes'
[7 of 7] Compiling System.Process.Concurrent ( System\Process\Concurrent.hs, .stack-work\dist\2672c1f3\build\System\Process\Concurrent.o )

System\Process\Concurrent.hs:24:49:
    Not in scope: `createProcessConcurrent'
Comment by dave Wed Sep 7 18:25:19 2016

Hi Joey,

Since this issue is > year old, and some fixes/workarounds were done to how locking mechanisms, could you please update on the status of "NFS support". Thank you in advance

Comment by https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4 Tue Sep 6 14:11:24 2016

@junk, this page is not really the place to ask such an unrelated question. Please use the forum for such questions.

(Anyway, git-annex uses gpg to encrypt data, so you can perhaps use gpg to check the embedded checksum, but I have never done it, and git-annex certianly doesn't support doing it.)

Comment by joey Mon Sep 5 19:47:48 2016

@Dosenpfand at a guess, perhaps you have missed enabling "Interoperable Access" in google cloud storage?

Or, maybe Google managed to break their S3 compatability..

gcsannex is probably a better way to tie git-annex and GCS together than using the S3 interface.

Comment by joey Mon Sep 5 18:24:37 2016