From 62129f0b24dbfbe5d80ca53696bcc505a5b66409 Mon Sep 17 00:00:00 2001
From: Joey Hess <joeyh@joeyh.name>
Date: Mon, 25 Mar 2024 14:11:25 -0400
Subject: [PATCH] fix windows transfer lock check

If the lock file was not able to be exclusivlely locked, don't indicate
locking failed. I'm pretty sure this was a typo. It goes all the way
back to 891c85cd88c5a90daf7d18160eeddd1483e8c649 where locking was first
introduced on windows, and there's no indication of why it would make
sense to return True here.

Sponsored-by: Leon Schuermann on Patreon
---
 Annex/Transfer.hs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Annex/Transfer.hs b/Annex/Transfer.hs
index 7bf0ca365b..501faac1ed 100644
--- a/Annex/Transfer.hs
+++ b/Annex/Transfer.hs
@@ -171,7 +171,7 @@ runTransfer' ignorelock t eventualbackend afile stalldetection retrydecider tran
 		createAnnexDirectory $ P.takeDirectory lck
 		catchMaybeIO (liftIO $ lockExclusive lck) >>= \case
 			Nothing -> return (Nothing, False)
-			Just Nothing -> return (Nothing, True)
+			Just Nothing -> return (Nothing, False)
 			Just (Just lockhandle) -> do
 				createtfile
 				return (Just lockhandle, False)