From b51885eb5bf6b763b580038b9f4d949082717f91 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawkC_3Vry8U5x3FAvd5Jmazzl7FYvFAtDCU" Date: Mon, 22 Jul 2013 21:33:28 +0000 Subject: [PATCH 1/2] --- doc/forum/non-bare_repo_on_cloud_remote.mdwn | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 doc/forum/non-bare_repo_on_cloud_remote.mdwn diff --git a/doc/forum/non-bare_repo_on_cloud_remote.mdwn b/doc/forum/non-bare_repo_on_cloud_remote.mdwn new file mode 100644 index 0000000000..3949e18dac --- /dev/null +++ b/doc/forum/non-bare_repo_on_cloud_remote.mdwn @@ -0,0 +1,6 @@ +Hi, + +I wondered if it's possible to have a non-bare repo on a cloud remote. I want to have some sort of Dropbox-like workflow were I simply put stuff into a directory on my drive and it gets synced via SSH to a central VPS so I can also always access it via HTTP, for example. + +Regards, +Lukas From 2f19e0b0991540bf454401619c06e500c06aebc6 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Mon, 22 Jul 2013 21:41:01 +0000 Subject: [PATCH 2/2] Added a comment --- ...ent_1_41ca74a4e4aaf4f6b012a92677037651._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_1_41ca74a4e4aaf4f6b012a92677037651._comment diff --git a/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_1_41ca74a4e4aaf4f6b012a92677037651._comment b/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_1_41ca74a4e4aaf4f6b012a92677037651._comment new file mode 100644 index 0000000000..2dae713b0d --- /dev/null +++ b/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_1_41ca74a4e4aaf4f6b012a92677037651._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.1.10" + subject="comment 1" + date="2013-07-22T21:41:01Z" + content=""" +I have tried but have not had any luck reproducing this when initializing a glacier remote. + +Do you also get this problem if you initialize a special remote of another type, such as the directory special remote, that's encrypted to the same gpg key? + +Can you reproduce the hang using the [[/install/Linux_standalone]] tarball? + +You should be able to tell which file descriptor gpg is blocking on. Just attach strace to the gpg process, and see what file descriptor it says gpg is reading from (or perhaps writing to). Since git-annex feeds it both a passphrase and data to encrypt, knowing the number of the file descriptor will narrow down the bug's cause. +"""]]