On 11 March 2010 17:41, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 11.03.2010 15:01, Amit Kravzov wrote:
>>> On Thu, Mar 11, 2010 at 08:43, Amit Kravzov<amitkar_at_rafael.co.il> wrote:
>>>>> On 11 March 2010 09:01, Amit Kravzov<amitkar_at_rafael.co.il> wrote:
>>>>>> Hi Simon,
>>>>>> We are checking this issue with Neon support for more details.
>>>>>> For meanwhile, is it possible for you to compile and provide us Tortoise 1.6.7 with prior Neon version that worked with Tortoise 1.6.6 so we can check it with our server kerberos configuration?
>>>>> Why don't you just revert to using 1.6.6 instead, or is there a bugfix
>>>>> in 1.6.7 that you need as well?
>>>> Hi Simon,
>>>> Technically I can revert, but this will not fix the issue. It will be very useful because we would be able to indicate that neon 0.29.x is the cause for this issue and be able (with your help) to deliver future TortoiseSVN releases without the problem.
>>> Why do you say reverting to 1.6.6 won't fix the issue? If 1.6.6
>>> worked, and 1.6.7 doesn't, go back to 1.6.6 and it almost certainly
>>> will work.
>> By saying "not fix the issue" I mean that future releases will be delivered with neon 0.29.3 or later so the problem will continue on. I want to contribute for others and not just fix my local problem.
> But us compiling 1.6.7 with an older version of neon won't help either.
> That would be the same as you reverting back to 1.6.6.
I think he is just wanting to pin this down to Neon rather than any
other change in TSVN or the SVN library. We could switch the 1.6.x
nightly back to an older Neon, but when does that get built?
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-03-11 18:56:54 CET