[fossil-users] Bug in commandline access to ticket reports
We have 25 ticket reports. The web access to any of these reports works fine. Commandline Issues: o When listing the reports via 'fossil ticket list report', only 22 reports appear. The Report Number begins with 0, then 1, 2 through 4 are skipped, and then 5 through 25 are shown. o Some of the missing reports can be shown when given the report title in the 'fossil ticket show report title' command instead of using the report number. o The more recently created reports that don't show up in the 'list report' command aren't even accessible via the 'fossil ticket show report title' command. So there appears to be issues with Fossil's commandline access to the ticket reports when there are a lot of reports. I'm using Fossil 1.20 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Potential Bug in Version 1.18: Database Error when retrieving Raw Ticket Report
All of the following is from the perspective of a user accessing Fossil via the web interface. STEPS TO REPRODUCE ANOMALY 1) Change the date format specifier for a report Was: datetime(tkt_mtime) Is: datetime(tkt_mtime,'localtime') 2) Run the report 3) In the resulting report page, click on the Raw link at the top of the page. 4) I expect to see a non-html listing of the tickets. 5) Instead I receive: error code 23: access to config.value is prohibited Database Error access to config.value is prohibited SELECT value FROM config WHERE name='timeline-utc' If you have recently updated your fossil executable, you might need to run fossil all rebuild to bring the repository schemas up to date. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Version 1.18 Bug: 'update -n' does not work for merged files
If I want to see what files might change with an 'update', I supply the '-n' option. E.g. fossil update -n For files that have a merge conflict, the 'baseline', 'original', and 'merge' files get created on my local file system. All other files that would get updated do not get updated (the expected result with the -n option). I would expect that no changes to my file system would occur when using the '-n' option. If this is not a bug, the documentation for the 'update' command should be changed to reflect the actual behavior. Thanks, Marty Backe ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
