#19 Duplicate IDs cause major problems due to acquisition

[Paul Winkler]

Consider this scenario:

Source has this folder tree:

A / B / C/ D/
D /

So there are two folders named D:
one in A, one in C.

Destination has this folder tree:

A/ B/ C/
D/
... so it is the same but missing A/B/C/D.

If you use zsyncer from the source server, and
go to A/B/C/D, manage_compare will show you
results acquired from the destination at A/D since it has
no A/B/C/D. And if you sync something
expecting it to end up in A/B/C/D, it will actually
show up in A/D/.
Similarly, if you remotely delete the contents of D,
you will
actually be deleting A/D.

In sum, we need to be sure we're always using
containment, not acquired contents.

[Paul Winkler]

Logged In: YES
user_id=38329

Now that we have a working test framework, I need to verify
if this is fixed. I think it is.