svnadmin verify changing its diagnosis?

I ran 'svn admin verify' yesterday on a repository and it failed
(returned non-zero and threw the 'malformed header' message.) Today
when I run 'svnadmin verify' it completes successfully for multiple
runs. fsfsverify.py (on a copy of the repos) didn't seem to find any
problems either. This using svn version 1.3.0 (r17949).

Anyone else ever see 'svnadmin verify' change its mind before?

Yesterday:
...
* Verified revision 797.
* Verified revision 798.
svnadmin: Found malformed header in revision file
<EOF>

Today:
...
* Verified revision 798.
* Verified revision 799.
* Verified revision 800.
* Verified revision 801.
* Verified revision 802.
* Verified revision 803.
...
* Verified revision 1306.
<EOF>

*****

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA621

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 5 17:45:41 2006