fix untrustworthiness of import/export remotes

Commit 36133f27c0 had a boolean flip in it,
aaargh.

Special remotes with importtree=yes or exporttree=yes are once again
treated as untrusted, since files stored in them can be deleted or modified
at any time.

Sponsored-by: Kevin Mueller on Patreon
This commit is contained in:
Joey Hess 2022-05-09 15:53:23 -04:00
parent e8a601aa24
commit 54809e9eb3
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 5 additions and 1 deletions

View file

@ -1,5 +1,9 @@
git-annex (10.20220505) UNRELEASED; urgency=medium
* Special remotes with importtree=yes or exporttree=yes are once again
treated as untrusted, since files stored in them can be deleted or
modified at any time.
(Fixes a reversion in 8.20201129)
* Added support for "megabit" and related bandwidth units
in annex.stalldetection and everywhere else that git-annex parses
data units. Note that the short form is "Mbit" not "Mb" because

View file

@ -216,7 +216,7 @@ adjustExportImport' isexport isimport r rs = do
, untrustworthy =
if versioned || thirdPartyPopulated (remotetype r)
then untrustworthy r
else False
else True
-- git-annex testremote cannot be used to test
-- import/export since it stores keys.
, mkUnavailable = return Nothing