[fossil-users] Search for tickets
Hello All, Looking at the tickets feature of Fossil, it would be really great if there could be a way to search for tickets. I see this request here: https://www.fossil-scm.org/fossil/tktview?name=7567c8daf9 The reference to the other ticket isn't exactly clear as it looks like they want sortable columns, which works in 3753b87d94 Referenced ticket: 3753b87d94 https://www.fossil-scm.org/index.html/tktview?name=923872a184 -- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] How to import tickets into fossil
Hello: I am converting from a bulletin board system that I was using as a ticketing system (elog). Does fossil have a mechanism where I can create and update the tickets from the command line? Even some form of input format would be useful. I guess the same question is once I have tickets in fossil, is there an export mechanism of some sort in case I want to move to another system? -- -- rouilj John Rouillard === My employers don't acknowledge my existence much less my opinions. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] How to serve up static files using --files
Hello: I am having an issue trying to serve up static files like index.html with fosssil in server mode. My command line is: fossil server --files *.txt,*.html /home/rouilj/.fossil_repos there is a file: /home/rouilj/.fossil_repos/index.html but when I connect to: http://server:8081/index.html all I get is a 404 error and a page with Not Found inside h1 tags. http://server:8081/reponame works fine. I have searched high and low trying to get some logging or debugging output (including building with configure ... --fossil-debug and running the server with --debug). However I have had no luck debugging the code base to figure out what I am doing wrong. Can somebody toss a clue by 4 my way? Thanks. -- -- rouilj John Rouillard === My employers don't acknowledge my existence much less my opinions. ___ 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] Incorrect password during 'fossil config pull user url'
Thus said Michael L. Barrow on Thu, 04 Dec 2014 13:34:42 -0800: What I'm trying to do is document the process of creating a new repository that will be in the same login group of a master repo. From my understanding, you still need to have the user accounts created in the secondary repos even if they're in the same login group. I haven't played much with login groups, but in my experimentation with the web UI it seems that if you add a user in one repository, it has an option called Scope that allows you to apply it to all the repositories in the login group. If you check that option, when changing the user, it will take effect in all repositories in the group. I don't know if there is a similar Scope option when managing users from the command line, but it seems like for a login group, just using the UI will work. Is there a better best practice for doing this? I would suggest using fossil config export/import user but I think I've misused it, or found a bug. I did ``fossil config export user fossil.users'' and then used ``fossil config import fossil.users'' in another repository and all users but the 2 listed in the fossil.users file were wiped out of the target repository. The problem I see with this is that it wiped out anonymous, developer, nobody, reader and the default setup user initially created from the repository. Devs: Is this really how it should be working? Should ``fossil export user'' also export the default users? I suppose there is also ``fossil config merge fossil.users'' which won't wipe them out, but it certainly was a bit unexpected to lose all those users (thankfully a test repo). Andy -- TAI64 timestamp: 40005482744d ___ 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] How to import tickets into fossil
Thus said John P. Rouillard on Fri, 05 Dec 2014 21:38:35 -0500: Does fossil have a mechanism where I can create and update the tickets from the command line? Even some form of input format would be useful. http://www.fossil-scm.org/index.html/help?cmd=ticket I guess the same question is once I have tickets in fossil, is there an export mechanism of some sort in case I want to move to another system? I don't think there is any specific mechanism for exporting tickets (except perhaps in the above mentioned command line options). I suppose there's always the SQL mechanism if one is desperate: http://www.fossil-scm.org/index.html/help?cmd=sqlite3 Given the warning there, any tampering with the DB should probably be done on a temporary clone which is discarded when done. Andy -- TAI64 timestamp: 400054827543 ___ 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] How to import tickets into fossil
In message 20141205201648.27318.qm...@angmar.bradfordfamily.org, Andy Bradford writes: Thus said John P. Rouillard on Fri, 05 Dec 2014 21:38:35 -0500: Does fossil have a mechanism where I can create and update the tickets from the command line? Even some form of input format would be useful. http://www.fossil-scm.org/index.html/help?cmd=ticket I know about that, but I am not sure how to use it. I can create the ticket: fossil ticket add title This is ticket title private_contact someb...@emmail.com comment encode the body of the ticket\n\nusing the quioting\tmechanism\nhere we go\n tkt_ctime 2011-10-20 12:34:23 type text/plain status open -q and somehow get a UUID back (lets say 12345), but how do I update the ticket with a new comment from another user? Neither set or change seems right as it will update the fields of the ticket I just added. Ahh, is an update for the ticket just an append to the comment with a header? So after I add a ticket, I can create a new comment on it with: fossil ticket change 12345. +comment -\nuser added on 2014-03-20 12:22:12\n\nThis is an update to the same ticket\nwith two lines of text -q Or should it be: fossil ticket change 12345. tkt_mtime 2014-03-20 12:22:12 login user username A user mimetype text/plain icomment This is an update to the same ticket\nwith two lines of text -q I am not finding anything that indicates which I should do. Also do the fossil ticket change and fossil ticket set command do the same thing (so they are interchangable)? I suspect (as in my second fossil ticket change example), set changes the ticket table and change changes the ticketchng table. Also is there a way to do a file attach from the command line? I don't see any ticket attach command. I do see an /attachadd page,but I am not quite sure how to automate using that to add my attachments on tickets. I guess the same question is once I have tickets in fossil, is there an export mechanism of some sort in case I want to move to another system? I don't think there is any specific mechanism for exporting tickets (except perhaps in the above mentioned command line options). So I would need to parse out the comment or dump the db to generate something for another ticketing system. Ok, I can handle that I guess. I suppose there's always the SQL mechanism if one is desperate: http://www.fossil-scm.org/index.html/help?cmd=sqlite3 Given the warning there, any tampering with the DB should probably be done on a temporary clone which is discarded when done. Yeah, that seems possible for dumping the data, but seems dangerous for importing the tickets. Thanks for your thoughts. -- -- rouilj John Rouillard === My employers don't acknowledge my existence much less my opinions. ___ 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] How to serve up static files using --files
Thus said John P. Rouillard on Fri, 05 Dec 2014 21:52:38 -0500: I am having an issue trying to serve up static files like index.html with fosssil in server mode. My command line is: fossil server --files *.txt,*.html /home/rouilj/.fossil_repos Maybe try quoting the argument following --files: fossil server --files '*.txt,*.html' /home/rouilj/.fossil_repos http://server:8081/index.html You're sure that 8081 is the fossil server that was started with the correct --files option? I tried the --files option here locally and it worked just fine, however, it only serves files that can be matched to a MIME type via file extension (e.g. .txt, .jpg, .html, etc.), and it only works when starting fossil server with a directory as the file to serve (which you did). Also, if any portion of the filename matches '*fossil*' it won't serve them (the directory is not included, so there should be no problem with your .fossil_repos directory). Andy -- TAI64 timestamp: 40005482945f ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
