[fossil-users] State of tkt-hook-change branch
What is the state of the tkt-hool-change branch? I tried using it for my own local repo and I can't get the http ticket hook to trigger. th1-uri-regexp: .* hook command is: http -asynchronous -- http://mpcjanssen.nl/cgi-bin/tkt-hook?uuid=$uuid After adding some debugging statements the hook command seems to fail with: Executing th1 common script Executing 1 th1 specific script http -asynchronous -- http://mpcjanssen.nl/cgi-bin/tkt-hook?uuid=$uuid parsing URL http://mpcjanssen.nl/cgi-bin/tkt-hook?uuid=7f4a275ec1d71597006fa063a57c166033937ca8 url must be http:// or https:// Anyone has any idea what's up? Mark ___ 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] State of tkt-hook-change branch
2013/12/13 Mark Janssen mpc.jans...@gmail.com: What is the state of the tkt-hool-change branch? I tried using it for my own local repo and I can't get the http ticket hook to trigger. Looks like an uninitialized variable. Should be fixed now. I think it's ready to be merged to trunk. Thanks! Regards, Jan Nijtmans ___ 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] State of tkt-hook-change branch
On Fri, Dec 13, 2013 at 12:29 PM, Jan Nijtmans jan.nijtm...@gmail.comwrote: 2013/12/13 Mark Janssen mpc.jans...@gmail.com: What is the state of the tkt-hool-change branch? I tried using it for my own local repo and I can't get the http ticket hook to trigger. Looks like an uninitialized variable. Should be fixed now. I think it's ready to be merged to trunk. Thanks! With the updated version [85528ef507] I still get the same error. xfer_run_script still fails with error: url must be http:// or https:// At xfer.c line 869 Maybe there is something else I am doing wrong? Regards, Mark ___ 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] State of tkt-hook-change branch
2013/12/13 Mark Janssen mpc.jans...@gmail.com: With the updated version [85528ef507] I still get the same error. xfer_run_script still fails with error: url must be http:// or https:// At xfer.c line 869 Maybe there is something else I am doing wrong? More likely that I did something wrong, like an incomplete commit. Please try again ;-) Regards, Jan Nijtmans ___ 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] State of tkt-hook-change branch
On Fri, Dec 13, 2013 at 2:15 PM, Jan Nijtmans jan.nijtm...@gmail.comwrote: 2013/12/13 Mark Janssen mpc.jans...@gmail.com: With the updated version [85528ef507] I still get the same error. xfer_run_script still fails with error: url must be http:// or https:// At xfer.c line 869 Maybe there is something else I am doing wrong? More likely that I did something wrong, like an incomplete commit. Please try again ;-) Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users Hi Jan, Two remarks: 1) I am fairly sure that: memset(urlData, '0', sizeof(urlData)); Should be memset(urlData, 0, sizeof(urlData)); 2) I think url_parse_local should be fixed to properly fill all the urlData fields instead of having to memset the structure before. Mark BTW with memset 0 it works :) ___ 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] State of tkt-hook-change branch
On Fri, Dec 13, 2013 at 3:19 PM, Jan Nijtmans jan.nijtm...@gmail.comwrote: Thanks for your feedback! One final piece of feedback, concerning the next step in the trigger process. Fossil seems to encode the trigger request as Content-Type: text/plain even in the case of a GET. Unfortunately this will lead to an error when trying to parse the request using tcllib's ncgi. ncgi only supports: - text/xml* - application/x-www-form-urlencoded* - application/x-www-urlencoded* And reading the specs it seems that a GET request should not specify a content-type at all. Mark ___ 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] State of tkt-hook-change branch
2013/12/13 Mark Janssen mpc.jans...@gmail.com: One final piece of feedback, concerning the next step in the trigger process. Fossil seems to encode the trigger request as Content-Type: text/plain even in the case of a GET. Unfortunately this will lead to an error when trying to parse the request using tcllib's ncgi. ncgi only supports: - text/xml* - application/x-www-form-urlencoded* - application/x-www-urlencoded* And reading the specs it seems that a GET request should not specify a content-type at all. Neither content-length ;-( http://fossil-scm.org/index.html/info/a60d2976ff Again, Thanks! Jan Nijtmans ___ 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] State of tkt-hook-change branch
On Fri, Dec 13, 2013 at 4:18 PM, Jan Nijtmans jan.nijtm...@gmail.comwrote: 2013/12/13 Mark Janssen mpc.jans...@gmail.com: One final piece of feedback, concerning the next step in the trigger process. Fossil seems to encode the trigger request as Content-Type: text/plain even in the case of a GET. Unfortunately this will lead to an error when trying to parse the request using tcllib's ncgi. ncgi only supports: - text/xml* - application/x-www-form-urlencoded* - application/x-www-urlencoded* And reading the specs it seems that a GET request should not specify a content-type at all. Neither content-length ;-( http://fossil-scm.org/index.html/info/a60d2976ff Again, Thanks! Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users Thanks for the quick fixes :) Everything works great now. Mark ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] ci_edit tag sorting bug?
Hello, I think I've discovered a bug with the way tags are sorted when in the ci_edit page. Basically, if the name of the tag sorts before the branch tag, then it displays an option to cancel the tag. For example, sym-blue, sym-bits, sym-black all sort before ``branch'' and so if the branch is named blue, bits, or black it brings up an option to cancel the tag. This can be seen in this query: $ sqlite3 -header new.fossil SELECT tag.tagid, tagname, tagxref.value FROM tagxref, tag WHERE tagxref.rid=23 AND tagtype0 AND tagxref.tagid=tag.tagid ORDER BY CASE WHEN tagname GLOB 'sym-*' THEN substr(tagname,5) ELSE tagname END; tagid|tagname|value 20|sym-azure| 19|sym-azzurro| 16|sym-blue| 8|branch|blue 18|sym-brie| 14|sym-brown| Notice that my branch is blue, and sym-blue sorts above it, so it doesn't get skipped in the loop: http://www.fossil-scm.org/index.html/artifact/003d21ea050649753662ed48cfabd1967857f50d?ln=2320,2323 So I think this query works better: $ sqlite3 -header new.fossil SELECT tag.tagid, tagname, tagxref.value FROM tagxref, tag WHERE tagxref.rid=23 AND tagtype0 AND tagxref.tagid=tag.tagid ORDER BY CASE WHEN tagname GLOB 'sym-*' THEN substr(tagname,5) ELSE tag.tagid END; tagid|tagname|value 8|branch|blue 20|sym-azure| 19|sym-azzurro| 16|sym-blue| 18|sym-brie| 14|sym-brown| Which brings the built-in tagids to the top and then sorts the sym-* by name. I placed it in pending-review: http://www.fossil-scm.org/index.html/info/c36ad48a87 Is there a better approach? Thanks, Andy -- TAI64 timestamp: 400052ab4ab1 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] New release supporting ssh access?
I am really looking forward to the release that includes the proper ssh remote repositories. I can build it for my environment, but I am teaching a course in January and I want the students to submit assignments using their own repositories (and encourage them to use fossil (and SCMs in general), and they use Windows and Linux, so it would be much easier if I could simply point them at the fossil-scm.org site! (If anyone's interested in the details, I'm going to set up accounts that can only run fossil, and give them each their own fossil with them, me, and the TA having access to the repository. Then they can do/submit assignments and the TA or I can mark them, leaving annotation files, mark files, etc.) I love everything I've seen about fossil, but have been waiting for this before using it in production. Thanks ../Dave ___ 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] New release supporting ssh access?
Thus said David Mason on Fri, 13 Dec 2013 13:37:40 -0500: I am really looking forward to the release that includes the proper ssh remote repositories. Will you describe what you envision is a ``proper ssh remote repository?'' The current SSH implementation in trunk does away with the dependency on the shell entirely and so allows for more flexibility with SSH. It is also possible to enforce Fossil permissions by using SSH keys to authenticate to Fossil by enabling the REMOTE_USER option on the repository. Are you looking for more than this? Thanks, Andy -- TAI64 timestamp: 400052ab5651 ___ 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] New release supporting ssh access?
On Fri, 13 Dec 2013 13:37:40 -0500 David Mason dma...@ryerson.ca wrote: I am really looking forward to the release that includes the proper ssh remote repositories. I can build it for my environment, but I am teaching a course in January and I want the students to submit assignments using their own repositories (and encourage them to use fossil (and SCMs in general), and they use Windows and Linux, so it would be much easier if I could simply point them at the fossil-scm.org site! (If anyone's interested in the details, I'm going to set up accounts that can only run fossil, and give them each their own fossil with them, me, and the TA having access to the repository. Then they can do/submit assignments and the TA or I can mark them, leaving annotation files, mark files, etc.) I love everything I've seen about fossil, but have been waiting for this before using it in production. I don't use fossil through ssh, but a sshfs may do what you want. See http://fuse.sourceforge.net/sshfs.html Don't know if works on MS-Windows. Thanks ../Dave ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users --- --- Eduardo Morras emorr...@yahoo.es ___ 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] New release supporting ssh access?
Thus said David Mason on Fri, 13 Dec 2013 13:37:40 -0500: (If anyone's interested in the details, I'm going to set up accounts that can only run fossil, and give them each their own fossil with them, me, and the TA having access to the repository. Then they can do/submit assignments and the TA or I can mark them, leaving annotation files, mark files, etc.) By the way, there is one caveat that was recently introduced that affects how a shared SSH account works. When cloning, the URL user becomes the primary fossil user in the checkout. Just out of curiosity, how do you intend on using fossil in this particular environment? Will you simply setup a fossil file that has correct Unix permissions to permit the sharing of the file between the student and TAs? Or were you planning on aggregating all the files under one user account (perhaps fossil) and then cloning the individual repositories using -A to override the local fossil user? Andy -- TAI64 timestamp: 400052ab791b ___ 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] New release supporting ssh access?
On Fri, 13 Dec 2013 13:37:40 -0500 David Mason dma...@ryerson.ca wrote: I am really looking forward to the release that includes the proper ssh remote repositories. I can build it for my environment, but I am teaching a course in January and I want the students to submit assignments using their own repositories (and encourage them to use fossil (and SCMs in general), and they use Windows and Linux, so it would be much easier if I could simply point them at the fossil-scm.org site! (If anyone's interested in the details, I'm going to set up accounts that can only run fossil, and give them each their own fossil with Since you are providing a server with Fossil repos on it, your build could work the way you want it for your students to use SSH for access using stock builds of Fossil. In the meantime, please tell us what is missing from Fossil. ___ 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] New release supporting ssh access?
On 13 December 2013 16:15, Andy Bradford amb-sendok-1389561340.dnoncohnjbcljmjie...@bradfords.org wrote: By the way, there is one caveat that was recently introduced that affects how a shared SSH account works. When cloning, the URL user becomes the primary fossil user in the checkout. I was just looking for when the code in trunk would make it to downloads for Mac/Windows/Linus. The server is running Mac OS X. Just out of curiosity, how do you intend on using fossil in this particular environment? Will you simply setup a fossil file that has correct Unix permissions to permit the sharing of the file between the student and TAs? Or were you planning on aggregating all the files under one user account (perhaps fossil) and then cloning the individual repositories using -A to override the local fossil user? The latter, one fossil account, with ssh keys triggering the fossil id - work for which I believe you can take much of the credit. Thanks to all of you working on this! ../Dave ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
