comments

2 files changed, 16 insertions, 8 deletions

diff --git a/doc/bugs/git_annex_test_fails_when_run_through_powershell/comment_1_014466c5da1922d34a498648baeeba26._comment b/doc/bugs/git_annex_test_fails_when_run_through_powershell/comment_1_014466c5da1922d34a498648baeeba26._comment
index f1c898624..f4d67c755 100644
--- a/doc/bugs/git_annex_test_fails_when_run_through_powershell/comment_1_014466c5da1922d34a498648baeeba26._comment
+++ b/doc/bugs/git_annex_test_fails_when_run_through_powershell/comment_1_014466c5da1922d34a498648baeeba26._comment
@@ -3,15 +3,7 @@
  subject="""comment 1"""
  date="2015-07-07T17:23:51Z"
  content="""
-Is the "mv" error message part of the output around the failing addurl
-test, or the failing import test? Not clear from your paste.
-
 The "cannot move" message is not an error message from an external "mv"
 command. This error comes from Win32.moveFileEx, which fails on cross-device
 renames.
-
-Of course, import is supposed to work across devices, and the code
-calls `moveFile`, which is supposed to catch rename errors and fall
-back to an external mv command. Seems that fallback is not working on
-Windows.
 """]]
diff --git a/doc/bugs/git_annex_test_fails_when_run_through_powershell/comment_2_241ab999007eecaa2cd5a854e722e315._comment b/doc/bugs/git_annex_test_fails_when_run_through_powershell/comment_2_241ab999007eecaa2cd5a854e722e315._comment
new file mode 100644
index 000000000..157fed799
--- /dev/null
+++ b/doc/bugs/git_annex_test_fails_when_run_through_powershell/comment_2_241ab999007eecaa2cd5a854e722e315._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2015-07-07T18:15:21Z"
+ content="""
+The import problem can be reproduced by running git annex import on a different
+drive in Windows. No powershell needed; it does fall back to the external
+mv command, but that fails for some reason. Was unable to determine why
+(running the same mv at the command line works ok). Fixed for Windows by
+avoiding using the external mv command there.
+
+Still need more details about the addurl failure. AFAICS, it does not
+involve "mv" at all. Probably it involves
+the generated file:// url not working for some reason. 
+What drive and path did you run the test suite in?
+"""]]