git-remote-annex: Fix cloning from a special remote on a crippled filesystem

Not initializing and so deleting the bundles only causes a little more work
on the first git fetch.
This commit is contained in:
Joey Hess 2024-11-19 12:43:51 -04:00
parent 1ff54a3b44
commit df29f29e0d
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 28 additions and 2 deletions

View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2024-11-19T16:18:31Z"
content="""
This is a new test.
Looks like it's found a legitimate bug in git-remote-annex. When the
filesystem is crippled, the git-annex init checks out an adjusted branch,
which here happens in the middle of git's own checkout and so legitimately
confuses git.
I can reproduce this on a FAT filesystem, cloning from eg a directory
special remote. Fixed this.
(The OSX failure is something else.)
"""]]