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:date:from:reply-to:message-id:to:subject
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=fpGAcJOCr9JDMV1+N2miPa/5xrnDXen3a7r4WMzfZFleu+SMimG4c
	qWHXYsRE/y0932aBiWYwlTS6iI5Aic3MHBs9NV5grZgU+R9OH0LSrmOti3te2uUl
	LQnrvv1swwy2BdCtOUHW/QPIoBEt4UZobxJ+1bM9DA1oZgbgRhV4Q8=
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:date:from:reply-to:message-id:to:subject
	:mime-version:content-type:content-transfer-encoding; s=default;
	bh=dSkO3YfBAm+StTc8V0NEAZ0l4Sw=; b=MdceN7if8O1r8AWW6NWid9ayz1OZ
	PV6TVB/VMrbDKQ6gsv25V5m7ZWA61pgnBk7Go8jj+nBtHDFT4+lOsPCHg8HfrOW7
	LIrMzgGHU57JvCM/escL9YSqHgb4RPicqMOyaQO7NIA/8bX2yLQMK4dJJ5M/aHaI
	XoJuNDH8boXGM2I=
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=1.7 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_BODY_URIBL_PCCC,KAM_FROM_URIBL_PCCC,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO:	smtp.ht-systems.ru
Date:	Tue, 2 Dec 2014 15:44:46 +0300
From:	Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To:	cygwin AT cygwin DOT com
Message-ID:	<854823806.20141202154446@yandex.ru>
To:	All <cygwin AT cygwin DOT com>
Subject:	Random failures with Cygwin patch
MIME-Version:	1.0
X-IsSubscribed:	yes

Greetings, All!

Since some time ago, I started seeing Cygwin patch randomly leave files like
file.ext.oxugLoy behind. The files contain the supposedly patched version of
the original file, which was not replaced.

The problem is sporadic, and only reproducible from inside a script file. when
I run the same commands from the same terminal by hands, it always works.

Script file itself is very simple. Basically a bunch of lines

d2u file1.ext file2.ext file3.ext
patch -p 0 < "file1-3.ext.patch" || echo Fail.

Most patches are applied to more than one file.
At the same time, some files may get patched properly, while other leave these
strange leftovers.
It never "Fail.", but the files are left scattered, that are intended to be
moved in replacement.

The files ACLs are all the same and uninteresting.

$ getfacl file.ext
# file: file.ext
# owner: anrdaemon
# group: None
user::rw-
group::r--
other:r--

The only possible interesting moment is that the files are located on Samba
share. But it was working fine like 3-4 months ago, and nothing has been
changed in permission handling on the Samba end.

Anything I can check to move further?


-- 
WBR,
Andrey Repin (anrdaemon AT yandex DOT ru) 02.12.2014, <15:31>

Sorry for my terrible english...


--
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 -