Closed Bug 408711 Opened 17 years ago Closed 17 years ago

patch interdiff feature not working

Categories

(mozilla.org Graveyard :: Server Operations, task)

x86
Windows XP
task
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: nelson, Assigned: justdave)

References

Details

BMO's interdiff feature, by which code reviewers can compare two versions of a patch, is not working since the switch to the load balancer. Steps to reproduce: Go to any bug that has multiple patches attached, multiple versions of the same patch to the same version of the same source file. Click on the "diff" link for one of the later patch versions. Then in the page for that patch, select an earlier version of the patch and click the "diff" button. Expected result: A page showing the differences between the patches. Actual result: A page showing no differences at all, as if the patches were identical. Examples: https://bugzilla.mozilla.org/attachment.cgi?oldid=290624&action=interdiff&newid=292518&headers=1 https://bugzilla.mozilla.org/attachment.cgi?oldid=290624&action=interdiff&newid=291459&headers=1
<justdave> ===mrapp51=== <justdave> package interdiff is not installed <justdave> ===mrapp52=== <justdave> package interdiff is not installed <justdave> ===mrapp53=== <justdave> package interdiff is not installed <justdave> that'd do it
Assignee: justdave → server-ops
Component: Bugzilla: Other b.m.o Issues → Server Operations
OS: Windows XP → All
QA Contact: reed → justin
Hardware: PC → All
Blocks: 395093
Assignee: server-ops → justdave
Component: Server Operations → Bugzilla: Other b.m.o Issues
OS: All → Windows XP
Hardware: All → PC
Component: Bugzilla: Other b.m.o Issues → Server Operations
I tested all the patchreader stuff *except* for comparing too patches. Sorry about that. Installed: patchutils.i386 0:0.2.31-2.2.2 Should work now.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
s/too/two/
Thanks, Dave.
Status: RESOLVED → VERIFIED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.