sync: Fix parsing of gcrypt::rsync:// urls that use a relative path
Such an url is not valid; parseURI will fail on it. But git-annex doesn't actually need to parse the url, because all it needs to do to support syncing with it is know that it's not a local path, and use git pull and push. (Note that there is no good reason for the user to use such an url. An absolute url is valid and I patched git-remote-gcrypt to support them years ago. Still, users gonna do anything that tools allow, and git-remote-gcrypt still supports them.) Sponsored-by: Jack Hill on Patreon
This commit is contained in:
parent
0e18bf029e
commit
a0badc5069
12 changed files with 45 additions and 22 deletions
|
@ -102,7 +102,7 @@ list autoinit = do
|
|||
Nothing -> return r
|
||||
Just url -> inRepo $ \g ->
|
||||
Git.Construct.remoteNamed n $
|
||||
Git.Construct.fromRemoteLocation (Git.fromConfigValue url) g
|
||||
Git.Construct.fromRemoteLocation (Git.fromConfigValue url) False g
|
||||
|
||||
{- Git remotes are normally set up using standard git commands, not
|
||||
- git-annex initremote and enableremote.
|
||||
|
@ -118,7 +118,7 @@ gitSetup :: SetupStage -> Maybe UUID -> Maybe CredPair -> RemoteConfig -> Remote
|
|||
gitSetup Init mu _ c _ = do
|
||||
let location = maybe (giveup "Specify location=url") fromProposedAccepted $
|
||||
M.lookup locationField c
|
||||
r <- inRepo $ Git.Construct.fromRemoteLocation location
|
||||
r <- inRepo $ Git.Construct.fromRemoteLocation location False
|
||||
r' <- tryGitConfigRead False r False
|
||||
let u = getUncachedUUID r'
|
||||
if u == NoUUID
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue