From 6280fac98bc12f755e12f97fcd6d79ceef15d137 Mon Sep 17 00:00:00 2001 From: datamanager Date: Tue, 21 May 2024 01:16:02 +0000 Subject: [PATCH 1/6] Initial thread posting --- .../Strange_symlinkPointsToGitDir_error.mdwn | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 doc/forum/Strange_symlinkPointsToGitDir_error.mdwn diff --git a/doc/forum/Strange_symlinkPointsToGitDir_error.mdwn b/doc/forum/Strange_symlinkPointsToGitDir_error.mdwn new file mode 100644 index 0000000000..a42ab4da4c --- /dev/null +++ b/doc/forum/Strange_symlinkPointsToGitDir_error.mdwn @@ -0,0 +1,24 @@ +Today, I got the strange error below. I unlocked a file, and edited it, and attempted to sync, when I saw the error. + +``` +remote: error: object a86b9c49d9ef8c88c3180013eef3da5f6ffa9353: symlinkPointsToGitDir: symlink target points to git dir +remote: error: object ebb743ffb44e23c54a7e3ed44a444cc0ed0df42d: symlinkPointsToGitDir: symlink target points to git dir +remote: fatal: fsck error in pack objects +error: remote unpack failed: unpack-objects abnormal exit +To gitlab.com:daraul/taskwarrior.git + ! [remote rejected] git-annex -> synced/git-annex (unpacker error) + ! [remote rejected] master -> synced/master (unpacker error) +error: failed to push some refs to 'gitlab.com:daraul/taskwarrior.git' +remote: error: object a86b9c49d9ef8c88c3180013eef3da5f6ffa9353: symlinkPointsToGitDir: symlink target points to git dir +remote: error: object ebb743ffb44e23c54a7e3ed44a444cc0ed0df42d: symlinkPointsToGitDir: symlink target points to git dir +remote: fatal: fsck error in pack objects +error: remote unpack failed: unpack-objects abnormal exit +To gitlab.com:daraul/taskwarrior.git + ! [remote rejected] master -> master (unpacker error) +``` + +It's strange because I've done this unlock, edit, and sync, flow a few times in the past week, with no problems. I've only been able to find one reference point for this, in [git's own documentation](https://git-scm.com/docs/git-fsck#Documentation/git-fsck.txt-codesymlinkPointsToGitDircode). + +It's very concerning because it prevents me from syncing with my remote repository at all. I was able to work around the problem with `git reset HEAD~` so I could at least get a few changes sent to my remote, but that meant I lost all the changes I made to the file itself. + +Can anyone say what the proble might be here? From d94ce5319b89cee28ea43d91377c2a69135f9c28 Mon Sep 17 00:00:00 2001 From: datamanager Date: Tue, 21 May 2024 01:16:50 +0000 Subject: [PATCH 2/6] A correction, and small update --- doc/forum/Strange_symlinkPointsToGitDir_error.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/forum/Strange_symlinkPointsToGitDir_error.mdwn b/doc/forum/Strange_symlinkPointsToGitDir_error.mdwn index a42ab4da4c..8e033b6bbd 100644 --- a/doc/forum/Strange_symlinkPointsToGitDir_error.mdwn +++ b/doc/forum/Strange_symlinkPointsToGitDir_error.mdwn @@ -21,4 +21,4 @@ It's strange because I've done this unlock, edit, and sync, flow a few times in It's very concerning because it prevents me from syncing with my remote repository at all. I was able to work around the problem with `git reset HEAD~` so I could at least get a few changes sent to my remote, but that meant I lost all the changes I made to the file itself. -Can anyone say what the proble might be here? +Can anyone say what the problem might be here? Why does git suddenly seem upset that I've got a symlink pointing at my git directory? From f0923985aaab14ae8df4fbde452900fe68476968 Mon Sep 17 00:00:00 2001 From: nobodyinperson Date: Tue, 21 May 2024 10:41:08 +0000 Subject: [PATCH 3/6] Added a comment: Seeing this for the first time today as well --- .../comment_1_4c956980c36a60bf6bcb47f58aa11f4b._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Strange_symlinkPointsToGitDir_error/comment_1_4c956980c36a60bf6bcb47f58aa11f4b._comment diff --git a/doc/forum/Strange_symlinkPointsToGitDir_error/comment_1_4c956980c36a60bf6bcb47f58aa11f4b._comment b/doc/forum/Strange_symlinkPointsToGitDir_error/comment_1_4c956980c36a60bf6bcb47f58aa11f4b._comment new file mode 100644 index 0000000000..9a3a57e7da --- /dev/null +++ b/doc/forum/Strange_symlinkPointsToGitDir_error/comment_1_4c956980c36a60bf6bcb47f58aa11f4b._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="nobodyinperson" + avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5" + subject="Seeing this for the first time today as well" + date="2024-05-21T10:41:08Z" + content=""" +I just got the same weird error `git annex assist`ing to GitLab with git annex 10.20240129. +"""]] From 04aa259cfa2cfa1e63799d75e02613b56da011ac Mon Sep 17 00:00:00 2001 From: nobodyinperson Date: Tue, 21 May 2024 10:49:58 +0000 Subject: [PATCH 4/6] Added a comment: Probably not git annex related, but a new git 'feature' --- ...comment_2_ad3cd43822bd5b256f12bfd55cde9e55._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/Strange_symlinkPointsToGitDir_error/comment_2_ad3cd43822bd5b256f12bfd55cde9e55._comment diff --git a/doc/forum/Strange_symlinkPointsToGitDir_error/comment_2_ad3cd43822bd5b256f12bfd55cde9e55._comment b/doc/forum/Strange_symlinkPointsToGitDir_error/comment_2_ad3cd43822bd5b256f12bfd55cde9e55._comment new file mode 100644 index 0000000000..8eaf724853 --- /dev/null +++ b/doc/forum/Strange_symlinkPointsToGitDir_error/comment_2_ad3cd43822bd5b256f12bfd55cde9e55._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="nobodyinperson" + avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5" + subject="Probably not git annex related, but a new git 'feature'" + date="2024-05-21T10:49:58Z" + content=""" +Apparently, very recent git (https://github.com/git/git/commit/a33fea0886cfa016d313d2bd66bdd08615bffbc9) got a check for symlinks pointing to the git dir, causing the remote to reject such commits. Brilliant idea to implement something like that... 🤦 GitLab seems to have that new git version. + + +"""]] From 2135514bc7dfb981cc5046b25c04de2dbf643ef5 Mon Sep 17 00:00:00 2001 From: datamanager Date: Tue, 21 May 2024 13:12:23 +0000 Subject: [PATCH 5/6] Added a comment: Not git's fault, but probably your forge's --- ...nt_3_37ff83879073be91a824d83db0ca7720._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/forum/Strange_symlinkPointsToGitDir_error/comment_3_37ff83879073be91a824d83db0ca7720._comment diff --git a/doc/forum/Strange_symlinkPointsToGitDir_error/comment_3_37ff83879073be91a824d83db0ca7720._comment b/doc/forum/Strange_symlinkPointsToGitDir_error/comment_3_37ff83879073be91a824d83db0ca7720._comment new file mode 100644 index 0000000000..964d435133 --- /dev/null +++ b/doc/forum/Strange_symlinkPointsToGitDir_error/comment_3_37ff83879073be91a824d83db0ca7720._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="datamanager" + avatar="http://cdn.libravatar.org/avatar/7d4ca7c5e571d4740ef072b83a746c12" + subject="Not git's fault, but probably your forge's" + date="2024-05-21T13:12:22Z" + content=""" +I don't think this is git's fault, but my gitlab's. The commit says that setting +`fsck.symlinkPointsToGitDir` to `warn` should avoid the problem. It seems, +however, that gitlab has it set to `error` -- your forge probably has the same +setting as well. I can think of only two solutions: + +1. Ask gitlab for recourse: maybe they can respect the setting in your local repository +2. Change to a forge that has it set to `warn` + +"""]] From 1ab1ea0bcc5b574d4486bf1f44d605ebde236650 Mon Sep 17 00:00:00 2001 From: nobodyinperson Date: Tue, 21 May 2024 13:25:54 +0000 Subject: [PATCH 6/6] Added a comment --- .../comment_4_75c38f7093208ff29b7bd414857626af._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Strange_symlinkPointsToGitDir_error/comment_4_75c38f7093208ff29b7bd414857626af._comment diff --git a/doc/forum/Strange_symlinkPointsToGitDir_error/comment_4_75c38f7093208ff29b7bd414857626af._comment b/doc/forum/Strange_symlinkPointsToGitDir_error/comment_4_75c38f7093208ff29b7bd414857626af._comment new file mode 100644 index 0000000000..4aa14e8f4d --- /dev/null +++ b/doc/forum/Strange_symlinkPointsToGitDir_error/comment_4_75c38f7093208ff29b7bd414857626af._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="nobodyinperson" + avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5" + subject="comment 4" + date="2024-05-21T13:25:54Z" + content=""" +Yup, that's my understanding as well. I made a [forum post](https://forum.gitlab.com/t/recent-git-v2-45-1-breaks-git-annex-compatibility/104909/1) at GitLab, but it's still under the noob-posting-spam-protection... Forgejo apparently doesn't exhibit this behaviour btw. +"""]]