Added a comment: Fetch from good repo to fix uuid.log issue
authorliam <liam@web>
Sun, 20 Apr 2025 12:32:32 +0000 (12:32 +0000)
committeradmin <admin@branchable.com>
Sun, 20 Apr 2025 12:32:32 +0000 (12:32 +0000)
doc/news/version_10.20250416/comment_3_9a9b7aa33311822ab38c00ca7477668b._comment [new file with mode: 0644]

diff --git a/doc/news/version_10.20250416/comment_3_9a9b7aa33311822ab38c00ca7477668b._comment b/doc/news/version_10.20250416/comment_3_9a9b7aa33311822ab38c00ca7477668b._comment
new file mode 100644 (file)
index 0000000..6c4d462
--- /dev/null
@@ -0,0 +1,20 @@
+[[!comment format=mdwn
+ username="liam"
+ avatar="http://cdn.libravatar.org/avatar/5cb416d010c1d3f0ca677dd7f6c822ea"
+ subject="Fetch from good repo to fix uuid.log issue"
+ date="2025-04-20T12:32:31Z"
+ content="""
+Hi,
+
+So to resolve the .DS_Store issue, I just had to go into the .git repo and remove all the .DS_Store files that MacOS littered around.
+
+To fix the repo itself, I ended up doing a `git fetch goodremote` and this seems to have fixed the issue.
+I can now run `git annex info` again without a problem.
+
+The weird thing is, it was complaining about `uuid.log`, however, when running `git show git-annex:uuid.log` I was getting the same output on both repos.
+It's not clear what went wrong. Maybe corruption but `git fsck` never showed an issue. Fetching from a good repo seems to have fixed it.
+
+Hopefully this helps if anyone has a similar problem.
+
+Liam
+"""]]