mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

followup and close

Browse source
This commit is contained in:
Joey Hess 2024-10-22 13:25:46 -04:00
parent 6396926375
commit f54c5260e4
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 28 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
doc/bugs/Wrong_error_message_when_cloning_shared_git_repo.mdwn
View file

@ -60,3 +60,4 @@ on Ubuntu installed from nixpkgs.
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
> Seems to be fixed by current git and/or git-annex. [[done]] --[[Joey]]

27
doc/bugs/Wrong_error_message_when_cloning_shared_git_repo/comment_3_bbb6a406f25388fcc8d88265d3c17bbd._comment Normal file
View file

@ -0,0 +1,27 @@
[[!comment format=mdwn
username="joey"
subject="""comment 3"""
date="2024-10-22T17:15:11Z"
content="""
Here is what I get while cloning:
joey@darkstar:/tmp>git clone localhost:/tmp/manrepo xx
Cloning into 'xx'...
fatal: detected dubious ownership in repository at '/tmp/manrepo/.git'
To add an exception for this directory, call:
git config --global --add safe.directory /tmp/manrepo/.git
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
This is with git 2.45.2, and since current git prevents cloning a repository in
this situation, git-annex doesn't need to do anything.
I also tested what happens if the repository ownership allows cloning, but
after clonging and before git-annex init, the repository owner changes. In
that case, with current git-annex, `git-annex-shell configlist` is able to
get the uuid from the remote repository despite the ownership snafu. Which is
ok.
"""]]