From 229dcb01be60aa0ad5a39f83a91813580db74a48 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 11 Jun 2013 14:44:47 +0000 Subject: Added a comment --- .../comment_1_284c806e83a32af81b02aea7c7bc285a._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/Move_ssh_config_to___126____47__ssh__47__git-annex__47__config/comment_1_284c806e83a32af81b02aea7c7bc285a._comment (limited to 'doc/bugs') diff --git a/doc/bugs/Move_ssh_config_to___126____47__ssh__47__git-annex__47__config/comment_1_284c806e83a32af81b02aea7c7bc285a._comment b/doc/bugs/Move_ssh_config_to___126____47__ssh__47__git-annex__47__config/comment_1_284c806e83a32af81b02aea7c7bc285a._comment new file mode 100644 index 000000000..5997664e0 --- /dev/null +++ b/doc/bugs/Move_ssh_config_to___126____47__ssh__47__git-annex__47__config/comment_1_284c806e83a32af81b02aea7c7bc285a._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 1" + date="2013-06-11T14:44:47Z" + content=""" +The only interface git provides to do this is `GIT_SSH`, which would have to be set to a wrapper script that runs ssh with the desirned options. + +And if that were used, `git pull` by itself would not work on the repositories set up by the assistant. I don't consider that very nice. +"""]] -- cgit v1.2.3 From f909b7603af67eafcc634341c3a4c174727ba7ac Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU" Date: Tue, 11 Jun 2013 14:47:40 +0000 Subject: Added a comment --- .../comment_5_998fe58994ecf855310e4b8e6cce9e18._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_5_998fe58994ecf855310e4b8e6cce9e18._comment (limited to 'doc/bugs') diff --git a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_5_998fe58994ecf855310e4b8e6cce9e18._comment b/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_5_998fe58994ecf855310e4b8e6cce9e18._comment new file mode 100644 index 000000000..8d27f6b5e --- /dev/null +++ b/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_5_998fe58994ecf855310e4b8e6cce9e18._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU" + nickname="Matt" + subject="comment 5" + date="2013-06-11T14:47:40Z" + content=""" +hi, yes I am. Is this bad? +"""]] -- cgit v1.2.3 From c54c91847ad12dc3c247eee732c54263d4eae5de Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 11 Jun 2013 14:48:01 +0000 Subject: Added a comment --- .../comment_2_1f55ad6b39906458779b2d604b003ffe._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/Move_ssh_config_to___126____47__ssh__47__git-annex__47__config/comment_2_1f55ad6b39906458779b2d604b003ffe._comment (limited to 'doc/bugs') diff --git a/doc/bugs/Move_ssh_config_to___126____47__ssh__47__git-annex__47__config/comment_2_1f55ad6b39906458779b2d604b003ffe._comment b/doc/bugs/Move_ssh_config_to___126____47__ssh__47__git-annex__47__config/comment_2_1f55ad6b39906458779b2d604b003ffe._comment new file mode 100644 index 000000000..3cf75df08 --- /dev/null +++ b/doc/bugs/Move_ssh_config_to___126____47__ssh__47__git-annex__47__config/comment_2_1f55ad6b39906458779b2d604b003ffe._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 2" + date="2013-06-11T14:48:01Z" + content=""" +Also, if you're going to set up something like local pairing, why would you *not* want to commit that config to git along with your other ssh configs? Config files in $HOME are quite frequently edited by helper programs to configure changes, and I personally commit those changes all the time. + +Perhaps your real problem is that you have one `.ssh/config` that is shared between multiple hosts, and the git-annex settings are specific to a single host. Have you considered using [vcsh](https://github.com/RichiH/vcsh)? +"""]] -- cgit v1.2.3 From c0f2245c3c03a605f7036b5685e094e0a44b1e04 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 11 Jun 2013 14:54:56 +0000 Subject: Added a comment --- .../comment_1_5b50d97e44cbd5b31ff24537ec3f8603._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/bugs/4.20130601_xmpp_sync_error/comment_1_5b50d97e44cbd5b31ff24537ec3f8603._comment (limited to 'doc/bugs') diff --git a/doc/bugs/4.20130601_xmpp_sync_error/comment_1_5b50d97e44cbd5b31ff24537ec3f8603._comment b/doc/bugs/4.20130601_xmpp_sync_error/comment_1_5b50d97e44cbd5b31ff24537ec3f8603._comment new file mode 100644 index 000000000..9c5062780 --- /dev/null +++ b/doc/bugs/4.20130601_xmpp_sync_error/comment_1_5b50d97e44cbd5b31ff24537ec3f8603._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 1" + date="2013-06-11T14:54:56Z" + content=""" +When you add the box.com repo on the desktop, it will show up on Android pretty quickly thanks to XMPP syncing. But this does not cause the repository to be enabled to be used on Android. You need to select it and enable it there. + +I can see this is the case thanks to the log you posted. The Android is constantly complaining: + +> XMPPSendPack: Unable to download files from your other devices. + +This message should also be appearing in an alert message in the sidebar of the webapp. +"""]] -- cgit v1.2.3 From 67b36df327fedf2eeb90d35f13f3c899d77b46b0 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 11 Jun 2013 15:09:44 +0000 Subject: Added a comment --- .../comment_6_4ce243cb0ea8ff810a4949a5320e4afc._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_6_4ce243cb0ea8ff810a4949a5320e4afc._comment (limited to 'doc/bugs') diff --git a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_6_4ce243cb0ea8ff810a4949a5320e4afc._comment b/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_6_4ce243cb0ea8ff810a4949a5320e4afc._comment new file mode 100644 index 000000000..54f533a92 --- /dev/null +++ b/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_6_4ce243cb0ea8ff810a4949a5320e4afc._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 6" + date="2013-06-11T15:09:44Z" + content=""" +No. Direct mode makes this kind of problem less likely to occur. + +Are you only seeing this problem on OSX? + +My guess, which is only a guess at this point is that while direct mode leaves files in-place etc, which should avoid this kind of problem, it does mess with their permissions berifly when ingesting them into the annex. The write bit is breifly turned off, +while it checks that nothing currently has the file open to be written. +"""]] -- cgit v1.2.3