X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:content-type:content-transfer-encoding; q=dns; s=default; b=J4U
	tbur12vG2oml2V5WYYUN+Qb/GseDJ5/tabGv4tRN4eQHnUR0nVORW5LemWPsppWD
	0eO+sCTxnb4HR0pZcRToRrdMHXdwhSiB817ja3kQCypopwCR/XQRn7/pOYCQPffa
	3Iy78heMuJ5f0WjBXML5Ir0ACVtdlPNy/gPQEGAo=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:content-type:content-transfer-encoding; s=default; bh=uug7hJNdM
	JXgg2XUmsIOhkDnnwE=; b=VDU4h9g6vjlaSJmvD8eCR6iUKCQmKdPSbhCWmTDIQ
	nwqSaUtfKUXV3xJpz7jcXlZ7kbVtg+0KPRh0vxUIhX6xpoq4ayAtCD6ShStqjX8/
	Se9WZ8IZ3ba5ekg1tuO5UC0TyVx9a1lxi+q2CnOkBstQ5xXmlkupDsfk5PmwU1rs
	Ag=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-2.5 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,FREEMAIL_FROM autolearn=ham version=3.3.2
X-HELO:	smtp204.alice.it
Message-ID:	<524B3694.4020703@alice.it>
Date:	Tue, 01 Oct 2013 22:54:44 +0200
From:	Angelo Graziosi <angelo DOT graziosi AT alice DOT it>
User-Agent:	Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version:	1.0
To:	Cygwin <cygwin AT cygwin DOT com>
Subject:	Re: What is wrong with SVN?

David Stacey wrote:
> I think what you're seeing here is what we term a BLODA - some non-Cygwin application interfering with a Cygwin application. In your case, if you're not running a native Windows svn client then anti-virus is top of the suspect list. I know you claim that you have used MSE for years, but anti-virus tools update very frequently, and their behaviour can (and does) change. See the following link, under "File access problems":
> http://cygwin.com/faq/faq.html#faq.using.bloda
>
> Your best bet is to either disable or tune the anti-virus tool so that it doesn't scan the '.svn' directory inside your working copy. If you do this, does the check out complete successfully? If you are not able to try this, can you get svn to recover? Try these two commands in succession:
>
>     $ svn cleanup <directory>
>     $ svn update <directory>
>
> Does the check out complete (or at least get a little further)?
>
> I've taken a look at the cygcheck output that you attached and it seems to be OK. So unless anyone else on this list can provide further insight, it really looks as if a third party (probably your anti-virus) is locking the 'wc.db' file whilst svn is trying to update it - and there's not much we can do about that.

As suggested here,

   http://gcc.gnu.org/ml/fortran/2013-09/msg00067.html

there is a git mirror which allows to download the fortran-dev branch..

Thanks,
  Angelo.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -