From f6d36d34edee42fcef2bf2e4769d3fe69f23dc27 Mon Sep 17 00:00:00 2001 From: "http://edheil.wordpress.com/" Date: Tue, 16 Jul 2013 19:05:49 +0000 Subject: [PATCH 1/9] --- .../reliability__47__completeness_of_XMPP_updates.mdwn | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 doc/forum/reliability__47__completeness_of_XMPP_updates.mdwn diff --git a/doc/forum/reliability__47__completeness_of_XMPP_updates.mdwn b/doc/forum/reliability__47__completeness_of_XMPP_updates.mdwn new file mode 100644 index 0000000000..fc558aad60 --- /dev/null +++ b/doc/forum/reliability__47__completeness_of_XMPP_updates.mdwn @@ -0,0 +1,7 @@ +This falls into the category of "noob questions" I think. + +The one piece of the git-annex assistant puzzle I've never messed with is XMPP pairing. I'm wondering how well a pair of repos can keep in sync with each other if their only connection is via XMPP. Will things go badly if changes are made to one while the other is offline? Do messages get queued up to deliver when they're both online? (Or do they get queued on the server side so they can be delivered even if one of them is online, makes changes, then goes offline, and the other one comes online later?) + +If some xmpp messages don't go through for whatever reason, will the remotes be able to "catch up" with each other later on and make up for lost time? + +Just hoping for a general sense of the limitations of XMPP pairing. TIA. From e9d2a34364585fd1ecf3beda79cff6709613f561 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 16 Jul 2013 19:08:49 +0000 Subject: [PATCH 2/9] Added a comment --- ...mment_2_0e99f6ef4f8b342ef0ebc64dbf8e2ce6._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/git_annex_uninit_loses_content_when_interrupted/comment_2_0e99f6ef4f8b342ef0ebc64dbf8e2ce6._comment diff --git a/doc/bugs/git_annex_uninit_loses_content_when_interrupted/comment_2_0e99f6ef4f8b342ef0ebc64dbf8e2ce6._comment b/doc/bugs/git_annex_uninit_loses_content_when_interrupted/comment_2_0e99f6ef4f8b342ef0ebc64dbf8e2ce6._comment new file mode 100644 index 0000000000..2b6fc41860 --- /dev/null +++ b/doc/bugs/git_annex_uninit_loses_content_when_interrupted/comment_2_0e99f6ef4f8b342ef0ebc64dbf8e2ce6._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.90" + subject="comment 2" + date="2013-07-16T19:08:49Z" + content=""" +However, if you then run `git annex uninit` a second time, it goes ahead and deletes the content! That is a bug. + +I looked into trying to make uninit always replace the symlink atomically with the file content. It can't be done when using --fast, since it's not possible to atomically replace a symlink with a hard link (AFAIK). It should be possible to do it in the normal mode, but it would require manually constructing a commit, since git does not provide a way to delete a file from the index and commit that staged change without also committing any other changes that are staged -- and uninit should preseve any changes to non-annexed files that the user has staged. So, I don't think atomic operation is the right answer. + +Instead, I have made uninit refuse to delete .git/annex/objects unless it's empty, and if objects are still left in there, for whatever reason, it'll fail at the end with a nice message explaining some options. I think this is the right fix because it also avoids uninit removing historical versions of files that were stored in git-annex.g +"""]] From f5268d90eb677585e194813062578998d9f07c19 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 16 Jul 2013 19:16:54 +0000 Subject: [PATCH 3/9] Added a comment --- .../comment_1_f5cd9f9deab13ab2d2290ad763906dd3._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/support_for_lossy_remotes/comment_1_f5cd9f9deab13ab2d2290ad763906dd3._comment diff --git a/doc/todo/support_for_lossy_remotes/comment_1_f5cd9f9deab13ab2d2290ad763906dd3._comment b/doc/todo/support_for_lossy_remotes/comment_1_f5cd9f9deab13ab2d2290ad763906dd3._comment new file mode 100644 index 0000000000..1e895944cb --- /dev/null +++ b/doc/todo/support_for_lossy_remotes/comment_1_f5cd9f9deab13ab2d2290ad763906dd3._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.90" + subject="comment 1" + date="2013-07-16T19:16:54Z" + content=""" +There is already one example of a lossy remote: If you use `git annex addurl --relaxed` it generates a key that just uses the url, without its size. When retreiving such a key, any content will be accepted. +"""]] From 401ae5f6c45d42b0a411a5588ed355912ed2b6b7 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 16 Jul 2013 19:27:07 +0000 Subject: [PATCH 4/9] Added a comment --- ...mment_1_e0f7aa48d54fc0564f41c3a569c723b7._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/reliability__47__completeness_of_XMPP_updates/comment_1_e0f7aa48d54fc0564f41c3a569c723b7._comment diff --git a/doc/forum/reliability__47__completeness_of_XMPP_updates/comment_1_e0f7aa48d54fc0564f41c3a569c723b7._comment b/doc/forum/reliability__47__completeness_of_XMPP_updates/comment_1_e0f7aa48d54fc0564f41c3a569c723b7._comment new file mode 100644 index 0000000000..d72cad5b97 --- /dev/null +++ b/doc/forum/reliability__47__completeness_of_XMPP_updates/comment_1_e0f7aa48d54fc0564f41c3a569c723b7._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.90" + subject="comment 1" + date="2013-07-16T19:27:07Z" + content=""" +Both clients have to be online at the same time for XMPP push to work. Once they're able to see each other, they'll sync up, even if they've diverged since the last sync. + +If you tend to only have one client or the other online, you should set up a git repo on a ssh server. Then clients will drop off their changes there, and the other one will check it when it comes online. (You don't really need to use XMPP at all in this case.) + +The most robust and fast combo is to use XMPP pairing, and also have a git repo on a ssh server. This way, when both clients are online, they'll use XMPP to instantly propagate changes, and when not the server is there to fall back to. +"""]] From 8bd48c5c5c91764840b342842fefecf17d64c2b6 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 16 Jul 2013 19:30:55 +0000 Subject: [PATCH 5/9] Added a comment --- .../comment_1_fb8a379ed7f4b88bd55245ce5b18042c._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/Failed_to_make_repository___40__calling_nonexistant_shell__41__/comment_1_fb8a379ed7f4b88bd55245ce5b18042c._comment diff --git a/doc/bugs/Failed_to_make_repository___40__calling_nonexistant_shell__41__/comment_1_fb8a379ed7f4b88bd55245ce5b18042c._comment b/doc/bugs/Failed_to_make_repository___40__calling_nonexistant_shell__41__/comment_1_fb8a379ed7f4b88bd55245ce5b18042c._comment new file mode 100644 index 0000000000..3a225a074c --- /dev/null +++ b/doc/bugs/Failed_to_make_repository___40__calling_nonexistant_shell__41__/comment_1_fb8a379ed7f4b88bd55245ce5b18042c._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.90" + subject="comment 1" + date="2013-07-16T19:30:55Z" + content=""" +That's not really how you're meant to use the standalone tarball. Just untar it somewhere, and add that directory to PATH (eg, in `~/.bash_profile`). +"""]] From 23057ebfae294e9bfdefdb816446ac66c507a34c Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 16 Jul 2013 19:40:20 +0000 Subject: [PATCH 6/9] Added a comment --- ...comment_1_7b9b4ef614c90e0b222d24678d1b9026._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/Encrypted_ssh_remote__44___synced_folders/comment_1_7b9b4ef614c90e0b222d24678d1b9026._comment diff --git a/doc/forum/Encrypted_ssh_remote__44___synced_folders/comment_1_7b9b4ef614c90e0b222d24678d1b9026._comment b/doc/forum/Encrypted_ssh_remote__44___synced_folders/comment_1_7b9b4ef614c90e0b222d24678d1b9026._comment new file mode 100644 index 0000000000..9ebee5f702 --- /dev/null +++ b/doc/forum/Encrypted_ssh_remote__44___synced_folders/comment_1_7b9b4ef614c90e0b222d24678d1b9026._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.90" + subject="comment 1" + date="2013-07-16T19:40:20Z" + content=""" +Yes, you need to add the rsync remote to the second computer. Once it's set up, they will be able to exchange file contents using it, and using XMPP as a control channel. + +If the first computer already has that rsync remote configured, it should push some notes about the existance of that remote to the second one, over XMPP. Then in the webapp, you should just need to click on \"enable\" next to the rsync remote, and it'll prompt for the necessary info to set it up. +"""]] From bccbcc1e04b2f43075d01799d6afd217f0a94f66 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 16 Jul 2013 19:45:42 +0000 Subject: [PATCH 7/9] Added a comment --- .../comment_1_4341898d5ae4f09a5b06d24f5fe6192d._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Why_can__39__t_encryption_be_enabled_for_removable_drives__63__/comment_1_4341898d5ae4f09a5b06d24f5fe6192d._comment diff --git a/doc/forum/Why_can__39__t_encryption_be_enabled_for_removable_drives__63__/comment_1_4341898d5ae4f09a5b06d24f5fe6192d._comment b/doc/forum/Why_can__39__t_encryption_be_enabled_for_removable_drives__63__/comment_1_4341898d5ae4f09a5b06d24f5fe6192d._comment new file mode 100644 index 0000000000..0ddf26666b --- /dev/null +++ b/doc/forum/Why_can__39__t_encryption_be_enabled_for_removable_drives__63__/comment_1_4341898d5ae4f09a5b06d24f5fe6192d._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.90" + subject="comment 1" + date="2013-07-16T19:45:42Z" + content=""" +git-annex stores a clone of the git repository on the removable drive. To encrypt a git remote, you can use the [git-remote-gcrypt](https://github.com/blake2-ppc/git-remote-gcrypt) tool. This will work with git-annex, but it needs integration into the webapp to support setting it up, and further integration so git-annex can detect when a git remote is encrypted and also encrypt the contents of file is stores there. +"""]] From 30319cb6dde94b939e8a1ef0a2e1fef9fb0825ba Mon Sep 17 00:00:00 2001 From: "http://siancu.myopenid.com/" Date: Tue, 16 Jul 2013 19:52:28 +0000 Subject: [PATCH 8/9] Added a comment --- .../comment_5_13b6e595d595da7f036e81258a65541e._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_5_13b6e595d595da7f036e81258a65541e._comment diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_5_13b6e595d595da7f036e81258a65541e._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_5_13b6e595d595da7f036e81258a65541e._comment new file mode 100644 index 0000000000..33c1319b33 --- /dev/null +++ b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_5_13b6e595d595da7f036e81258a65541e._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://siancu.myopenid.com/" + nickname="siancu" + subject="comment 5" + date="2013-07-16T19:52:28Z" + content=""" +Ok, I will try without XMPP. However I'm going to need it, because, if I understood correctly, it is needed to do remote pairings. But for now I can manage without as I can take the laptop with me to work and to syncing locally. +"""]] From cdd5be64e61b3ecc501caff9f2e1380e88359cb9 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawkF8_uQjLYm5Mf5F_JuVW-BxlvzpWjvR_o" Date: Tue, 16 Jul 2013 22:22:26 +0000 Subject: [PATCH 9/9] Added a comment: git annex fsck --- ...comment_2_06574e05149a677d666a722061586658._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/TransferScanner_crash_on_Android/comment_2_06574e05149a677d666a722061586658._comment diff --git a/doc/bugs/TransferScanner_crash_on_Android/comment_2_06574e05149a677d666a722061586658._comment b/doc/bugs/TransferScanner_crash_on_Android/comment_2_06574e05149a677d666a722061586658._comment new file mode 100644 index 0000000000..12105342c5 --- /dev/null +++ b/doc/bugs/TransferScanner_crash_on_Android/comment_2_06574e05149a677d666a722061586658._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkF8_uQjLYm5Mf5F_JuVW-BxlvzpWjvR_o" + nickname="Andrew" + subject="git annex fsck" + date="2013-07-16T22:22:25Z" + content=""" +Running git annex fsck appears to have resolved the corruption, but it removed all the content and the assistant hasn't refetched them. + +I'm running git annex get . now to refetch all the content. +"""]]