Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • 2
    First thing I'd do is add id to the script to see user and group identities of the process, and check permissions of /home/git/bubblegum/.git. An ls -l .git just in case might also help if you for some reason have funny mounting stuff going on (unlikely, but who knows). Commented Sep 2, 2021 at 9:05
  • Good idea @dirkt, I have edited this information in Commented Sep 2, 2021 at 9:50
  • I do not have any other filesystems mounted in or under /home/git/bubblegum/.git/; I would consider this bad practise Commented Sep 2, 2021 at 9:51
  • Is /home NFS-mounted, or similar? And I'd still add the ls -l .git; as the permissions are ok, something must confuse git pull, so debugging consists of collecting information about what git pull in that situation actually sees that makes it complain. Also do GIT_CURL_VERBOSE=1 GIT_TRACE=1 git pull -v .. Commented Sep 2, 2021 at 10:18
  • 2
    You run git pull . in /home/git/bubblegum, meaning you pull the changes from the repo you are in? Why do you pull from pwd and not from another source? Commented Sep 2, 2021 at 10:56