Re: Meld does not detect changes in subversion

[Kai Willadsen <kai willadsen gmail com>]

On 3 December 2014 at 23:10, Copernica BV, Emiel Bruijntjes
<emiel bruijntjes copernica com> wrote:
> On 03-12-14 13:04, Kai Willadsen wrote:
> > On 2 December 2014 at 05:21, Copernica, Emiel Bruijntjes
> > <emiel bruijntjes gmail com> wrote:
> > > Hi,
> > >
> > > I've been an enthusiastic meld user for a long time, but since I've
> > > upgraded
> > > my computer to Ubuntu 14.10, meld no longer works correctly in
> > > combination
> > > with SVN.
> > >
> > > My setup:
> > >
> > > Ubuntu 14.10
> > > Subversion client 1.8.10
> > > Meld version 3.13.0
> > >
> > > BTW: as you can see, I am using the very latest meld version from the git
> > > repository, because I hoped that the problem was already resolved.
> > >
> > > Now the problem: when I'm in a subversion directory with uncommitted
> > > changed
> > > files, I used to run "meld ." to show all the changes. When I do this now
> > > however, meld reports no changes at all. It only shows an empty
> > > directory,
> > > with no files or subdirectories at all. No changes are shown.
> >
> > What directory are you running "meld ." on? Is it it the repository
> > root or somewhere down in the tree? If the latter, then please try
> > running from the root. (It should work either way, but would help
> > narrow down what's wrong.)
> >
> > Do you get any tracebacks or other debugging on the command line?
> >
> > cheers,
> > Kai
>
> That's a good question, the problem indeed only occurs when I run it from a
> directory inside the tree, and not from the top level directory. When
> running it from the root, all modified files are correctly recognized.
>
> There are no errors or traces reported, it just doesn't detect any changes
> when running from a sub-dir.

In that case, can you please check that you've pulled and are actually
running current master? As far as I know, this was fixed in:
    https://git.gnome.org/browse/meld/commit/?id=352f4f3cb9936e4099275d2267d7b7dea94ae6e0
and has also been fixed in 3.12.2 release.

If master doesn't fix your problem, then maybe something went weird
with the cherry-pick; if 3.12.2 doesn't fix it then this would seem to
be a different problem.

cheers,
Kai