I tried some more tests using path to avoid using a file as root...
unison version 2.13.16
# unison -batch a -path file b -backups
Contacting server...
Looking for changes
Reconciling changes
a b
changed ----> file
a : changed file modified on 2009-03-03 at 10:18:50
size 5 rw-rw----
b : unchanged file modified on 2009-03-03 at 10:18:22
size 6 rw-rw----
Propagating updates
UNISON started propagating changes at 10:18:51 on 03 Mar 2009
[BGN] Updating file file
from /tmp/a
to /tmp/b
[END] Updating file file
UNISON finished propagating changes at 10:18:51 on 03 Mar 2009
Saving synchronizer state
Synchronization complete (1 item transferred, 0 skipped, 0 failures)
# ls a b
a:
file notme
b:
file file..001..unison.bak
---
unison version 2.27.57
# unison -batch a -path file b -backups
Contacting server...
Connected [//queeg//tmp/a -> //queeg//tmp/b]
Fatal error: Both old 'backups' preference and new 'backup' preference
are set!
elbou...@queeg:/tmp$ unison -backups -batch a -path file b
Contacting server...
Connected [//queeg//tmp/a -> //queeg//tmp/b]
Fatal error: Both old 'backups' preference and new 'backup' preference
are set!
elbou...@queeg:/tmp$ ls a b
a:
file notme
b:
file file..001..unison.bak
elbou...@queeg:/tmp$ ls -l a b
a:
total 4
-rw-rw---- 1 elbournb users 5 2009-03-03 10:18 file
-rw-rw---- 1 elbournb users 0 2009-03-03 10:18 notme
b:
total 8
-rw-rw---- 1 elbournb users 5 2009-03-03 10:18 file
-rw-rw---- 1 elbournb users 6 2009-03-03 10:18 file..001..unison.bak
----
Basically something seems awry with the handling of the -backups option.
From the 2.27.57 manual:
backups
Setting this flag to true is equivalent to setting backuplocation
to local and backup to Name *.
Soooooooooo:
# unison -backuplocation local -backup 'Name *' -batch a -path file b
Contacting server...
Connected [//queeg//tmp/a -> //queeg//tmp/b]
Looking for changes
Reconciling changes
changed ----> file
a : changed file modified on 2009-03-03 at 10:36:55
size 5 rw-rw----
b : unchanged file modified on 2009-03-03 at 10:31:51
size 9 rw-rw----
Propagating updates
UNISON 2.27.57 started propagating changes at 10:36:59 on 03 Mar 2009
[BGN] Updating file file from /tmp/a to /tmp/b
[END] Updating file file
UNISON 2.27.57 finished propagating changes at 10:36:59 on 03 Mar 2009
Saving synchronizer state
Synchronization complete (1 item transferred, 0 skipped, 0 failures)
elbou...@queeg:/tmp$ ls -l a b a:
total 4
-rw-rw---- 1 elbournb users 5 2009-03-03 10:36 file
-rw-rw---- 1 elbournb users 0 2009-03-03 10:18 notme
b:
total 4
-rw-rw---- 1 elbournb users 5 2009-03-03 10:36 file
Ok. It is replicating but there is no backup. Looks like 2.27.57 has a
regression in all the backup options.
YMMV?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
