]> dgit.raspbian.org Git - git-annex.git/commitdiff
comment
authorJoey Hess <joeyh@joeyh.name>
Tue, 16 Aug 2022 16:09:12 +0000 (12:09 -0400)
committerJoey Hess <joeyh@joeyh.name>
Tue, 16 Aug 2022 16:09:12 +0000 (12:09 -0400)
doc/forum/Android__58___repository_is_not_initialized_for_use_by_/comment_4_99d78dca3534c4d54f6925a095f1d43f._comment [new file with mode: 0644]

diff --git a/doc/forum/Android__58___repository_is_not_initialized_for_use_by_/comment_4_99d78dca3534c4d54f6925a095f1d43f._comment b/doc/forum/Android__58___repository_is_not_initialized_for_use_by_/comment_4_99d78dca3534c4d54f6925a095f1d43f._comment
new file mode 100644 (file)
index 0000000..d22a6e1
--- /dev/null
@@ -0,0 +1,23 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 4"""
+ date="2022-08-16T16:03:57Z"
+ content="""
+Aha, that is a useful clue about what's going on here!
+
+Since those smudge commands are run by git, it may be that git is doing
+something to the environment or cwd that prevents git-annex from reading
+the git config.
+
+Also, you have git installed in termux, but git-annex includes its
+own copy of git in its distribution. So it may be that the termux git is
+somehow causing this problem, but the one included in git-annex does not.
+
+Can you try running: 
+
+       cd git-annex.linux
+       ./runshell
+
+And then see if the problem occurs when you use git-annex from within the
+shell that starts?
+"""]]