Bug 497831 - meld tree compare fails to step through individual files correctly
meld tree compare fails to step through individual files correctly
Product: Fedora
Classification: Fedora
Component: meld (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Brian Pepple
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-04-27 09:48 EDT by Bas Mevissen
Modified: 2009-12-18 04:22 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 04:22:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bas Mevissen 2009-04-27 09:48:19 EDT
Description of problem:
When doing a tree compare, I checked individual files for changes. Meld opened a new tap to compare two complementary files (from both trees). It scrolled to somewhere in the the files and refused to step from diff to diff with the up/down arrow buttons.

Version-Release number of selected component (if applicable):

How reproducible:
Happens now and then

Steps to Reproduce:
1. meld <tree1> <tree2>
2. go to some file
3. compare them and try to step from diff to diff
Actual results:
Only one diff is shown, somewhere in the file

Expected results:
Stepping (scrolling) through file from diff to diff

Additional info:
Latest version in SVN does not seem to have this problem.
Comment 1 Christoph Wickert 2009-05-10 12:23:54 EDT
BTW: Meld 1.3 was released on April 17th, I think you should consider an update.
Comment 2 Brian Pepple 2009-05-10 16:26:02 EDT
(In reply to comment #1)
> BTW: Meld 1.3 was released on April 17th, I think you should consider an
> update.  

It's updated in the devel branch, but it had enough changes that I'm not comfortable pushing it to F11 this late in the game.
Comment 3 Bas Mevissen 2009-05-11 07:06:32 EDT
I've used (for daily integration work) a version very close to 1.3.0 now since the opening of this bug report. It was stable, performance was good and I didn't notice any problems. So I feel very confident that 1.3.0 is a much better choice than 1.2.x on both F10 and F11. For the F11 case, one might consider releasing it shortly after the official F11 release due to freezing policies.
Comment 4 Bug Zapper 2009-11-18 06:51:55 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 5 Bug Zapper 2009-12-18 04:22:01 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.