Hi all,
Yesterday I stumbled on what I think is a bug (albeit a minor one, since
there's a fairly easy workaround).
It would seem that "config pull ticket" doesn't apply the changes in the
definition of the ticket table.
Steps to reproduce
------------------
On a remote repository, I changed the definition of the ticket table
using the web interface:
- added a field, and applied the changes.
- changed the ticket view and edit pages to include the new field.
- altered an existing report to include the new field.
- Tested by creating a new ticket, and editing an existing one. In both
cases, it shows up fine in the report.
Then, on my local repo:
- (cli) fossil config pull ticket
- (web) tried to edit a ticket => error: 'unknown field'
- (web) tried to view the list of tickets => error: 'unknown field'
Workaround
----------
- (web) admin/ticket/table page
- click on 'Apply Changes'
- then editing a ticket or viewing a report works
From what I can see, clicking 'Apply Changes'[1] on the ticket table
page, causes fossil to call [ticket_schema_check] and then
[ticket_rebuild]. "configuration pull/sync ticket" should probably do
that as well, if a ticket-table has been received.
[1]:
http://fossil-scm.org/index.html/artifact/a63d053af5cc76ef22b8f8018a36dcef35033420?ln=169-170
[ticket_schema_check]:
http://fossil-scm.org/index.html/artifact/583b882efd0979b42e0bd73de3f9aa19e1851677?ln=627
[ticket_rebuild]:
http://fossil-scm.org/index.html/artifact/583b882efd0979b42e0bd73de3f9aa19e1851677?ln=276
Unfortunately, my C skills aren't quite sufficient to provide a patch. :-\
--
Martijn Coppoolse
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
