Defect #12973

Bazaar: Incorrect issue-to-revision relation after "uncommit"

Added by LluĂ­s Vilanova over 4 years ago. Updated almost 4 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:SCM
Target version:-
Resolution: Affected version:

Description

Redmine shows the relation of issues to revisions using bazaar's revno (revision number), but that is incorrect given that one can "uncommit", resulting in that issue being shown as relating with two revisions.

Not sure of the internal model, but Redmine should probably use Bazaar's "revno" (for showing to the user) and checking if the "revid" is valid for actual relations.

Steps to reproduce:

# create issue #N
$ hack, hack, hack
$ bzr commit -m "closes #N" 
$ bzr log --show-ids -r -1
------------------------------------------------------------
revno: X
revision-id: string1
parent: ...
committer: ...
branch nick: ...
timestamp: ...
message:
  closes #N
# check repository (so that the issue gets updated and relates to revision X)
$ bzr uncommit
$ hack, hack, hack
$ bzr commit -m "closes #N" 
$ bzr log --show-ids -r -1
------------------------------------------------------------
revno: X
revision-id: string2
parent: ...
committer: ...
branch nick: ...
timestamp: ...
message:
  closes #N
$ bzr log -r string1
# error, does not exist
$ bzr log -r string2
# same as 'bzr log -r -1'
# check repository (so that the issue gets updated and now relates to two revisions, but only revid "string2" is valid)

Related issues

Related to Redmine - Feature #2799: Support for Bazaar's shared reposetories (created with in... New 2009-02-21

History

#1 Updated by Alexander Usenko almost 4 years ago

The possible workaround is to reattach the bazaar repository (remove repository from redmine and then add it again). After than all relations with repo revisions will be rebuilded. Worked for me.

Also available in: Atom PDF