Hi, I've merged a few bugs (275949, 382871, 429270, 435562, 443119, 454063, 474690, 544824, 563712 and 572009), making 572009 (the most recent one) the master bug. I was expecting it to be the one displayed in the bug listing, but it isn't. Instead, the oldest bug seems to be the one displayed (275949). I think it would make more sense to display the master bug and not another one when repeatmerged is set to no. Cheers, Emilio
tag 572033 wontfix thanks There is no "master bug" in a set of merged bugs. The bug which is displayed when you have repeatmerged off is always the bug with the lowest number. [In all but unusual cases, that's the right bug, and in those unusual cases, you should fix up the oldest bug anyway.] Don Armstrong
Then I guess http://www.debian.org/Bugs/server-control#forcemerge needs to be fixed: "Forcibly merges two or more bug reports. The first bug listed is the master bug, ..." Cheers, Emilio
You've elided the part which actually explains what "master bug" means in that context: "The first bug listed is the master bug, and its settings (the settings which must be equal in a normal merge) are assigned to the bugs listed next." Since it appears to be confusing, I'll adjust the wording. Don Armstrong