Hi Taylor, Thanks for your prompt reply. Apologies for this being a support enquiry rather than bug report. Yeah, it was quite a leap actually! I got confused between the core.sharedRepository and safe.directory settings. Setting the latter in the server made it. I presume the intent of safe.directory is to have a more granular control in shared repos. Thank-you very much, Jordi Balcells-Smith Service support specialist - IT operations Community Network Services -----Original Message----- From: Taylor Blau <me@xxxxxxxxxxxx> Sent: Tuesday, October 15, 2024 1:32 AM To: Jordi Balcells-Smith <Jsmith@xxxxxxxxxxxxx> Cc: git@xxxxxxxxxxxxxxx Subject: Re: Git bug report - CNS - Shared repository permissions issues under RedHat 9 On Mon, Oct 14, 2024 at 12:07:07PM +0000, Jordi Balcells-Smith wrote: > We upgraded the operating system from RedHat Enterprise Linux 7 to 9. > This upgrade pulled the version of Git from 1.8.3.1 to 2.43.5. Given that 1.8.3.1 was tagged sometime in June, 2013, I'd say that is quite the jump ;-). > > c:\tmp\gittest>git clone > ssh://10.150.80.53/data/git/cns/repo-parent/repo.git > Cloning into 'repo'... > fatal: detected dubious ownership in repository at '/data/git/cns/repo-parent/repo.git' > To add an exception for this directory, call: > > git config --global --add safe.directory > /data/git/cns/repo-parent/repo.git > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights and the repository > exists This is intentional. Please see the documentation in git-config(1) on safe.directory for more information about what this check does and how to disable it (if you desire). Thanks, Taylor
