Fossil: View Ticket

2011-06-01
22:32		• Fixed ticket [5f611295e3]: Cannot update to a branch leaf (due to events tagged as the branch) plus 1 other change artifact: 73a2845ace user: drh
22:32		In contexts where only a check-out makes since, only resolve tags or branch names into check-outs, not events or other artifacts. Ticket [5f611295e3c2a8]. check-in: 2a013f0228 user: drh tags: trunk
12:29		• Ticket [5f611295e3] Cannot update to a branch leaf (due to events tagged as the branch) status still Open with 2 other changes artifact: 5e98baa3cc user: viriketo
2011-04-05
07:31		• Ticket [5f611295e3]: 1 change artifact: 15eb23793d user: viriketo
2011-02-10
21:14		• Ticket [5f611295e3]: 2 changes artifact: 7ba02bbc57 user: anonymous
2011-02-09
13:36		• New ticket [5f611295e3]. artifact: e7d5d0458b user: anonymous

Ticket Hash:	5f611295e3c2a8a900ce39e9a72ecd9aace4c59e
Title:	Cannot update to a branch leaf (due to events tagged as the branch)
Status:	Fixed	Type:	Code_Defect
Severity:		Priority:
Subsystem:		Resolution:	Fixed
Last Modified:	2011-06-01 22:32:45 14.84 years ago	Created:	2011-02-09 13:36:47 15.14 years ago
Version Found In:	[6f42e76d80] 2011-01-13

Description:

We have hit a problem where we cannot update to a branch we have. We have been using this branch for months.

$ fossil update tai
fossil: no such version: tai
$ fossil branch list |grep tai
  tai
  tai_dll

The branch has a single leaf. This command worked fine until yesterday. The latest change that may have done something is adding an event with the same tag as the branch name. We also had a double leaves yesterday late, and we changed one of the branches to "fork a new branch since this checkin" using the ui Edit button.

The current leaf says in Tags and Properties:

    * bgcolor=#c0ffc0 inherited from [e6e7a07477]
    * branch=tai inherited from [e6e7a07477]
    * sym-delivered added by [401c9ad515] on 2011-02-09 02:54:05
    * sym-tai inherited from [e6e7a07477]

Any idea? All our workstation fossil clients show the same behaviour (linux and cygwin).

anonymous claiming to be viric added on 2011-02-10 21:14:07 UTC:
I could reproduce this another time. An Event page with the same tag as the branch name triggers the problem: then 'fossil update XXX' will get the Event instead of the checkin of the leaf with the name XXX.

viriketo added on 2011-04-05 07:31:18 UTC:
This still happens with fossil version [1d93222627] 2011-03-01 19:04:32.

"fossil update branchname" will fail if there is an event tagged with 'branchname' after the branch leaf.

viriketo added on 2011-06-01 12:29:19 UTC:
Fossil [d8221b9863] 2011-05-12 still has the problem.