summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/bugs/get_failed__44___but_remote_has_the_file/comment_3_845e8a23d63fb0b071c63ee736697d26._comment20
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/bugs/get_failed__44___but_remote_has_the_file/comment_3_845e8a23d63fb0b071c63ee736697d26._comment b/doc/bugs/get_failed__44___but_remote_has_the_file/comment_3_845e8a23d63fb0b071c63ee736697d26._comment
new file mode 100644
index 000000000..0ddbe14bf
--- /dev/null
+++ b/doc/bugs/get_failed__44___but_remote_has_the_file/comment_3_845e8a23d63fb0b071c63ee736697d26._comment
@@ -0,0 +1,20 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawnBJ6Dv1glxzzi4qIzGFNa6F-mfHIvv9Ck"
+ nickname="Jim"
+ subject="comment 3"
+ date="2013-01-19T22:21:04Z"
+ content="""
+Wait, that's weird, it works today. I'm thinking that maybe there was another copy of `git-annex` backgrounded and holding a lock, since that reproduces this behavior:
+
+ pilot:~/vid/tv/Show$ git annex get --from bucket Show\ -\ S03E08.mp4
+ get Show - S03E08.mp4 (from bucket...)
+ Enter passphrase for key '/home/jim/.ssh/id_rsa':
+ SHA256E-s358393024--efda17d23d68b85d47ad342f8e41f79ac04d4a65d7ef654b4838b995b86bdefe.mp4
+ 96043008 26% 10.27MB/s 0:00:24 ^Z
+ [1]+ Stopped git annex get --from bucket Show\ -\ S03E08.mp4
+ pilot:~/vid/tv/Show$ git annex get --from bucket Show\ -\ S03E08.mp4
+ get Show - S03E08.mp4 failed
+ git-annex: get: 1 failed
+
+So, I guess this is probably \"not a bug\", but having a more specific error would be really helpful.
+"""]]