Yes, I overwrite the "fossil" file, I do not sync it.
I somehow just thought that this could cause problems.

However, there are a few
reasons, which made me try it this way:
It is really circular to boot the computer, connect
it to the network, start the fossil server just for doing
a sync (Then turning it of again...).

The next thing is, I maintain more than 5 projects
with fossil now.
There are two ways to sync them. The first one
is to write a script which holds a list of available fossils
and syncs all of them, or you type the sync command
5 times (and then you forgot one).
With my approach, I was able to put all
fossils into a dir and ftpget them, but that did not
solve my network boot up problem.

So I tried it with a thumb drive and exchanged
the fossil files between the two computers with it.

I think I use your method now.

Is it also possible to sync between two local fossil
databases, without a network connection?

I also noticed that fossil generates a unique project-id
and a unique server-id for each newly generated
fossil file. It would be great have a command which
regenerates this ids. So one could simply
copy a original fossil and regenerate it's ids,
initial username and generate a new random password.
Additionally, this command should have a option
to set all the ids and passwords entries to empty values.
This newly prepared fossil is then saved as a copy.
Fossil then generates ids and sets random passwords
on the next time the prepared fossil is opened.

This is usefull for people who want to upload the fossil
file itselve, to a public webspace for example.

Greetings, Louis

Am 16.02.2011 16:54, schrieb Williams, Brian:
> I have a question for you:
> When you say you "copy" the repo, are you file coping or doing a fossil
> clone?
> Again, when you say you "overwrite" the repo on Computer 1, are
> overwriting the file or doing a sync?
>
> If you are really overwriting the repositories then I can well expect
> that there are problems.
>
> I have a similar setup, but I maintain a fossil repo on a thumb drive;
> when I get home, I do a sync with the repo on my home machine and I'm up
> to date. I update the workspace and I'm ready to work.
>
> Fossil is an extremely powerful and flexible tool, but it does have a
> few rules; one of those is to associate a check out with one (and only
> one) repository.
>
> -----Original Message-----
> From: fossil-users-boun...@lists.fossil-scm.org
> [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Louis
> Hoefler
> Sent: Wednesday, February 16, 2011 9:19 AM
> To: fossil-users@lists.fossil-scm.org
> Subject: [fossil-users] Fossil file deletion
>
> Following szenario:
>
> I have two computers.
>
> On computer 1, I create a fossil with some work.
>
> Now I commit my work and copy the fossil to computer 2.
> I rename files on computer 2, do some other work, and commit.
>
> I make some filechanges on computer 1, and commit.
> Now I have two fossils who are out of sync.
>
> I come back home and overwrite the fossil from computer
> 1 with the one from computer 2 (where I renamed files).
>
> Now, after I do a fossil update, the (modified) files
> on computer 1 are deleted and fossil stops the update
> process, becouse it can not find the newly renamed files.
>
> I do not really understand the logic behind this error but,
> if this isnt the case: Files should be deleted only,
> if they have not changed (in case of a rename they should
> not be deleted if the last known version in fossil differs
> from the current file on disk).
>
> Greetings, Louis
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to