After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 656491 - Meld shows wrong diff in some situations
Meld shows wrong diff in some situations
Status: RESOLVED DUPLICATE of bug 652996
Product: meld
Classification: Other
Component: filediff
1.5.x
Other Linux
: Normal major
: ---
Assigned To: meld-maint
meld-maint
Depends on:
Blocks:
 
 
Reported: 2011-08-14 00:46 UTC by nh2
Modified: 2011-08-14 02:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
meld l.bad r.bad (25.98 KB, text/plain)
2011-08-14 00:47 UTC, nh2
Details
meld l.bad r.bad (2) (25.84 KB, application/octet-stream)
2011-08-14 00:48 UTC, nh2
Details
meld l.good r.good (25.78 KB, application/octet-stream)
2011-08-14 00:48 UTC, nh2
Details
meld l.good r.good (2) (25.71 KB, application/octet-stream)
2011-08-14 00:49 UTC, nh2
Details

Description nh2 2011-08-14 00:46:59 UTC
I just came across the following weird bug:

Meld just shows a line as added on one side which was actually not added while the line that was added is not shown as added (see meld l.bad r.bad, change number 2).

Cutting off a bit on both files makes it work (see meld l.good r.good, change number 1).

I guess there is some error in the offset calculation after change 1 so that following changes are wrong.

Note that diff, tkdiff and compare handle this correctly.
Comment 1 nh2 2011-08-14 00:47:59 UTC
Created attachment 193795 [details]
meld l.bad r.bad
Comment 2 nh2 2011-08-14 00:48:25 UTC
Created attachment 193796 [details]
meld l.bad r.bad (2)
Comment 3 nh2 2011-08-14 00:48:53 UTC
Created attachment 193797 [details]
meld l.good r.good
Comment 4 nh2 2011-08-14 00:49:14 UTC
Created attachment 193798 [details]
meld l.good r.good (2)
Comment 5 Kai Willadsen 2011-08-14 02:04:47 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 652996 ***