Comment 3 for bug 794210

My repository is at svn://gashler.com/meldtest. Here are the steps that
repro for me:

svn co svn://gashler.com/meldtest
cd meldtest
echo "changed" > hi.txt
meld .
double-click on hi.txt
observe the issue

This repository is quite minimalistic, so I doubt that it is part of the
problem. Here are the steps I used to create it:

svnadmin create ./meldtest
add the line "anon-access = write" to meldtest/conf/svnserve.conf
svnserve -d -r .
svn co svn://localhost/meldtest ./test
cd test
echo "original" > hi.txt
svn add hi.txt
svn commit -m "initial commit"

If the repository itself is not part of the problem, and I'm pretty-sure
it is not, then there must be some other difference between our
machines. It's a 64-bit machine. I did a fresh install of Kubuntu on a
newly-formatted machine just hours before I found and reported the bug,
so I didn't really have much time to do anything too unusual. Meld has
worked perfectly for me in the past on the same machine with at least 5
different versions of Ubuntu, so I'm pretty-sure the problem is related
to recent changes. I'm using ReiserFS for the first time instead of
Ext3, and I mounted /home on its own partition, but I'm pretty-sure none
of that should have any effect on how Python interacts with the file-system.

Would it help if I inserted a few lines that would print out some
additional information on my machine, perhaps near misc.py line 245? I
have never programmed in Python before, but I am capable in other
languages, so I'd be willing to try if you could give me some guidance
about what info would be helpful and how to express a print statement in
Python.

On 06/08/2011 01:40 AM, Julian Taylor wrote:
> I can't reproduce this, can you provide a example repository which
> reproduces the crash?
>
> ** Changed in: meld (Ubuntu)
> Status: New => Incomplete
>