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 650250 - meld /path/to/vcs does not work when cwd does not contain a vcs
meld /path/to/vcs does not work when cwd does not contain a vcs
Status: RESOLVED FIXED
Product: meld
Classification: Other
Component: dirdiff
1.5.x
Other Linux
: Normal normal
: ---
Assigned To: meld-maint
meld-maint
Depends on:
Blocks:
 
 
Reported: 2011-05-15 19:40 UTC by Julian Taylor
Modified: 2011-05-29 02:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Julian Taylor 2011-05-15 19:40:53 UTC 
meld /path/to/vcs only opens window with an empty location when /path/to/vcs points to a vcs.

If you click on e.g. flatten in the opened meld you get following tracebacks:
> ./meld.git/bin/meld /path/to/vcs
...
Traceback (most recent call last):

+ Trace 227130

  • File "/home/jtaylor/tmp/meld.git/meld/vcview.py", line 423 in on_button_flatten_toggled 
    self.refresh()
  • File "/home/jtaylor/tmp/meld.git/meld/vcview.py", line 584 in refresh 
    self.set_location( self.model.value_path( self.model.get_iter_root(), 0 ) )
  • File "/home/jtaylor/tmp/meld.git/meld/tree.py", line 111 in value_path 
    return self.get_value(it, self.column_index(COL_PATH, pane))
TypeError: iter must be a GtkTreeIter 


It seems to execute valid_repo() in the directory where meld was started.
If that directory does not contain a vcs you get the empty window.
If you do have a vcs in that folder it will work, even when the vcs is a different one than the one pointed to by /path/to/vcs

downstream bug:
https://bugs.launchpad.net/ubuntu/+source/meld/+bug/770549
verified with git in current git head 1e097face620
Comment 1 Kai Willadsen 2011-05-29 02:21:10 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.