On Saturday 20 January 2007 21:42 Gunter Ohrner wrote:
> Am Samstag, 20. Januar 2007 16:16 schrieb Philipp Marek:
> > > The "fsvs status" after the sync-repos shows that fsvs incorrectly
> > > thinks that the working copy is in sync.
> >
> > I'll take a look.
> In fact, after a sync-repos on my "live" directory structure, fsvs 1.0.15
> didn't show ANY file as changed, it only recognized (and transmitted) new
> files.
>
> That worked fine, however.
I can re-create the bug.
What helps is "-C -C", ie. checksum every file:
[EMAIL PROTECTED]:/tmp/testdir2$ WAA=/tmp/waa/ ~/svk/fsvs/fsvs/src/fsvs st
[EMAIL PROTECTED]:/tmp/testdir2$ WAA=/tmp/waa/ ~/svk/fsvs/fsvs/src/fsvs st
-C
[EMAIL PROTECTED]:/tmp/testdir2$ WAA=/tmp/waa/ ~/svk/fsvs/fsvs/src/fsvs st
-C -C
..C. 7 ./Datei2
A "fsvs commit -C -C" would work.
But that's not how it should be, of course.
Sadly we don't get the filesize on sync-repos - then it would be much
better ... I think we should store the filesize in another property.
Do you want to extend fsvs for that?
The problem seems to be line 173 in update.c:
{
==> /* Take the newer of the two timestamps. */
if (apr_time_sec(at) >= sts->st.mtim.tv_sec)
{
sts->st.mtim.tv_sec=apr_time_sec(at);
That was to get some kind of sane make-behaviour, IIRC.
I'll have to think about that.
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]