Do we have a prop-time bug?

Hello

If I run the following status command on my Subversion working copy

$ strace -e trace=open svn st ../svn 2>&1 > /dev/null | grep /prop-base/

then I see all the prop-base files that get opened. Given that I have
no property modifications I don't expect to see any, but there are
quite a few.

Typically I see lines like

open("../svn/tools/examples/.svn/prop-base/svnlook.py.svn-base", O_RDONLY) = 3

and when I examine ../svn/tools/examples/.svn/entries I see

<entry
   committed-rev="4470"
   name="svnlook.py"
   text-time="2003-02-09T23:21:56.000000Z"
   committed-date="2003-01-20T19:18:20.646842Z"
   checksum="67f2f11c66db2641ece7dd6567041637"
   last-author="philip"
   kind="file"/>

Can anyone else reproduce this? I'm interested mainly in those who
have committed, because what the files appear to have in common is
that they are all files I have committed sometime in the past. In
most, but not all, cases I see that the dodgy files don't have a
prop-time value listed, in a few cases there is a value and it is
out-of-date.

Next, if I run the command

$ strace -e trace=open svn st ../svn 2>&1 > /dev/null | grep dir-prop-base

I get a list of the dir-prop-base files that get opened. Here there
usually is a prop-time entry but it is out-of-date and does not
correspond to the timestamp on the property file file.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org