diff options
author | Joey Hess <joey@kitenet.net> | 2014-09-26 15:37:59 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2014-09-26 15:37:59 -0400 |
commit | be93bf66f8e2cc0de226e4e3b75ed83f3ade1a9e (patch) | |
tree | 50c259c05751aac3b64db4daf442e2457af376f2 | |
parent | d3465e2c656049daef795182ac6c42851bc4fd54 (diff) | |
parent | a85ae82f24336bd21810db3d31dc1ecd5c029092 (diff) |
Merge branch 'master' of ssh://git-annex.branchable.com5.20140926
9 files changed, 83 insertions, 0 deletions
diff --git a/doc/bugs/Can__39__t_add_a_git_repo_to_git_annex:___34__Invalid_path_repo__47__.git__47__X__34___for_many_X/comment_10_2c8e8a4f35b392b1cb4dc8104786312d._comment b/doc/bugs/Can__39__t_add_a_git_repo_to_git_annex:___34__Invalid_path_repo__47__.git__47__X__34___for_many_X/comment_10_2c8e8a4f35b392b1cb4dc8104786312d._comment new file mode 100644 index 000000000..b95b3ed68 --- /dev/null +++ b/doc/bugs/Can__39__t_add_a_git_repo_to_git_annex:___34__Invalid_path_repo__47__.git__47__X__34___for_many_X/comment_10_2c8e8a4f35b392b1cb4dc8104786312d._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="JerSou" + ip="82.228.88.32" + subject="comment 10" + date="2014-09-25T19:27:43Z" + content=""" +I thought a workaround (but I don't think ultimately use) : + +> \# for each git repo : + +> mv .git .gitToAnnex + +> ln -s .gitToAnnex .git + +> echo .gitToAnnex >> .gitignore + +"""]] diff --git a/doc/forum/.mdwn b/doc/forum/.mdwn new file mode 100644 index 000000000..ae58726f4 --- /dev/null +++ b/doc/forum/.mdwn @@ -0,0 +1,3 @@ +http://stackoverflow.com/questions/26041704/removing-repository-in-git-annex + +Does anyone know a solution for this? diff --git a/doc/forum/Direct_Mode_-_Restore_file_from_Full_Backup_Repository__63__/comment_1_67ac7e8b53a4374baf640d32dac79030._comment b/doc/forum/Direct_Mode_-_Restore_file_from_Full_Backup_Repository__63__/comment_1_67ac7e8b53a4374baf640d32dac79030._comment new file mode 100644 index 000000000..21adc4ef9 --- /dev/null +++ b/doc/forum/Direct_Mode_-_Restore_file_from_Full_Backup_Repository__63__/comment_1_67ac7e8b53a4374baf640d32dac79030._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.144" + subject="comment 1" + date="2014-09-25T15:52:04Z" + content=""" +Yes, you need to use git to either revert the repository to a previous version that had the file, or perhaps just revert the commit where the file was deleted. Either way, this requires letting git modify files in the repository, which is prevented by direct mode. So, if you can `git annex indirect` to switch to indirect mode, your git commands will work then. +"""]] diff --git a/doc/forum/Direct_Mode_-_Restore_file_from_Full_Backup_Repository__63__/comment_2_eb6df2bfcb3892ae22050a8c5f67ee90._comment b/doc/forum/Direct_Mode_-_Restore_file_from_Full_Backup_Repository__63__/comment_2_eb6df2bfcb3892ae22050a8c5f67ee90._comment new file mode 100644 index 000000000..5963d4b74 --- /dev/null +++ b/doc/forum/Direct_Mode_-_Restore_file_from_Full_Backup_Repository__63__/comment_2_eb6df2bfcb3892ae22050a8c5f67ee90._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmK0703vNSIQsP1mGf-4MAPnsBZiSc6yVo" + nickname="Emre" + subject="comment 2" + date="2014-09-25T19:25:06Z" + content=""" +Thanks Joeyh, of course i guess checking stuff in git would then lose my timestamps as in the previous post. I recommend, as a feature request, to make file recovery a bit easier if possible. I'm not a git expert and definitely wont use command line stuff for doing this on the long run, unless some more intuitive commands like \"git annex list-old-versions\" or \"git annex show-deleted\" and then \"git annex restore \"filename\" version_no etc. +"""]] diff --git a/doc/forum/Git_annex_assistant_can__39__t_find_rsync_nor_git-annex_on_server/comment_2_496e2f3a61b609ebb28ab55e5c30022b._comment b/doc/forum/Git_annex_assistant_can__39__t_find_rsync_nor_git-annex_on_server/comment_2_496e2f3a61b609ebb28ab55e5c30022b._comment new file mode 100644 index 000000000..f0e63837c --- /dev/null +++ b/doc/forum/Git_annex_assistant_can__39__t_find_rsync_nor_git-annex_on_server/comment_2_496e2f3a61b609ebb28ab55e5c30022b._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.144" + subject="comment 2" + date="2014-09-25T15:42:41Z" + content=""" +You need to be able to `ssh yourserver which rsync` and have it succeed. That's what git-annex uses to probe if rsync etc is present. + +Note that, since that does not start a login shell, bash doesn't source ~/.bash* at all, or even /etc/profile. So none of the ways people add nonstandard directories to PATH will work. + +So, use this to check the PATH that is available on the system: `ssh yourserver 'echo $PATH'` +"""]] diff --git a/doc/forum/Removing_git-annex_repo/comment_1_58fcceb96647a8c7f33d188ae908f3bd._comment b/doc/forum/Removing_git-annex_repo/comment_1_58fcceb96647a8c7f33d188ae908f3bd._comment new file mode 100644 index 000000000..d03ca6b4e --- /dev/null +++ b/doc/forum/Removing_git-annex_repo/comment_1_58fcceb96647a8c7f33d188ae908f3bd._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.144" + subject="comment 1" + date="2014-09-25T15:44:16Z" + content=""" +chmod u+w -R ~/annex/.git +"""]] diff --git a/doc/forum/XMPP_problem_behind_router/comment_2_3186ebe32c30764b9fd53625dd3e4eda._comment b/doc/forum/XMPP_problem_behind_router/comment_2_3186ebe32c30764b9fd53625dd3e4eda._comment new file mode 100644 index 000000000..63387ae3d --- /dev/null +++ b/doc/forum/XMPP_problem_behind_router/comment_2_3186ebe32c30764b9fd53625dd3e4eda._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.144" + subject="comment 2" + date="2014-09-25T15:48:39Z" + content=""" +I don't think that google XMPP server is at gmail.com. This suggests that the SRV record lookup to get from the email server to the xmpp server failed somehow. So, I'd look for a issue on the router's DNS server, or perhaps reconfigure DNS to bypass that server. +"""]] diff --git a/doc/forum/assistant_created_encrypted__backup_remote:_Howto_restore__63__/comment_6_cf877a3502802492cd2bc3012cb2d779._comment b/doc/forum/assistant_created_encrypted__backup_remote:_Howto_restore__63__/comment_6_cf877a3502802492cd2bc3012cb2d779._comment new file mode 100644 index 000000000..3765a67cc --- /dev/null +++ b/doc/forum/assistant_created_encrypted__backup_remote:_Howto_restore__63__/comment_6_cf877a3502802492cd2bc3012cb2d779._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.144" + subject="comment 6" + date="2014-09-25T15:59:34Z" + content=""" +Right. + +So, I think I should go change the description displayed by the webapp to \"full backup (file contents only)\" and \"full backup (entire git repository)\" or so. It's a little hard to word it precisely without making it hard to understand. + +Or, the webapp could display a nudge to make a clone when no other clones of the git repository exist. I think that's probably more valuable, so [[todo_added|todo/webapp_nudge_when_less_than_numcopies_clones]]. +"""]] diff --git a/doc/todo/webapp_nudge_when_less_than_numcopies_clones.mdwn b/doc/todo/webapp_nudge_when_less_than_numcopies_clones.mdwn new file mode 100644 index 000000000..ee38d0fff --- /dev/null +++ b/doc/todo/webapp_nudge_when_less_than_numcopies_clones.mdwn @@ -0,0 +1,7 @@ +Currently, nothing stops a user from setting up ~/annex, adding some special remote, and never once ending up with a clone of their repository, so there is really no backup of the repository as a whole, despite the special remotes. + +Potentially adding to the confusion, they might have remotes in repository groups "full backup" or "backup", and so think everything is backed up. + +Webapp could count the number of known remote uuids that are not special remotes, and require there to be at least numcopies of them (excluding the current repo I suppose), and pop up a nudge with a button that presents the various available ways to make a non-special remote. + +Working out if a remote uuid is a special remote is probably the hard bit. A special remote will be listed in uuid.log, with a type other than gcrypt or git. Any other uuid, that is not dead, can count as 1 clone. This does not handle git remotes that are not using git-annex (eg github), so it could also look through the git remote list and count any that don't have an annex-uuid. |