On Thu, 21 May 2009, B Smith-Mannschott wrote:
> On Wed, May 20, 2009 at 17:54, <petesea_at_bigfoot.com> wrote:
>>
>> I too would really like to see a fix for this issue as soon as
>> possible. I've run into a different problem using svnsync with 1.5.5
>> (see http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2174274)
>> and have been unable to find any answers on it. Hoping a newer version
>> would fix it, I tried 1.6.2 and ran into the eol issue. Searching
>> around for solutions to this problem the best I've found is "stick with
>> 1.5.x", which doesn't help much in my case.
>
> I don't see how my patch for 3404 would help with the issue you
> describe. I don't think the two problems are related.
Sorry if I wasn't clearer... I wasn't expecting the 3404 patch to fix the
"node revision id" issue I'm seeing, the 3404 patch will only allow me to
test 1.6.2. I was only trying to express my desire to see the 3404 patch
incorporated into the next release as soon as possible.
Since I have no other idea how to fix the "node revision id" problem, I've
been hoping 1.6.2 will magically fix it, but I can't check that until I
get past the 3404 issue.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2352628
Received on 2009-05-21 19:51:25 CEST