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

Re: write-through-proxy and checksum error - URL path mangled in text data

From: Sebastian Brandt <sbrandt_at_gmx.de>
Date: Fri, 11 Nov 2011 10:22:31 +0100

Am 19.07.2011 12:58, schrieb Sebastian Brandt:
> Am 19.07.2011 12:35, schrieb Stefan Sperling:
>> On Tue, Jul 19, 2011 at 10:58:49AM +0200, Sebastian Brandt wrote:
>>> That discussion was two years ago; yet, I have been unable to find a
>>> bug/issue report of this problem, or a documented fix.
>>> So, before I post the bug report, I ask for feedback here - was the problem
>>> observed by others, has it already been fixed in some 1.6.x version, etc.
>>> Otherwise, I'll post this as an issue.
>> An issue has already been filed:
>> http://subversion.tigris.org/issues/show_bug.cgi?id=3445#desc9
>> It seems like some patches have been committed, but the issue
>> is not marked fixed yet. So apparently some problems remain?
> Ah, thanks, I was searching for "checksum error", mainly.
> "In r38533, I made the string substitution case-sensitive, and added
> Kamesh's recommended skip-filtering-if-its-a-noop logic."
> Unfortunately, this is the revision in the old tigris repository which I
> can't find any information about ... so, I don't know which releases do have
> this patch.
> http://svn.apache.org/viewvc/subversion/trunk/subversion/mod_dav_svn/mirror.c?view=log
> Ah,
> http://svn.apache.org/viewvc?view=revision&revision=878607 is it, it seems.
> 1.5.1 is r872368, so, a bit older than that patch.
> 1.5.7 is r878676 which should contain the "case-sensitive" patch, at least.
> debian 5.0.8 has 1.5.1 ... seems I need to get>=1.5.7 or>=1.6.4
>> I've moved the issue into the 1.7-consider milestone so it gets
>> more attention.
> Thanks.
> The biggest problem has already been solved, it seems; the fact that the
> payload is changed is not, though ...
Great ... on 21st Jul 2011 I installed subversion 1.6.12 (r955767) from
lenny-backports. And now I have to find out that the problem still persists
... I don't get it.
libapache2-svn 1.6.12dfsg-6~bpo50+1

Seems I have to get the source code of the debian package and have a look
whether the patch is in there, or not.

The HEAD version has another change (canonicalized_uri, root_dir), but the
FIXME is still there ... but maybe the fix for the "noop replace" (which
should hit in our case), and the case sensitive replace (which also should,
but does not, hit in our case) ...

Looks like changes on 916286 and 1064734
But 1064734 is just the removal of a not-NULL-check ...

How can I find out in which subversion releases the r878607, r916286 and
r1064734 are included?

Received on 2011-11-11 10:22:55 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.