[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: svn up problem using latest trunk revision (1092011)

From: Marc Haesen <Marc.Haesen_at_oneaccess-net.com>
Date: Thu, 14 Apr 2011 10:04:34 +0200

Indeed, r1092033 fixes the problem to.

Thanks,
Marc

-----Original Message-----
From: Bert Huijben [mailto:bert_at_qqmail.nl]
Sent: donderdag 14 april 2011 9:49
To: Marc Haesen; dev_at_subversion.apache.org
Subject: RE: svn up problem using latest trunk revision (1092011)

> -----Original Message-----
> From: Bert Huijben [mailto:bert_at_qqmail.nl]
> Sent: donderdag 14 april 2011 9:19
> To: 'Marc Haesen'; dev_at_subversion.apache.org
> Subject: RE: svn up problem using latest trunk revision (1092011)

> This patch would only affect the error:
>
> if (recorded_base_checksum && expected_base_checksum
> && strcmp(expected_base_checksum, recorded_base_checksum) !=
0)
> return svn_error_createf(SVN_ERR_WC_CORRUPT_TEXT_BASE, NULL,
> _("Checksum mismatch for '%s':\n"
> " expected: %s\n"
> " recorded: %s\n"),
> svn_dirent_local_style(fb->local_abspath, pool),
> expected_base_checksum, recorded_base_checksum);
>
> While you got the error from a different function.
>
> Are you sure you tested this on a clean checkout?
>
> (What HEAD version did you get on the checkout? I can't reproduce it
here)

While I couldn't reproduce this issue, I expect that it is fixed by
r1092033.
(In a different way than in your patch: It uses SHA1 properly when the
server doesn't provide a checksum)

        Bert
Received on 2011-04-14 10:05:08 CEST

This is an archived mail posted to the Subversion Dev mailing list.