Closed Bug 79816 Opened 24 years ago Closed 24 years ago

duplicates.cgi doesn't work with anything but db files.

Categories

(Bugzilla :: Bugzilla-General, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Bugzilla 2.14

People

(Reporter: endico, Assigned: gerv)

Details

Attachments

(3 files)

on bugzilla.mozilla.org i've found and patched several problems with duplicates.cgi. the patched version is at http://bugzilla.mozilla.org/duplicates.cgi the original version from cvs is at http://bugzilla.mozilla.org/duplicates-orig.cgi 1) the report tries to open a db file so if your installation uses some other data format you're out of luck. I hard coded in ".dbi" for our installation but that's obviously not the best solution for everyone. 2) print today's date in the error message when you can't open a db. 3) don't print bugs that are verified or closed. If a bug is so recently fixed that its not verified yet then It seems likely that there are still people using a broken build that may want to file a duplicate bug. 4) when sorting by bug number, sort in reverse order. The first 100 low numbered bugs are of virtually no interest but high numbered bugs are quite interesting.
jake points out that my diff is against an old version of duplicates.cgi. That doesn't make sense. I updated right before i made the changes. oh well.
Funky! :-) We now need to get QA to verify some of the older ones on the list, to make it more useful. I'll do a NG post at some point. And move the www.mozilla.org list over. No more work for me! ;-) I'll also integrate the new bits of changes into Bugzilla CVS at some point too. Gerv
ok, what happened is that the last time I checked out, I checked out by date so when i updated it the file it didn't sync to the tip. sigh. I think the db problem is solved on the tip but I don't think all the other problems are.
Target Milestone: --- → Bugzilla 2.16
OK, I've extracted the strikethrough part of Dawn's patch, plus a couple of other tweaks, and am attaching a new patch. Review me, please :-) Gerv
Version: Bugzilla 2.11 → Bugzilla 2.13
Keywords: patch, review
The only comment I have is that it seems like using 'eq' instead of a regular expression '=~' would be a little better when checking the $bug_status variable. The only difference I can think of would be performance, and I don't know if there's a perf difference between 'eq' and '=~'. Of course, the regular expression method is what's in use at b.m.o right now, so if you don't wanna change it, that's fine. r=jake
Fair point. Any other comments before I redo the patch? Gerv
Checked in using "eq" instead of =~. Gerv
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Target Milestone: Bugzilla 2.16 → Bugzilla 2.14
Moving to Bugzilla product
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: Bugzilla 2.13 → unspecified
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: