(no commit message)
authorjose1711 <jose1711@web>
Thu, 26 Jun 2025 17:31:49 +0000 (17:31 +0000)
committeradmin <admin@branchable.com>
Thu, 26 Jun 2025 17:31:49 +0000 (17:31 +0000)
doc/forum/Old_files_being_pushed_to_transfer_repository.mdwn [new file with mode: 0644]

diff --git a/doc/forum/Old_files_being_pushed_to_transfer_repository.mdwn b/doc/forum/Old_files_being_pushed_to_transfer_repository.mdwn
new file mode 100644 (file)
index 0000000..f48589b
--- /dev/null
@@ -0,0 +1,15 @@
+Hello,
+
+could someone please help me understand why old files are being pushed to `transfer`-type repository on `git annex sync --content`? The command is executed from a `client`-type repository. The goal is to have new photos downloaded from `transfer`, not the other way around.
+
+With `--explain` I am seeing:
+
+```
+[ 20210428_164158.jpg matches preferred content: standard[TRUE] ]
+copy 20210428_164158.jpg (to transfer_repository...) 
+ok
+```
+
+`transfer_repository` is put into `transfer` group and wanted is set to `standard` hence it *should* not want the old files (there is a client repo that already has them).
+
+Thanks, jose