copy --from --to location tracking update

copy: When --from and --to are combined and the content is already present
on the destination remote, update location tracking as necessary.

Sponsored-by: Dartmouth College's DANDI project
This commit is contained in:
Joey Hess 2023-03-13 14:50:28 -04:00
parent 38e9ea8497
commit f1b678face
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 19 additions and 0 deletions

View file

@ -13,6 +13,9 @@ git-annex (10.20230228) UNRELEASED; urgency=medium
build.
* importfeed: Display feed title.
* init: Support being ran in a repository that has a newline in its path.
* copy: When --from and --to are combined and the content is already
present on the destination remote, update location tracking as
necessary.
-- Joey Hess <id@joeyh.name> Mon, 27 Feb 2023 12:31:14 -0400

View file

@ -399,6 +399,9 @@ fromToPerform src dest removewhen key afile = do
Right True -> do
showAction $ "from " ++ Remote.name src
showAction $ "to " ++ Remote.name dest
-- The log may not indicate dest's copy
-- yet, so make sure it does.
logChange key (Remote.uuid dest) InfoPresent
-- Drop from src, checking copies including
-- the one already in dest.
dropfromsrc id

View file

@ -51,3 +51,5 @@ I would expect `copy` to make a record locally that now the content is also on d
[[!meta author=yoh]]
[[!tag projects/dandi]]
> [[fixed|done]] --[[Joey]]

View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2023-03-13T18:34:36Z"
content="""
Aah, I see, this is when the content is present on the --to
remote, but git-annex is not locally aware of that yet.
And `git-annex copy --to remote` does
update location tracking in such a case, so --from --to should also.
"""]]