Confusing "Branch unlinked" in activity log and emails
Bug #366013 reported by
James Westby
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Medium
|
Björn Tillenius | ||
Bug Description
Hi,
Please take a look at bug 345706.
The comment by Sveinung Kvilhaugsvik (kvilhaugsvik) on 24 Apr, where
he says that he updated the branch was emailed to me as:
"""
Updated my bazaar branch containing the fix since another packagekit
0.3.14-0ubuntu5 was released and Jaunty already is out
** Branch unlinked: lp:~kvilhaugsvik/packagekit/ubuntu-packagekit
"""
indicating that he had removed the branch. I went to the bug to look and
there was a linked branch. The same action is in the activity log.
I don't know if the branch was unlinked at this point, but it is confusing
that it states it was unlinked, but doesn't have a subsequent "branch linked"
message, when there is a branch there now.
Thanks,
James
Revision history for this message
| Björn Tillenius (bjornt) wrote | #1 |
| affects: | launchpad → malone |
| Changed in malone: | |
| status: | New → Triaged |
Revision history for this message
| Björn Tillenius (bjornt) wrote | #2 |
| Changed in malone: | |
| importance: | Undecided → Medium |
| milestone: | none → 2.2.4 |
| Changed in malone: | |
| assignee: | nobody → Björn Tillenius (bjornt) |
| status: | Triaged → In Progress |
Revision history for this message
| Björn Tillenius (bjornt) wrote | #3 |
| Changed in malone: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| James Westby (james-w) wrote Re: [Bug 366013] Re: Confusing "Branch unlinked" in activity log and emails | #4 |
| Changed in malone: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
It's hard to say exactly what went wrong here, but one issue is that when the branch scanner links the branch to the bug when it find --fixes revision properties using a different API to link the branch to the bug, so it doesn't get recorded in the activity log. Let's fix the scanner so that it uses the right API; after that we can see if this happens again.