On Wed, Jul 23, 2014 at 05:50:00PM +0200, Stefan Sperling wrote:
> On Wed, Jul 23, 2014 at 02:02:39PM +0200, Matthias Vorwerk wrote:
> > Hi,
> >
> > setting the svn property svn:global-ignores to the repository root (or some
> > higher level directory in the repository) - it obviously does not get inherited
> > if I only checkout and work in some lower-level directory (until
> > subversion-1.8.9) .
> >
> > It looks like the parent directory containing the svn:global-ignores property
> > must be present in the workspace. This seems to be in contrast to e.g. the
> > svn:auto-props property which may not be present in the workspace - it seems to
> > be looked for also on the server - which is what I expect.
> >
> > So the effect of the current svn:global-ignores handling is that the client
> > behavior depends on the hierarchy which is checked out in the workspace.
> >
> > Can you reproduce this bahvior?
> >
> > Regards,
> > Matthias
>
> Yes, this is a bug.
>
> The function filter_unwanted_props() in libsvn_wc/wc_db.c seems filters out
> the cached global-ignores prop because the property names it compares are
> different (one is qualified with "svn:" and the other isn't), even though
> they should be the same:
>
> 10240 if (strcmp(ipropname, propname) != 0)
> (gdb) p ipropname
> $5 = 0x21281cfda20 "global-ignores"
> (gdb) p propname
> $6 = 0x211f750bba6 "svn:global-ignores"
>
> I'm not sure off-hand how to fix this.
> I've filed http://subversion.tigris.org/issues/show_bug.cgi?id=4515
>
> Thanks for your report.
I tried to look into this today but I cannot reproduce this bug anymore.
I should have written a reproduction script.
Matthias, do you have a way of reliably triggering this bug? Thanks.
Received on 2014-08-04 17:09:31 CEST