Opened 19 years ago
Closed 18 years ago
#3325 closed defect (fixed)
trac-post-commit-hook error when both re: and fixes: keywords included
| Reported by: | Owned by: | Christian Boos | |
|---|---|---|---|
| Priority: | high | Milestone: | 0.10 |
| Component: | ticket system | Version: | 0.9.5 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
When a commit message includes both the "re: " and "fixes: " on the same ticket numbers (e.g. "re: #100 fixes: #100"), the trac-post-commit-hook script fails with the following message:
Unexpected error while processing ticket ID 8: columns ticket, time, field are not unique
The script appears to be trying to insert two rows in ticket_change with the same key field values.
Attachments (0)
Change History (9)
comment:1 by , 19 years ago
| Milestone: | → 0.10 |
|---|---|
| Owner: | changed from to |
| Priority: | lowest → high |
| Severity: | trivial → normal |
| Status: | new → assigned |
comment:2 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Please try out r3486. It works fine for me.
comment:4 by , 19 years ago
No way. It contains changes that are specific to the 0.10 api/data model. However, it should be possible to downgrade it. I'll have a try.
comment:5 by , 19 years ago
No biggie if you can't, it's not a big deal to just not re: and close: in the same commit message. I'll upgrade to 0.10 when it's stable.
comment:6 by , 19 years ago
He, I guess we had a collision… I was about to say:
I ported the above fix to 0.9-stable in r3487. Can you please test it?
comment:8 by , 18 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
comment:9 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
anonymous: do not change the status of a ticket without a reason/description.
I tried to have a look at that, and I've seen that a lot of changes I've recently made have horribly broken that script…