summaryrefslogtreecommitdiff
path: root/doc/bugs/hGetContents:_user_error.mdwn
diff options
context:
space:
mode:
authorGravatar https://m-f-k.myopenid.com/ <https://m-f-k.myopenid.com/@web>2013-06-28 19:56:11 +0000
committerGravatar admin <admin@branchable.com>2013-06-28 19:56:11 +0000
commita4f42b3b6c50ba1bdbbf71f81b8f9fab9372db67 (patch)
tree070ca40d3e1d7b0caca4ef2de87eec167440a3dc /doc/bugs/hGetContents:_user_error.mdwn
parente7517d9abe5aaf5216338ac96b25cbf8b5a6d8e9 (diff)
init bugreport
Diffstat (limited to 'doc/bugs/hGetContents:_user_error.mdwn')
-rw-r--r--doc/bugs/hGetContents:_user_error.mdwn33
1 files changed, 33 insertions, 0 deletions
diff --git a/doc/bugs/hGetContents:_user_error.mdwn b/doc/bugs/hGetContents:_user_error.mdwn
new file mode 100644
index 000000000..8ec84f5ea
--- /dev/null
+++ b/doc/bugs/hGetContents:_user_error.mdwn
@@ -0,0 +1,33 @@
+### Please describe the problem.
+My server is on debian testing. After an upgrade (git annex: 3.20120629 → 4.20130521) I can't do anything in my repository anymore. git itself works, but invoking any git-annex command leads to:
+
+ git-annex: fd:6: hGetContents: user error (Pattern match failure in do expression at libraries/base/GHC/Event/Thread.hs:90:3-10)
+
+This repo is handled by a script, which invokes only the following git/git-annex commands:
+
+ $ git annex sync
+ $ git annex add
+ $ git commit -m "…"
+
+I realized this after trying to move files from my server to my local repo. My local machine runs debian sid. When trying to transfer files, this happens:
+
+ $ git annex sync
+ → ok
+ $ git annex move --from origin .
+ move x.zip (from origin...)
+ user@host's password: ← pw ok
+ git-annex-shell: fd:6: hGetContents: user error (Pattern match failure in do expression at libraries/base/GHC/Event/Thread.hs:90:3-10)
+ rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
+ rsync error: error in rsync protocol data stream (code 12) at io.c(605) [Receiver=3.0.9]
+ failed
+
+I updated git-annex on both machines to 4.20130627 (rest of server is still on debian testing), but it didn't change anything.
+
+The server was not down since the last successful transfer, so I can't imagine anything interrupting any git-annex process.
+
+### What steps will reproduce the problem?
+See above.
+
+### What version of git-annex are you using? On what operating system?
+Server: 4.20130521 on debian testing (now: 4.20130627)
+Local: 4.20130621 on debian sid (now: 4.20130627)