On 18 Dec 2002, Karl Fogel <kfogel@newton.ch.collab.net> wrote:
> Martin Pool <mbp@samba.org> writes:
> > % svn up
> > svn: Incomplete data
> > svn: Delta source ended unexpectedly
> >
> > I got an Ethereal capture of the transaction (for lack of anything
> > better to do.) This is attached.
> >
> > If I extract and gunzip the response then it seems to be a complete
> > XML file. (Also attached.)
> >
> > The same error occurs every time I try to update that wc. I've tried
> > svn cleanup to no effect. I can send a tarball of the wc if you want.
>
> Hmmmm. This can happen when a wcprop gets out of date.
>
> Save that working copy somewhere.
>
> Then, examine the version-resource-urls in .svn/wcprops/*. The format
> is
>
> K <keylen>
> keystring
> V <valuelen>
> valuestring
>
> so one property's name/value pair takes four lines. The file ends
> with "END".
>
> The values should be pretty self-explanatory. The question is, do
> they match the committed-revs given in the .svn/entries file? If not,
> you have out-of-date wcprops.
OK, I'll check...
> Working on issue #689 as fast as can... :-)
That sounds good.
In addition, I'd like some kind of checksumming on directory changes.
Conceptually the client might send a checksum of the XML .svn/entries
file, to protect against corrupt directories getting into the
repository because of svn bugs. I think it is probably more complex
in practice because the server after applying equivalent changes might
end up with different files. Mixed-version repositories probably make
it complicated too.
Presumably property changes need protection too.
Probably somebody already thought about these two but #689 only talks
about text changes so I thought I'd mention it.
--
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 18 08:14:59 2002