From 70a15660de1b38564bf92e823c74049ca3b66ae7 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 16 Oct 2012 05:56:10 +0000 Subject: [PATCH 1/7] Added a comment --- .../comment_2_0d751d81ac618f8d7e3f1dd20c830542._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/Crash_trying_to_sync_with_a_repo_over_ssh/comment_2_0d751d81ac618f8d7e3f1dd20c830542._comment diff --git a/doc/bugs/Crash_trying_to_sync_with_a_repo_over_ssh/comment_2_0d751d81ac618f8d7e3f1dd20c830542._comment b/doc/bugs/Crash_trying_to_sync_with_a_repo_over_ssh/comment_2_0d751d81ac618f8d7e3f1dd20c830542._comment new file mode 100644 index 0000000000..5622bd6da1 --- /dev/null +++ b/doc/bugs/Crash_trying_to_sync_with_a_repo_over_ssh/comment_2_0d751d81ac618f8d7e3f1dd20c830542._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.152.246.8" + subject="comment 2" + date="2012-10-16T05:56:10Z" + content=""" +And I found a clean way to avoid that partial !! too. :) Down to 22 of the little monsters to clean up now. +"""]] From 87dd423d796acfe305344cbccf69e3aa2ec23ab0 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnZ0g2UAijV7RGrKtWPljCCAYHBJ3pwPvM" Date: Tue, 16 Oct 2012 06:01:38 +0000 Subject: [PATCH 2/7] Added a comment --- .../comment_11_7f9453c69a813cf86f42d49237e83a29._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Can__39__t_init_git_annex/comment_11_7f9453c69a813cf86f42d49237e83a29._comment diff --git a/doc/forum/Can__39__t_init_git_annex/comment_11_7f9453c69a813cf86f42d49237e83a29._comment b/doc/forum/Can__39__t_init_git_annex/comment_11_7f9453c69a813cf86f42d49237e83a29._comment new file mode 100644 index 0000000000..0d1ebde6d1 --- /dev/null +++ b/doc/forum/Can__39__t_init_git_annex/comment_11_7f9453c69a813cf86f42d49237e83a29._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnZ0g2UAijV7RGrKtWPljCCAYHBJ3pwPvM" + nickname="Meng" + subject="comment 11" + date="2012-10-16T06:01:38Z" + content=""" +OK; The purpose of putting files on the remote `smb://` partition is to publish these big data files, so other (potentially non-technical) people can download and use them. They'll not be willing to learn how to use git, let alone git-annex. And i have multiple development machines that can generate revisions/updates to these big files. I previously just rsync from/to various development machines to/from this smb partition, but i find sometimes I don't always srync in correct direction. The hope is i can have annex on these development machines, and set the smb:// partition as the remote for these git annex. But it sounds like none of the special remote will have the original form, and a normal remote is not possible on smb:// partition. +"""]] From 44050301c22a8706a82e021c350d7f8ab4968a13 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnZ0g2UAijV7RGrKtWPljCCAYHBJ3pwPvM" Date: Tue, 16 Oct 2012 06:01:44 +0000 Subject: [PATCH 3/7] Added a comment --- .../comment_12_fca9ed3707e097bee2cd642424681005._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Can__39__t_init_git_annex/comment_12_fca9ed3707e097bee2cd642424681005._comment diff --git a/doc/forum/Can__39__t_init_git_annex/comment_12_fca9ed3707e097bee2cd642424681005._comment b/doc/forum/Can__39__t_init_git_annex/comment_12_fca9ed3707e097bee2cd642424681005._comment new file mode 100644 index 0000000000..adc9fba3bb --- /dev/null +++ b/doc/forum/Can__39__t_init_git_annex/comment_12_fca9ed3707e097bee2cd642424681005._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnZ0g2UAijV7RGrKtWPljCCAYHBJ3pwPvM" + nickname="Meng" + subject="comment 12" + date="2012-10-16T06:01:44Z" + content=""" +OK; The purpose of putting files on the remote `smb://` partition is to publish these big data files, so other (potentially non-technical) people can download and use them. They'll not be willing to learn how to use git, let alone git-annex. And i have multiple development machines that can generate revisions/updates to these big files. I previously just rsync from/to various development machines to/from this smb partition, but i find sometimes I don't always srync in correct direction. The hope is i can have annex on these development machines, and set the smb:// partition as the remote for these git annex. But it sounds like none of the special remote will have the original form, and a normal remote is not possible on smb:// partition. +"""]] From 6996d834cb2f3f31c6e8966a3219e07ed07a09bb Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnZ0g2UAijV7RGrKtWPljCCAYHBJ3pwPvM" Date: Tue, 16 Oct 2012 06:01:57 +0000 Subject: [PATCH 4/7] removed --- .../comment_11_7f9453c69a813cf86f42d49237e83a29._comment | 8 -------- 1 file changed, 8 deletions(-) delete mode 100644 doc/forum/Can__39__t_init_git_annex/comment_11_7f9453c69a813cf86f42d49237e83a29._comment diff --git a/doc/forum/Can__39__t_init_git_annex/comment_11_7f9453c69a813cf86f42d49237e83a29._comment b/doc/forum/Can__39__t_init_git_annex/comment_11_7f9453c69a813cf86f42d49237e83a29._comment deleted file mode 100644 index 0d1ebde6d1..0000000000 --- a/doc/forum/Can__39__t_init_git_annex/comment_11_7f9453c69a813cf86f42d49237e83a29._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnZ0g2UAijV7RGrKtWPljCCAYHBJ3pwPvM" - nickname="Meng" - subject="comment 11" - date="2012-10-16T06:01:38Z" - content=""" -OK; The purpose of putting files on the remote `smb://` partition is to publish these big data files, so other (potentially non-technical) people can download and use them. They'll not be willing to learn how to use git, let alone git-annex. And i have multiple development machines that can generate revisions/updates to these big files. I previously just rsync from/to various development machines to/from this smb partition, but i find sometimes I don't always srync in correct direction. The hope is i can have annex on these development machines, and set the smb:// partition as the remote for these git annex. But it sounds like none of the special remote will have the original form, and a normal remote is not possible on smb:// partition. -"""]] From e9387aee5ccdaec936783ddd81762c14735583e4 Mon Sep 17 00:00:00 2001 From: EskildHustvedt Date: Tue, 16 Oct 2012 07:58:45 +0000 Subject: [PATCH 5/7] --- ...and_eats_up_all_of_RAM_after_X_restart.mdwn | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/bugs/Assistant_enters_eternal_loop_and_eats_up_all_of_RAM_after_X_restart.mdwn diff --git a/doc/bugs/Assistant_enters_eternal_loop_and_eats_up_all_of_RAM_after_X_restart.mdwn b/doc/bugs/Assistant_enters_eternal_loop_and_eats_up_all_of_RAM_after_X_restart.mdwn new file mode 100644 index 0000000000..bf364370d1 --- /dev/null +++ b/doc/bugs/Assistant_enters_eternal_loop_and_eats_up_all_of_RAM_after_X_restart.mdwn @@ -0,0 +1,18 @@ +*What steps will reproduce the problem?* + +Log in to X, have the DE start the assistant with --autostart. Then kill X with ctrl+alt+backspace and log back in once X comes back up. + +*What is the expected output? What do you see instead?* + +It enters an eternal loop, quickly using up all of the available RAM as well as 100% of CPU. Initially noticed because the computer became extremely sluggish, at which point the assistant was using up over 7G (of the available 8G) of RAM, and all of the available power on one of the CPU cores. + +Killing the assistant and then starting it again results in it working normally again. + +*What version of git-annex are you using? On what operating system?* + +git-annex version: 3.20121010 on Debian Sid (under GNOME3/Gnome-Shell in case that's relevant). +I've also seen it happen on another computer in similar circumstances. That one on Debian Testing, with git-annex from sid (so same git-annex version). In this case X was restarted while running with /etc/init.d/gdm3 restart, and again the issue appeared after logging out and then back in. + +*Please provide any additional information below.* + +Given that the assistant isn't really using X directly, I suppose this could be due to losing its connection to the gpg and ssh agents as a side-effect of X being shut down. I'm not sure if it happens immediately after X being killed, or once I log back in again. From 148f7ee1f34ab236f83d825f810207387ae7de8e Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawkywesyg6tKBZcmxJ2EMUO89DZL1LZ7Sng" Date: Tue, 16 Oct 2012 12:02:27 +0000 Subject: [PATCH 6/7] Added a comment --- ..._69aec9207d2e9da4bc042d3f4963d80e._comment | 48 +++++++++++++++++++ 1 file changed, 48 insertions(+) create mode 100644 doc/bugs/submodule_path_problem/comment_1_69aec9207d2e9da4bc042d3f4963d80e._comment diff --git a/doc/bugs/submodule_path_problem/comment_1_69aec9207d2e9da4bc042d3f4963d80e._comment b/doc/bugs/submodule_path_problem/comment_1_69aec9207d2e9da4bc042d3f4963d80e._comment new file mode 100644 index 0000000000..1ff33e36ad --- /dev/null +++ b/doc/bugs/submodule_path_problem/comment_1_69aec9207d2e9da4bc042d3f4963d80e._comment @@ -0,0 +1,48 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkywesyg6tKBZcmxJ2EMUO89DZL1LZ7Sng" + nickname="Peter" + subject="comment 1" + date="2012-10-16T12:02:27Z" + content=""" +Not quite there yet. + +git-annex init works now, but there is still a problem with paths: + +Using the same setup as previously, git-annex init now works: + + cd lib/submod + git annex init + +But adding a file failes: + + git annex add big-file + +Output: + + add big-file (checksum...) + git-annex: big-file: getFileStatus: does not exist (No such file or directory) + failed + (Recording state in git...) + git-annex: add: 1 failed + +Debug: + + +[2012-10-16 13:59:26 CEST] read: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"ls-files\",\"--others\",\"--exclude-standard\",\"-z\",\"--\",\"big-file\"] +[2012-10-16 13:59:26 CEST] read: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"diff\",\"--name-only\",\"--diff-filter=T\",\"-z\",\"--\",\"big-file\"] +add big-file [2012-10-16 13:59:26 CEST] chat: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"check-attr\",\"-z\",\"--stdin\",\"annex.backend\",\"annex.numcopies\",\"--\"] +(checksum...) [2012-10-16 13:59:26 CEST] chat: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"cat-file\",\"--batch\"] + +git-annex: big-file: getFileStatus: does not exist (No such file or directory) +failed + + [2012-10-16 13:59:26 CEST] chat: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"hash-object\",\"-w\",\"--stdin-paths\"] + [2012-10-16 13:59:26 CEST] feed: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"update-index\",\"-z\",\"--index-info\"] + [2012-10-16 13:59:26 CEST] read: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] + (Recording state in git...) + [2012-10-16 13:59:26 CEST] read: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"write-tree\"] + [2012-10-16 13:59:26 CEST] chat: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"commit-tree\",\"ed2f98d7105deed7482b3dde43426c177b360131\",\"-p\",\"refs/heads/git-annex\"] + [2012-10-16 13:59:26 CEST] call: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"update-ref\",\"refs/heads/git-annex\",\"df49e7bef8409dff450ce549c40f4ab429ea3144\"] + [2012-10-16 13:59:26 CEST] chat: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"cat-file\",\"--batch\"] + git-annex: add: 1 failed +"""]] From fdca690900fa3fe0206464512904518637fddf37 Mon Sep 17 00:00:00 2001 From: "https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89" Date: Tue, 16 Oct 2012 16:30:57 +0000 Subject: [PATCH 7/7] --- doc/todo/wishlist:_An_option_like_--git-dir.mdwn | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 doc/todo/wishlist:_An_option_like_--git-dir.mdwn diff --git a/doc/todo/wishlist:_An_option_like_--git-dir.mdwn b/doc/todo/wishlist:_An_option_like_--git-dir.mdwn new file mode 100644 index 0000000000..cb9d374b39 --- /dev/null +++ b/doc/todo/wishlist:_An_option_like_--git-dir.mdwn @@ -0,0 +1,3 @@ +I'm currently integrating git-annex support into a filesystem synchronization tool that I use, and I have a use case where I'd like to run "git annex sync' on a local directory, and then automatically ssh over to remote hosts and run "git annex sync" in the related annex on that remote host. However, while I can easily "cd" on the local, there is no really easy way to "cd" on the remote without a hack. + +If I could say: git annex --annex-dir=PATH sync, where PATH is the annex directory, it would solve all my problems, and would also provide a nice correlation to the --git-dir option used by most Git commands. The basic idea is that I shouldn't have to be IN the directory to run git-annex commands, I should be able to tell git-annex which directory to apply its commands to.