Finally triggered a memory over here - almost certainly a svndumpfilter
operation that filtered out commit contents.
Eric.
On 3/14/14, 2:25 PM, Eric Johnson wrote:
> More puzzling then either case you suggest.
>
> Doing "svn log -v --xml ..." directly on the server (thus
> side-stepping authorization questions) yields:
>
> <logentry
> revision="2">
> <paths>
> </paths>
> </logentry>
> <logentry
> revision="3">
> <paths>
> </paths>
> </logentry>
> <logentry
> revision="4">
> <paths>
> </paths>
> </logentry>
> <logentry
> revision="5">
> <paths>
> </paths>
> </logentry>
> <logentry
> revision="6">
> <paths>
> </paths>
> </logentry>
> <logentry
> revision="7">
> <paths>
> </paths>
> </logentry>
> <logentry
> revision="8">
> <paths>
> </paths>
> </logentry>
> <logentry
> revision="9">
> <paths>
> </paths>
> </logentry>
> <logentry
> revision="10">
> <paths>
> </paths>
> </logentry>
>
> It's like the only thing left of these revisions is just the revision
> #. Even svnlook on the server yields blank responses.
>
> $ svnlook info _______________ --revision 2
>
>
> 0
> $ svnlook info _______________ --revision 3
>
>
> 0
>
> Anyone seen anything like this before?
>
> Eric.
>
> On 3/14/14, 12:18 PM, Philip Martin wrote:
>> Stefan Sperling <stsp_at_elego.de> writes:
>>
>>> On Fri, Mar 14, 2014 at 10:51:56AM -0700, Eric Johnson wrote:
>>>> Just encountered a weird issue....
>>>>
>>>> I'm seeing Subversion log entries with no data. For example, svn
>>>> log output
>>>> that looks like the following:
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>> r2 | (no author) | (no date) | 1 line
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>> r3 | (no author) | (no date) | 1 line
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>> r4 | (no author) | (no date) | 1 line
>>>>
>>>> ....
>>>>
>>>> How is this possible? Have I lost data?
>>>>
>>>> svnadmin verify doesn't report any problems.
>>>>
>>>> Eric.
>>> Perhaps the authz configuration denies your user access to one
>>> or more paths which were modified in these revisions. In this
>>> case the log message and changed paths list are never shown since
>>> doing so might reveal the existence of secret files.
>> If authz denies access to some, but not all, of the paths modified in a
>> revision then log shows svn:author and svn:date but does not show
>> svn:log. That is not what is shown above.
>>
>> If authz denied access to all of the paths modified in a revision then
>> log does not show any of svn:author, svn:date or svn:log. That could be
>> what is shown above. Given read access to the root and no access to a
>> subdir then revisions that only modify paths in the subdir produce that
>> output.
>>
>> The other possibility is that svn:date and svn:author have been deleted
>> from the revisions.
>>
>
Received on 2014-03-15 00:12:21 CET