From d910a94df7d6f5c87897c248586cb65523457f99 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 7 Sep 2017 13:45:31 -0400 Subject: prevent exporttree=yes on remotes that don't support exports Don't allow "exporttree=yes" to be set when the special remote does not support exports. That would be confusing since the user would set up a special remote for exports, but `git annex export` to it would later fail. This commit was supported by the NSF-funded DataLad project. --- Logs/Trust.hs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'Logs/Trust.hs') diff --git a/Logs/Trust.hs b/Logs/Trust.hs index 85b62ed74..54cafc9f4 100644 --- a/Logs/Trust.hs +++ b/Logs/Trust.hs @@ -67,7 +67,7 @@ trustMapLoad = do overrides <- Annex.getState Annex.forcetrust l <- remoteList -- Exports are never trusted, since they are not key/value stores. - exports <- filterM (Types.Remote.exportSupported . Types.Remote.exportActions) l + exports <- filterM Types.Remote.isExportSupported l let exportoverrides = M.fromList $ map (\r -> (Types.Remote.uuid r, UnTrusted)) exports logged <- trustMapRaw -- cgit v1.2.3