From 2195280920871b2f40710055725b80c448791aea Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 9 Oct 2023 14:38:24 -0400 Subject: [PATCH] comment --- ...t_2_b0deace2dcadbd50c0e0cb155041b255._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/bugs/encountering_fatal_error_on_auto_annex_upgrade/comment_2_b0deace2dcadbd50c0e0cb155041b255._comment diff --git a/doc/bugs/encountering_fatal_error_on_auto_annex_upgrade/comment_2_b0deace2dcadbd50c0e0cb155041b255._comment b/doc/bugs/encountering_fatal_error_on_auto_annex_upgrade/comment_2_b0deace2dcadbd50c0e0cb155041b255._comment new file mode 100644 index 0000000000..3d8a5a145c --- /dev/null +++ b/doc/bugs/encountering_fatal_error_on_auto_annex_upgrade/comment_2_b0deace2dcadbd50c0e0cb155041b255._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2023-10-09T18:29:08Z" + content=""" +As to why the upgrade fails, it seems to me that mounting webdav as a +filesystem could easily have incompatabilities that cause strange behavior. + +git can fail with this error message in at least 3 different ways. Although +in all cases it's supposed to be displaying a path where it has "(null)", +so it seems something is causing git to have a null pointer. That seems +like it almost has to be a bug in git. + +It might help to run the git-annex command with --debug to determine what +git command is doing this. +"""]] -- 2.39.5