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

Re: Re: Re: can't open .svn\tmp\tempfile.tmp: access is denied

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Tue, 3 Mar 2009 22:15:35 +0000

2009/3/3 Mubasher Hanif <mubasherhaneef_at_yahoo.com>:
>> 2009/3/3 Mubasher Hanif <mubasherhaneef_at_yahoo.com>:
>> >> Mubasher Hanif wrote:
>> >> > Does anyone found any other good solution other than adding exclusion to McAfee?
>> >>
>> >> How about "uninstalling McAfee"?
>> >>
>> >> Sorry, but if the $%&*#@! virus scanner is keeping files locked when
>> >> it's not supposed to you're not going to find "another good solution"
>> >> unless McAfee get their act together and fix their broken behaviour...
>> >>
>> >> --
>> >> Kurt Bernhard Pruenner --- Haendelstrasse 17 --- 4020 Linz --- Austria
>> >> .......It might be written "Mindfuck", but it's spelt "L-A-I-N".......
>> >> np: Telefon Tel Aviv - You Are the Worst Thing in the World
>> >>     (Immolate Yourself)
>> >
>> > Well, with due respect, first of all I can't ask 100 people in my office to uninstall some software and secondly according to our company policy we are not suppose to disable McAfee even for a moment.
>> >
>> > Just to mind you it could be broken behavoiur of *Tortoise*. If you read thread and even we had same experience that everything was working perfect with previous version of *Tortoise*.
>> >
>> > Anyhow, thanks for your suggestion.
>> All subversion operations are performed by the subversion libraries,
>> not by TortoiseSVN. And as has already been explained, you won't see
>> this with the command line client because virus scanners treat console
>> apps differently. If you think Subversion has broken behaviour then
>> you need to report it on the subversion mailing list. Be prepared to
>> back up your claims with solid evidence that the fault is with
>> subversion and not McAfee.
> If you read my earlier reply again, then it's clearly stated that "It could be Tortoise". I didn't claim that it is Tortoise. Honestly, I hate to play blame game without evidence.
> And the only proof that I have so far that we saw broken/whatever behaviour on three different machines and like I said everything was working perfect on old version of Tortoise and with same version of McAfee.

I am not trying to shed blame. I only said it is not (or at least very
unlikely to be) Tortoise because that part is done by the SVN library.
I did not say that it is *not* SVN, so if you have evidence to suggest
that it is you need to take it to the subversion users list. But it
would need to be more evidence than "it was working before and it
ain't working now".

> Again, I am not blaming anyone here and we are going to ask our IT help to push that exclusion in all McAfee installations.

That's the best plan for now. Subversion 1.7 will include a completely
rewritten working copy structure using an SQLite database in place of
the .svn folder structure. That may or may not help, but it is a long
way off yet as 1.6 is still in its release cycle.


:       ___
:  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 2009-03-03 23:15:46 CET

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

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