I did upgrade them all to 2.3, but I didn’t do rebuild.  Do I need to do that?

> On Aug 15, 2017, at 11:46 AM, Stephan Beal <sgb...@googlemail.com> wrote:
> 
> 1) no.
> 
> 2) make sure all of your systems have been upgraded to compatible versions 
> (v2) and that you run "fossil rebuild" on each after upgrading. That might 
> not solve what you're seeing, but it's a good place to start.
> 
> ----- stephan
> Sent from a mobile device, possibly from bed. Please excuse brevity, typos, 
> and top-posting.
> 
> On Aug 15, 2017 19:41, "Steve Schow" <st...@bstage.com 
> <mailto:st...@bstage.com>> wrote:
> Its been a while since I used Fossil, getting back to it, and have two quick 
> easy questions.
> 
> 1 - Is there any way to embed a substitution parameter into a source file 
> that Fossil can replace with version info at time of checkin?  (similar to 
> RCS).
> 
> 2 - I previous setup my fossil system with 4 machines, one machine running as 
> web server to handle ticketing and wiki as well as me kind of the master 
> repository.  Then the other 3 machines sync off that machine.  So I have 3 
> backups.  Fine so far.  It was working great last year.  Today I tried to 
> check something in to the master repository, but even after going to one of 
> the others and running fossil sync, the change doesn’t show up there…am I 
> forgetting something?
> 
> thanks
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org <mailto:fossil-users@lists.fossil-scm.org>
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users 
> <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