I'm not sure about why this is happenig...but this is driving me crazy. Now, after I thought we had the problems behind us. I found a file that should be on the OS (it is in subversion, but refuses to show up in a status and remote-status), but isn't. So, I "bumped" the file on the "master" system, and re-ran the "fsvs update -oconflict=remote -d" command, and got this error (only the last few lines included):
15:23:28.143 up__parse_prop[update.c:165] got property for sql: svn:entry:committed-rev=39 15:23:28.143 cb___store_prop[racallback.c:292] have name=svn:entry:committed-rev; user? 0 15:23:28.143 up__parse_prop[update.c:165] got property for sql: svn:entry:committed-date=2008-08-29T18:59:37.704186Z 15:23:28.143 cb___store_prop[racallback.c:292] have name=svn:entry:committed-date; user? 0 15:23:28.143 up__parse_prop[update.c:165] got property for sql: svn:entry:last-author=user 15:23:28.143 cb___store_prop[racallback.c:292] have name=svn:entry:last-author; user? 0 15:23:28.143 up__parse_prop[update.c:165] got property for sql: svn:entry:uuid=9b534c72-a6ac-4330-b533-75b76ca60dff 15:23:28.143 cb___store_prop[racallback.c:292] have name=svn:entry:uuid; user? 0 15:23:28.143 ops__find_entry_byname[est_ops.c:781] Searching for create_schema.sql (create_schema.sql) found no entry (ignored_too=0) 15:23:28.143 cb__add_entry[racallback.c:165] entry opt/myoffice/sql/create_schema.sql, mode 0100000; not found, may not create An error occurred at 15:23:28.187: No such file or directory (2) in cb__record_changes_mixed [racallback.c:834]: reporter->finish_report: cb___open_file 15:23:28.187 main[fsvs.c:1261] memory stats: 0x807e000 to 0x81e9000, 1452 KB I _really_ want this solution to work. It seems quite elegant and feels like the most appropriate solution for us. The problem is that I'm starting to get some push from other team members to move to other solutions. The fact is, we _can_not_ use the fsvs if it is so unpredictable. Could we have messed up something in the compile? Could we have messed up something in the repository initialization? Could we have some odd config settings that are interfeering with the running of this? At this point, I think something is wrong with our setup, since there does appear to be plenty of people that have successfully used this system. My goal is to find out what we're doing wrong/differently, and fix it. Let me know and I can send/post all of my configs, including the commands I'm using to initialize/update the system. Again, I really do appreciate all of your help (especially Phil). Thanks in advance for any thoughts you can offer. Stu On Fri, Aug 29, 2008 at 2:32 PM, Philipp Marek <[EMAIL PROTECTED]> wrote: > On Friday 29 August 2008 Stuart Lester wrote: >> A little progress (and maybe a resolution). You mentioned the >> "conflict" option in an earlier reply/post. I think that's probably >> key to resolving this...we want to set that to "remote". I don't know >> how to do that. I believe, after looking through the docs, that the >> option we need is: >> -oconflict=remote >> >> Is this correct? > Yes, for the commandline. > But you could use that in the $FSVS_CONF/config file (or the WC-specific), > too. > > > But that should just be a workaround - why are these files reported as > changed? For a directory I could understand it if files below are > added/removed - but that doesn't cause this error for me. > > > 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]
