Re: [fossil-users] Using doc/ckout from win service
Od: Andy Bradford The distinction is that ckout only works with an open repository. Using Windows as a service does not use an open repository, so I wouldn't expect this to work. It might be possible for you to run the service from an open repository, but I'm not sure what the implications of this would be. I am not very clear, what specifically should I do to run service from open repository (while running fossil server args as server or the same command as service, in both cases it uses the same directory with repositories) I cant figure out where server/service distinction is made. I like to debug it but so far on Windows my attempts are failing. (I use Codelite v6 [1] as a front end with gdb) Could someone share tips for debugging fossil in Windows environment? Thanks Peter [1] http://www.codelite.org/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Using doc/ckout from win service
Hi Peter as the original author of the Windows service code, I probably can explain the behavior you are seeing. On 23.08.2014 09:13, Petr Ferdus wrote: I am not very clear, what specifically should I do to run service from open repository (while running fossil server args as server or the same command as service, in both cases it uses the same directory with repositories) I cant figure out where server/service distinction is made. You can not run a service from a open checkout, but you can create a service from a open checkout. In this case, the service is created with the repository you specified when you opened the checkout. A service is never intended to serve a open checkout! It only serves Fossil repositories. HTH -- tsbg ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Tag appears in Timeline, but not in Timeline Tags Only
In the repository at http://chiselapp.com/user/vinkix/repository/olrcix (cloneable URL) The timeline for 2014-08-20 19:29 shows a tag for RELEASE-1.6.14 In the Timeline Tags Only for this date, the tag is not shown. I have no idea why it does not show. It could be a bug in Fossil or it could be something I'm doing. Any ideas? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Tag appears in Timeline, but not in Timeline Tags Only
On Sat, Aug 23, 2014 at 9:38 AM, David Evans dave.evan...@googlemail.com wrote: In the repository at http://chiselapp.com/user/vinkix/repository/olrcix (cloneable URL) The timeline for 2014-08-20 19:29 shows a tag for RELEASE-1.6.14 In the Timeline Tags Only for this date, the tag is not shown. I have no idea why it does not show. It could be a bug in Fossil or it could be something I'm doing. The Timeline Tags Only shows only changes to tags, as when you apply a tag to a check-in after the fact. But RELEASE-1.6.14 was not changed after-the-fact. It has always been a part of the check-in. (You apparently created it with the --tag option when you did fossil commit.) So there have been no changes to the RELEASE-1.6.14 tag so it does not show up on the Tags Only timeline. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Using doc/ckout from win service
Thomas Schnurrenberger A service is never intended to serve a open checkout! It only serves Fossil repositories. Thank you for clarification. I have misunderstood doc/ckout purpose. Setting repository as a directory together with --files parameter suits my needs better. Anyone succeeded with simple directory browser which could be used to check on files on filesystem outside repositories? Thanks Peter ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Versionable settings question
In the admin settings page it reads: Settings marked with (v) are 'versionable' and will be overridden by the contents of files named .fossil-settings/PROPERTY. If such a file is present, the corresponding field above is not editable. It seems that the fields are only uneditable if you use fossil ui or fossil server (or some way of browsing from an open checkout) but not for a CGI session. It makes sense that it works this way because it is relatively easy for fossil to look at the file system of the open checkout to detect if there is a versionable setting and modifying the generated html appropriately, but is probably far more difficult to look into the repository to see if those files exist (and if they do, do they exist for the current trunk, or tip, or whatever). Perhaps impossible is a better word, since the versionable settings have to exist in a given commit, and being versionable you would what whatever current commit is open to be the versions of the settings in use. Since a CGI session is using a specific repo, not an open checkout. Okay, sorry for the rambling. I was thinking of using the versionable settings as a way to avoid pulling configuration settings from the master to my remote repositories, but now this is seeming like a less than perfect option, because the CGI of the master can't see the same settings information that my open checkouts see. Am I missing something? Is it possible for the CGI to see the versionable settings, or am I correct in my reasoning as to why? -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
