* SUMMARY Tagging for Bugzilla-3.2.3 (and other older versions) mistakenly backed out a change in duplicates.cgi and brought these files back from the dead: duplicates.xul js/duplicates.js template/en/default/reports/duplicates.rdf.tmpl The attached patch shows which changes were mistakenly added back. * NOTES Removing version tags (like BUGZILLA-3_2_3) from the above files and retagging duplicates.cgi from v1.61 to v1.62 would fix the issue. It appears that Bugzilla 3.3.* and 3.4.* tags and branches are correct.

These versions/tags appear to be affected: $ cvs log duplicates.cgi | grep 1.61 Bugzilla_Stable: 1.61 BUGZILLA-3_2-STABLE: 1.61 BUGZILLA-3_2_3: 1.61 BUGZILLA-3_2_2: 1.61 BUGZILLA-3_2_1: 1.61 BUGZILLA-3_2: 1.61 BUGZILLA-3_2rc2: 1.61 BUGZILLA-3_2rc1: 1.61 BUGZILLA-3_2-BRANCH: 1.61.0.2 BUGZILLA-3_1_4: 1.61 BUGZILLA-3_1_3: 1.61

duplicates.xul has been removed from Bugzilla 3.4, see the target milestone. It's still available in 3.2.x, as expected.

The reason I filed this was that I thought you'd want to remove this code in a future 3.2.x update since it was originally removed in 2.20.4.

(In reply to comment #3) > The reason I filed this was that I thought you'd want to remove this code in a > future 3.2.x update since it was originally removed in 2.20.4. You completely misunderstood what the version field means. 2.20.4 was the current version of Bugzilla when I filed the bug. But in no way does it mean that it was removed in this release. This information is stored in the target milestone field, which is set to Bugzilla 3.4. So this bug is not WONTFIX, it's really INVALID.

(In reply to comment #4) > So this bug is not WONTFIX, it's really INVALID. You are correct--my bad.