On Wednesday 07 March 2007 15:44 Benjamin M. wrote:
> Ph. Marek wrote, On 07/03/07 02:50:
> > Don't you have r703?
> No more problem with diff or run-tests 023 with FSVS 1.1.0.
That's good.
> Now... I have tried the sync-repos command...
...
> $ fsvs info
>
>
> An error occurred: No such file or directory (2)
> in info__work: Couldn't find a working copy with matching base.
> FSVS (licensed under the GPLv2), (C) by Ph. Marek; version trunk:677
That's ok. It could be a bit more user-friendly, though.
> $ fsvs urls file:///tmp/fsvs-test-repos/
> $ fsvs info
> No tree information available. Did you commit?
> $ fsvs sync-repos
> NmC. 0
> .mC. 0 .
> Sync-repos to revision 1.
> $ fsvs info
> .... 4096 .
> Type: directory
> URL: file:///tmp/fsvs-test-repos/
> Status: 0x0 (unmodified)
> Flags: 0x0 (none)
> Dev: 64772
> Inode: 16387
> Mode: 040775
> UID/GID: 700 (webmaster)/700 (webmaster)
> MTime: Wed Mar 7 09:16:52 2007
> CTime: Wed Mar 7 09:16:52 2007
> WAA-Path:
> /tmp/fsvs-test-waa/5a/b8/caa10538a87aff49fe6f19370d6c/
> Revision: 1
> Size: 4096
> $ fsvs st
> <returns nothing>
There you're right. It should possibly return the file.
> $ fsvs remote-status
> .m.. 4096 .
> Remote-status against revision 1.
>
> $ cat test.txt
> Hello world!
> $ svn cat file:///tmp/fsvs-test-repos/test.txt
> Hello World!
>
> I would expect test.txt to be reported as Changed... am I missing
> something?
No. AFAIK (without looking) sync-repos has a small bug, in that files *with
the same size* are not reported as changed, because their mtime is read after
syncing. (See mtime, ctime stamps above).
Bug:
$ fsvs st -C -C
should report it (doing a checksum), and
$ fsvs commit -C -C
too.
So, BTW ... why does your fsvs give no MD5 of that file?
$ fsvs info big_file
.... 588888 ./big_file
Type: file
URL: file:///tmp/ram/fsvs-test-1000/repos/trunk/big_file
Status: 0x0 (unmodified)
Flags: 0x0 (none)
Dev: 20
Inode: 16306
Mode: 0100644
UID/GID: 1000 (flip)/1000 (flip)
MTime: Wed Mar 7 19:57:53 2007
CTime: Wed Mar 7 19:57:53 2007
WAA-Path: /tmp/ram/waa/be/9b/c359b8d47483ea64ef5faa12ac2d/
Revision: 4
Repos-MD5: 9f588ff5001de34673652c4a767575e4
Size: 588888
$ echo 'Hello world!' | md5sum
59ca0efa9f5633cb0371bbc0355478d8 -
Could you please check whether fsvs really prints no MD5 for you?
Why not?
I'd like to know whether the MD5 is locally correct or not.
And now to your point - should fsvs on a sync-repos *always* check the local
files for identity? (Doing a MD5?) Would be slow. Should it do that always on
status? Probably not.
But you're right, in that it could see the differing mtime, and say "possibly
changed" - as it does with other files.
How's r726 for you?
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]
