prevent initialization with bad freeze/thaw hook configured
When annex.freezecontent-command or annex.thawcontent-command is configured but fails, prevent initialization. This allows the user to fix their configuration and avoid crippled filesystem detection entering an adjusted unlocked branch unexpectedly, when they had been relying on the hooks working around their filesystems's infelicities. In the case of git-remote-annex, a failure of these hooks is taken to mean the filesystem may be crippled, so it deletes the bundles objects and avoids initialization. That might mean extra work, but only in this edge case where the hook is misconfigured. And it keeps the command working for cloning even despite the misconfiguration. Sponsored-by: the NIH-funded NICEMAN (ReproNim TR&D3) project
This commit is contained in:
parent
adc7a51a9e
commit
bff089a392
8 changed files with 162 additions and 70 deletions
|
@ -1204,7 +1204,7 @@ cleanupInitialization sab alternatejournaldir = void $ tryNonAsync $ do
|
|||
_ -> noop
|
||||
void $ liftIO $ tryIO $ removeDirectory annexobjectdir
|
||||
|
||||
notcrippledfilesystem = not <$> probeCrippledFileSystem
|
||||
notcrippledfilesystem = not <$> isCrippledFileSystem
|
||||
|
||||
nonbuggygitversion = liftIO $
|
||||
flip notElem buggygitversions <$> Git.Version.installed
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue