Ladies and Gentlemen,We have a unique challenge that we're trying to address using fsvs. We havea lot of servers out "in the wild" as it were, and instead of using somesort of package management system to upgrade the OS and our own software, wewant to use fsvs.

The idea is that we can make updates on our own master server, check theminto fsvs/subversion, and then have each of the "in the wild" servers updatefrom fsvs/subversion. This seems like a great idea, but we've had a bit ofdifficulty when trying to actually get these updates to work.

In our testing environment, we'll make some changes and then commit themfine, but when we try to do an update, we will often (but not always) getsomething like the following:

We've tried with and without the "-r <revision>", and we don't always getthe same file as having changed (though it is usually one of a handful offiles). I'm fairly certain that the file in question has not in factchanged. One thing we've tried is doing a revert just before an update, butthat doesn't seem to fix it.

We really like fsvs, from a conceptual level, and it seems like the rightsolution, but this has us pulling our hair out. Can anyone shine any lighton the situation? Is this an imporper use of this package? Are we missingsomething obvious? I can elaborate on our setup and such, if that would behelpful, but I don't want to dump a bunch of configs on this list if itisn't necessary.