bzr-tfs sometimes 'loses' TFS commits
Bug #619551 reported by
John C Barstow
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Team Foundation Server support for Bazaar |
Confirmed
|
High
|
Unassigned | ||
Bug Description
There appears to be a scenario where TFS commits end up in the repository but not in the branch. I'm not sure what causes this; the net effect is that commits appear to be lost (because the pull command just compares the repositories, not the branches?)
Further investigation is warranted. In particular I suspect some uncaught exception during the bzr pull.
Missing revisions can be listed with 'bzr heads --dead'.
If the missing revision can be placed at the branch head you can fix it with 'bzr pull -r revid:$revision .' (Important: you need to pull from the current directory!), where $revision is the revid from the bzr heads output.
| Changed in bzr-tfs: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| Changed in bzr-tfs: | |
| milestone: | none → 0.3 |
| Changed in bzr-tfs: | |
| milestone: | 0.3 → 0.4 |
Revision history for this message
| John C Barstow (jbowtie) wrote | #1 |
| Changed in bzr-tfs: | |
| status: | Confirmed → Fix Released |
Revision history for this message
| John C Barstow (jbowtie) wrote | #2 |
| Changed in bzr-tfs: | |
| status: | Fix Released → Confirmed |
| description: | updated |
To post a comment you must log in.
This has not been reported since the release of 0.3; I believe the underlying bug has been fixed.