[fossil-users] SunOS 5.1 build?
Hi folks, A request for those who are configure / make wizards: could someone provide me with a build of fossil from SunOS / sparcv9? Specifically 5.1. I don't have ssh access to the server, so I can't compile it myself. At least, I don't know enough about compiling to do so myself on my cygwin install. Does someone have a fairly recent build handy that they could send my way? Thanks, Tomek ___ 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] Setting up a private repo online
That's what I figured. Thanks Richard! On Thu, Aug 11, 2011 at 9:31 PM, Richard Hipp wrote: > > > On Thu, Aug 11, 2011 at 9:15 PM, Tomek Kott wrote: > >> Hi fossil experts: >> >> If I get rid of all permissions from "nobody" and all the other default >> users, am I safe putting up a repository online that I would like to keep >> private? Assuming, of course, that I put the fossil repos in a folder that >> is not accessible publicly, but accessible to the cgi-bin process? >> >> I am testing this out at the moment through a new repo, and *I* can't >> find a way in, but that doesn't mean it's not possible :) >> > > It is *intended* to be secure. I sure hope it is, since I have a lot of > private repos out there. > > You need to disable all capabilities for both "nobody" and "anonymous" in > order to lock it down. I normally set up appropriate capabilities for > "reader" and "developer" and then when simply make authorized users either a > reader or a developer. > > >> >> Thanks, >> >> Tomek >> >> ___ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> >> > > > -- > 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 > > ___ 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] Setting up a private repo online
On Thu, Aug 11, 2011 at 9:15 PM, Tomek Kott wrote: > Hi fossil experts: > > If I get rid of all permissions from "nobody" and all the other default > users, am I safe putting up a repository online that I would like to keep > private? Assuming, of course, that I put the fossil repos in a folder that > is not accessible publicly, but accessible to the cgi-bin process? > > I am testing this out at the moment through a new repo, and *I* can't find > a way in, but that doesn't mean it's not possible :) > It is *intended* to be secure. I sure hope it is, since I have a lot of private repos out there. You need to disable all capabilities for both "nobody" and "anonymous" in order to lock it down. I normally set up appropriate capabilities for "reader" and "developer" and then when simply make authorized users either a reader or a developer. > > Thanks, > > Tomek > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- 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
[fossil-users] Setting up a private repo online
Hi fossil experts: If I get rid of all permissions from "nobody" and all the other default users, am I safe putting up a repository online that I would like to keep private? Assuming, of course, that I put the fossil repos in a folder that is not accessible publicly, but accessible to the cgi-bin process? I am testing this out at the moment through a new repo, and *I* can't find a way in, but that doesn't mean it's not possible :) Thanks, Tomek ___ 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] Bug: errant operations don't cause exit(EXIT_FAILURE).
On 08/11/11 17:39, Richard Hipp wrote: > There are 47 people on this list who have the appropriate credentials to > write a ticket and/or make changes to the code. All you have to do is > convince 1 out of those 47 people that the problem is worth their time > and effort. > > Or, failing that, you can fill out and send in a Copyright Release > (http://www.fossil-scm.org/fossil/doc/trunk/www/copyright-release.html) > and then you can become the 48th person with the credentials to write > tickets and otherwise make changes, and then take care of the problem > yourself. > > Yes, this all ought to be documented. Once again, all you have to do is > convince somebody that doing so is worth their time and effort. Or you > can send in a CLA and get the credentials to do it yourself. Alright. I'll read the CLA carefully, try to become #48, take care of the problem myself if it hasn't been until then, and go ahead and document the procedure. Thanks, -Martin ___ 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] Bug: errant operations don't cause exit(EXIT_FAILURE).
On Thu, Aug 11, 2011 at 5:25 PM, Martin S. Weber wrote: > On 08/09/11 15:14, Martin S. Weber wrote: > > I stumbled over this while I had a network outage... > > ...so what's the new workflow now that I as anonymous cannot create a > ticket > to capture that problem. Will I get an ACK on this list? Will a ticket be > silently created by someone? Will there be a followup on this list once a > problem-solving commit (or the decision "it's not a bug, it's a feature") > happened? This ought to be documented, IMO... > There are 47 people on this list who have the appropriate credentials to write a ticket and/or make changes to the code. All you have to do is convince 1 out of those 47 people that the problem is worth their time and effort. Or, failing that, you can fill out and send in a Copyright Release ( http://www.fossil-scm.org/fossil/doc/trunk/www/copyright-release.html) and then you can become the 48th person with the credentials to write tickets and otherwise make changes, and then take care of the problem yourself. Yes, this all ought to be documented. Once again, all you have to do is convince somebody that doing so is worth their time and effort. Or you can send in a CLA and get the credentials to do it yourself. > > Regards, > > -Martin > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- 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] Creating repositories remotely
On Thu, 11 Aug 2011 14:20:34 -0700, you wrote: >On Thu, Aug 11, 2011 at 2:03 PM, Stephan Beal wrote: > >> There is no built-in way to create a remote repository (a fossil server >> represents the _one_ repository which must already exist before the server >> can start). You have to create the .fsl file, run fossil ui once to set the >> admin password, upload it to the server, and either run it (if you're >> running it as a server) or set up a CGI script wrapper to run it (for CGI >> use). >> > >How much damage would setting up one .fsl file, and then copying it multiple >times - once for each new repository - cause? If that worked, you could wrap >a script around scp (or pscp on Windows) to make a "create remote >repository" command. Although it would work, every clone would have the same project-id, which might create confusion when multiple repositories are online. > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Bug: errant operations don't cause exit(EXIT_FAILURE).
On 08/09/11 15:14, Martin S. Weber wrote: > I stumbled over this while I had a network outage... ...so what's the new workflow now that I as anonymous cannot create a ticket to capture that problem. Will I get an ACK on this list? Will a ticket be silently created by someone? Will there be a followup on this list once a problem-solving commit (or the decision "it's not a bug, it's a feature") happened? This ought to be documented, IMO... Regards, -Martin ___ 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] Creating repositories remotely
On Thu, Aug 11, 2011 at 5:21 PM, Richard Hipp wrote: > > > On Thu, Aug 11, 2011 at 4:53 PM, lists wrote: > >> I'm a new user of fossil, having come grudgingly from CVS. Needless to >> say, my stubbornness was unfounded-life is immeasurably easier than it was >> on CVS for hundreds of little (and big) reasons. >> >> In trying to convert my workflow to fossil, I haven't been able to find >> any information in the wiki nor mail archives about creating a new >> repository, remotely, on the fossil server. > > > For a server you need two things: (1) The repository database file (the > *.fossil file) and (2) some mechanism to serve that file. > > Item (2) can be either CGI, or inetd/xinetd, or "fossil server". See the > documentation for details. In any of these cases you have to give it the > name of a repository database file to serve. > > But here is a cool feature: The name of the repo database file you give to > Fossil for (2) can actually be a directory rather than an individual file. > In that case, Fossil will serve all repos underneath that directory. > An amplification: In order for this to work, the repository files need to be named with a ".fossil" suffix. Other suffixes like ".fsl" or ".f" or anything else. If you are dealing with individual repositories, the suffix does not matter - it can be anything you want. But for this one server-every-file-in-a-subdirectory feature, all the repositories files have to end with ".fossil". > > Suppose you have (2) set up to serve files out of the /home/www/repos > directory on your server. Then in order to create a new repository on the > server you can do this: > > (a) Create the repository locally using "fossil init repo-name.fossil" > (b) Do whatever check-ins and configuration you want on the new repository, > including setting the administrator password. > (c) Test your setup locally using "fossil ui" > (d) Scp or ftp the repository file into the /home/www/repos directory on > the server. > > If you upload a repo file named /home/www/repos/abc.fossil" then you can > access it using http://domain/abc. If you upload the file to > /home/www/repos/dir1/dir2/xyz.fossil, then you access it using > http://domain/dir1/dir2/xyz. And so forth. > > So once you get (1) up and going, installing a new repository is just a > matter of uploading a new repository file. > > > >> I understand that in a large project and a tightly controlled server this >> may be undesirable, but in a home or small office environment, this is very >> useful without having to resort to log on to the server, issue the "fossil >> new " command and logging off, especially if you wish to restrict >> general log-in access to the server itself. >> >> One use for this is when creating static web sites; a new project comes >> along and whichever developer starts work on the project first simply >> creates the repository and commences work. Everyone else merely carries on >> as normal; "fossil clone " and "fossil open ", etc. >> >> Am I missing something, or is this simply not a feature that exists yet? >> >> Sacha >> ___ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> > > > > -- > D. Richard Hipp > d...@sqlite.org > -- 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] Creating repositories remotely
On Thu, Aug 11, 2011 at 11:15 PM, Sacha El Masry wrote: > Are there any plans to increase the breadth of the ui to manage multiple > repositories, including listing available repositories already on the > server > (.fsl/.fossil), creating new ones and possibly deleting existing ones, > given high enough privileges, of course? > Personally, i would say that that falls comfortably in the realm of "3rd party application." Remember that fossil tries to be cross-platform, and anything dealing with permissions or execution of external commands (e.g. scp) likely requires OS-specific handling (i.e. more complexity and more places for platform-specific bugs). -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ 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] Creating repositories remotely
On Thu, Aug 11, 2011 at 4:53 PM, lists wrote: > I'm a new user of fossil, having come grudgingly from CVS. Needless to say, > my stubbornness was unfounded-life is immeasurably easier than it was on CVS > for hundreds of little (and big) reasons. > > In trying to convert my workflow to fossil, I haven't been able to find any > information in the wiki nor mail archives about creating a new repository, > remotely, on the fossil server. For a server you need two things: (1) The repository database file (the *.fossil file) and (2) some mechanism to serve that file. Item (2) can be either CGI, or inetd/xinetd, or "fossil server". See the documentation for details. In any of these cases you have to give it the name of a repository database file to serve. But here is a cool feature: The name of the repo database file you give to Fossil for (2) can actually be a directory rather than an individual file. In that case, Fossil will serve all repos underneath that directory. Suppose you have (2) set up to serve files out of the /home/www/repos directory on your server. Then in order to create a new repository on the server you can do this: (a) Create the repository locally using "fossil init repo-name.fossil" (b) Do whatever check-ins and configuration you want on the new repository, including setting the administrator password. (c) Test your setup locally using "fossil ui" (d) Scp or ftp the repository file into the /home/www/repos directory on the server. If you upload a repo file named /home/www/repos/abc.fossil" then you can access it using http://domain/abc. If you upload the file to /home/www/repos/dir1/dir2/xyz.fossil, then you access it using http://domain/dir1/dir2/xyz. And so forth. So once you get (1) up and going, installing a new repository is just a matter of uploading a new repository file. > I understand that in a large project and a tightly controlled server this > may be undesirable, but in a home or small office environment, this is very > useful without having to resort to log on to the server, issue the "fossil > new " command and logging off, especially if you wish to restrict > general log-in access to the server itself. > > One use for this is when creating static web sites; a new project comes > along and whichever developer starts work on the project first simply > creates the repository and commences work. Everyone else merely carries on > as normal; "fossil clone " and "fossil open ", etc. > > Am I missing something, or is this simply not a feature that exists yet? > > Sacha > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- 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] Creating repositories remotely
On Thu, Aug 11, 2011 at 2:03 PM, Stephan Beal wrote: > There is no built-in way to create a remote repository (a fossil server > represents the _one_ repository which must already exist before the server > can start). You have to create the .fsl file, run fossil ui once to set the > admin password, upload it to the server, and either run it (if you're > running it as a server) or set up a CGI script wrapper to run it (for CGI > use). > How much damage would setting up one .fsl file, and then copying it multiple times - once for each new repository - cause? If that worked, you could wrap a script around scp (or pscp on Windows) to make a "create remote repository" command. ___ 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] Creating repositories remotely
On Thu, Aug 11, 2011 at 11:03:10PM +0200, Stephan Beal wrote: > On Thu, Aug 11, 2011 at 10:53 PM, lists wrote: > > > In trying to convert my workflow to fossil, I haven't been able to find any > > information in the wiki nor mail archives about creating a new repository, > > remotely, on the fossil server. I understand that in a large project and a > > tightly controlled server this may be undesirable, but in a home or small > > office environment, this is very useful without having to resort to log on > > to the server, issue the "fossil new " command and logging off, > > especially if you wish to restrict general log-in access to the server > > itself. > > > > There is no built-in way to create a remote repository (a fossil server > represents the _one_ repository which must already exist before the server > can start). You have to create the .fsl file, run fossil ui once to set the > admin password, upload it to the server, and either run it (if you're > running it as a server) or set up a CGI script wrapper to run it (for CGI > use). This is a pity, as it just increases the number of steps in creating a new repository. Are there any plans to increase the breadth of the ui to manage multiple repositories, including listing available repositories already on the server (.fsl/.fossil), creating new ones and possibly deleting existing ones, given high enough privileges, of course? Thanks, Sacha ___ 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] Creating repositories remotely
On Thu, Aug 11, 2011 at 10:53 PM, lists wrote: > In trying to convert my workflow to fossil, I haven't been able to find any > information in the wiki nor mail archives about creating a new repository, > remotely, on the fossil server. I understand that in a large project and a > tightly controlled server this may be undesirable, but in a home or small > office environment, this is very useful without having to resort to log on > to the server, issue the "fossil new " command and logging off, > especially if you wish to restrict general log-in access to the server > itself. > There is no built-in way to create a remote repository (a fossil server represents the _one_ repository which must already exist before the server can start). You have to create the .fsl file, run fossil ui once to set the admin password, upload it to the server, and either run it (if you're running it as a server) or set up a CGI script wrapper to run it (for CGI use). -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Creating repositories remotely
I'm a new user of fossil, having come grudgingly from CVS. Needless to say, my stubbornness was unfounded-life is immeasurably easier than it was on CVS for hundreds of little (and big) reasons. In trying to convert my workflow to fossil, I haven't been able to find any information in the wiki nor mail archives about creating a new repository, remotely, on the fossil server. I understand that in a large project and a tightly controlled server this may be undesirable, but in a home or small office environment, this is very useful without having to resort to log on to the server, issue the "fossil new " command and logging off, especially if you wish to restrict general log-in access to the server itself. One use for this is when creating static web sites; a new project comes along and whichever developer starts work on the project first simply creates the repository and commences work. Everyone else merely carries on as normal; "fossil clone " and "fossil open ", etc. Am I missing something, or is this simply not a feature that exists yet? Sacha ___ 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] question
On Thu, Jul 21, 2011 at 4:23 AM, Rene wrote: > On Wed, 20 Jul 2011 20:10:45 -0400, Richard Hipp wrote: > > On Wed, Jul 20, 2011 at 5:15 PM, Zhang, Jenny wrote: > > > >> HI, > >> > >> > >> > >> I WOULD LIKE TO KNOW IF FOSSIL CAN HANDEL VERSION CONTROL FOR > >> BINARY FILES? > > > > Yes. For example I store all of my presentation slides (odp files > > generated by open office) in a Fossil repository. There are also > > some binary files in the Fossil's self-hosting repository. For > > example, the Fossil logo (a gif image) is stored in the repo: > > http://www.fossil-scm.org/fossil/artifact/0fa38d60655 [3] > OK it stores binary files. does it make deltas of the versions or > is every binary file just stored as is? > Here's the page on Fossil's delta format: http://www.fossil-scm.org/index.html/doc/trunk/www/delta_format.wiki It looks similar to xdelta. Bill ___ 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] Maybe a bug in sync
Justin, Sorry, I completely forgot that I'm actually using the fossil version included from the SharpFossil project. You can download the version I'm using here: http://repository.mobile-developers.de/cgi-bin/ikoch/sharpfossil/wiki?name=Downloads. However, I went and downloaded the version you are using, and tried the same commands, including using %COMPUTERNAME% and %USERNAME% as the parameters. Everything works for me as would be expected. Really the point at which it is failing seems to be the autosync portion, since it is not pushing and artifacts over, which indicates that the client1.txt is not being sent over. I tried this on a computer at work that has XP Pro SP3 installed, and everything worked. So, I would still recommend running all the same commands by hand with the version you can run. That way we can remove the batch file itself as the culprit. I would imagine that this is a firewall issue of some sort with XP. I don't know what might be the problem, but it doesn't seem to be a problem with fossil as far as I can tell. It works fine on my Win 7 and XP machines as expected. Tomek 2011/8/11 Yujianbin > Indeed, I use my Windows PC as server and client. > My %COMPUTERNAME% is Y00122496. My %USERNAME% is y00122496. > Y00122496 haven't been defined as 127.0.0.1 in hosts. Y00122496 is the > localhost and needn't to be defined. > The server repo is in D:\server. The client repo is in D:\client. I guess > they can run independently. > And I use CMD.exe as my shell to run the scripts, not BY HAND. > > > http://www.fossil-scm.org/download.html hasn't offer fossil V1.19. > The foot of page http://www.fossil-scm.org/schimpf-book/index shows: > Fossil version 1.19 [abe7b8335f] 2011-08-02 18:42:14 > So I download the Zip archive from > http://www.fossil-scm.org/index.html/info/abe7b8335f > But I encounter fail on build it via VC++ 6.0: > > > I'm in doubt whether the version of VC++ is correct. > I can't find this info in > http://fossil-scm.org/index.html/doc/trunk/www/build.wiki: > I encounter fail on build it via VC++ 6.0: > There is a trivial defect: two "c:\msc\extra\include" of '-I' > > >cl -c -nologo -MT -O2 -I. -I..\src -I..\win\include > -Ic:\msc\extra\include -Ic:\msc\extra\ > include /Fo.\blob.obj -c blob_.c > blob_.cblob_.c(22) : fatal error C1083: Cannot open include file: 'zlib.h': > No such file or directory > NMAKE : fatal error U1077: 'cl' : return code '0x2' > Stop. > > > Follow the instruction on > http://www.sqlite.org/debug1/wiki?name=compillingOnWindows > I should download some software packages. I need more time to do it. > > > Best regards. > Justin Yu > > > > Re: [fossil-users] Maybe a bug in sync > Tomek Kott [tkott.s...@gmail.com] > 2011-08-10 (星期三) 22:42 > > Without using the batch files, I've done everything you have by hand using > fossil 1.19 2011 07 22. When I go back to the server, and write fossil open > ops, I correctly get the client1.txt file on the server side. Therefore, it > is either a windows XP vs. 7 issue, or a fossil vs. 1.18 vs 1.19 issue. > > Please update to 1.19 and try the same script. > > One other possibility is that there is something related to the shell you > are using. Are you running this on powershell or the cmd.exe? > > Two other confusing pieces to note: > D:\client>fossil commit --comment client1 > You can see: The first ‘Autosync’ will poll repo from server. > Autosync: http://y00122496@y00122496:8080 >Bytes Cards Artifacts Deltas > Sent: 130 1 0 0 > Received: 170 4 0 0 > Total network traffic: 321 bytes sent, 345 bytes received > New_Version: 11de786c5c9d689c798399f2c37d98f5b5602c89 > You can see: The second ‘Autosync’ will push repo to server. > Autosync: http://y00122496@y00122496:8080 >Bytes Cards Artifacts Deltas > Sent: 539 9 0 0 > Received: 264 6 0 0 > Total network traffic: 459 bytes sent, 397 bytes received > > First, you can notice that on the push, no artifacts are sent. On my tests, > there are two artifacts sent (I imagine it is the manifest and the file). > Therefore, it is not surprising that the server never shows the client file. > > Second, I assume that you have y00122496 defined as 127.0.0.1 in your hosts > file somewhere, since you can successfully clone from it. > > Same question as last time though: have you tried these same commands BY > HAND to ensure
Re: [fossil-users] [d8221b9863] Remove deleted file from repo?
On Wed, 10 Aug 2011 18:13:35 +0400, Konstantin Khomoutov wrote: >Apparently, you're confusing files present in a checkout and *modified* >files present in a checkout. Thanks for the clarification. I'll go through the wiki + PDF for more infos. ___ 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] Maybe a bug in sync
Indeed, I use my Windows PC as server and client. My %COMPUTERNAME% is Y00122496. My %USERNAME% is y00122496. Y00122496 haven't been defined as 127.0.0.1 in hosts. Y00122496 is the localhost and needn't to be defined. The server repo is in D:\server. The client repo is in D:\client. I guess they can run independently. And I use CMD.exe as my shell to run the scripts, not BY HAND. http://www.fossil-scm.org/download.html hasn't offer fossil V1.19. The foot of page http://www.fossil-scm.org/schimpf-book/index shows: Fossil version 1.19 [abe7b8335f] 2011-08-02 18:42:14 So I download the Zip archive from http://www.fossil-scm.org/index.html/info/abe7b8335f But I encounter fail on build it via VC++ 6.0: I'm in doubt whether the version of VC++ is correct. I can't find this info in http://fossil-scm.org/index.html/doc/trunk/www/build.wiki: I encounter fail on build it via VC++ 6.0: There is a trivial defect: two "c:\msc\extra\include" of '-I' cl -c -nologo -MT -O2 -I. -I..\src -I..\win\include -Ic:\msc\extra\include -Ic:\msc\extra\ include /Fo.\blob.obj -c blob_.c blob_.cblob_.c(22) : fatal error C1083: Cannot open include file: 'zlib.h': No such file or directory NMAKE : fatal error U1077: 'cl' : return code '0x2' Stop. Follow the instruction on http://www.sqlite.org/debug1/wiki?name=compillingOnWindows I should download some software packages. I need more time to do it. Best regards. Justin Yu Re: [fossil-users] Maybe a bug in sync Tomek Kott [tkott.s...@gmail.com] 2011-08-10 (星期三) 22:42 Without using the batch files, I've done everything you have by hand using fossil 1.19 2011 07 22. When I go back to the server, and write fossil open ops, I correctly get the client1.txt file on the server side. Therefore, it is either a windows XP vs. 7 issue, or a fossil vs. 1.18 vs 1.19 issue. Please update to 1.19 and try the same script. One other possibility is that there is something related to the shell you are using. Are you running this on powershell or the cmd.exe? Two other confusing pieces to note: D:\client>fossil commit --comment client1 You can see: The first ‘Autosync’ will poll repo from server. Autosync: http://y00122496@y00122496:8080 Bytes Cards Artifacts Deltas Sent: 130 1 0 0 Received: 170 4 0 0 Total network traffic: 321 bytes sent, 345 bytes received New_Version: 11de786c5c9d689c798399f2c37d98f5b5602c89 You can see: The second ‘Autosync’ will push repo to server. Autosync: http://y00122496@y00122496:8080 Bytes Cards Artifacts Deltas Sent: 539 9 0 0 Received: 264 6 0 0 Total network traffic: 459 bytes sent, 397 bytes received First, you can notice that on the push, no artifacts are sent. On my tests, there are two artifacts sent (I imagine it is the manifest and the file). Therefore, it is not surprising that the server never shows the client file. Second, I assume that you have y00122496 defined as 127.0.0.1 in your hosts file somewhere, since you can successfully clone from it. Same question as last time though: have you tried these same commands BY HAND to ensure that the batch file itself isn't the problem? Tomek ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
