File: comment_2_f105714b9bac7f45fdcb9a47e77255ac._comment

package info (click to toggle)
git-annex 7.20190129-3
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 56,292 kB
  • sloc: haskell: 59,105; sh: 1,255; makefile: 225; perl: 136; ansic: 44
file content (24 lines) | stat: -rw-r--r-- 921 bytes parent folder | download | duplicates (8)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
[[!comment format=mdwn
 username="joey"
 subject="""comment 2"""
 date="2015-10-15T18:30:27Z"
 content="""
Depends.. If one or both special remotes used encryption then no,
one can't see the encrypted files that were put in the other one.

If neither used encryption, and they're otherwise configured the same,
then you can just use `git annex fsck --from A`. This will check files
to see if their content is located on remote A, and if so, and git-annex
had thought the file was only located on remote B, it will update the location
tracking log to reflect the reality that the file is present on A.

If either remote used encryption, then A can't see files that were added
to B. So instead, you need this approach , which involves data transfer:

	git annex enableremote B
	git annex copy --from B
	git annex copy --to A
	git annex drop --from B
	git annex dead B # if it wasn't already dead
	git remote remove B
"""]]