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:from:to:cc:subject:date:message-id :mime-version:content-type:content-transfer-encoding; q=dns; s= default; b=pvaZrYT3tQMR6LRDlXfswRn4ohgOBwIZ8l0b0xY/FCI5+OTSlw6jI QtRzqVNfXXOF3N5V/lPI0CfPCCRtqAh7QrhyCN/YQi0wSG3tytBp98dm7J4NzQxZ IZd0J7jHkuM3Tec0n89OcYaOsrLIgrQ/0jgkzNCivV3BnkuHJnXlsk= 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:from:to:cc:subject:date:message-id :mime-version:content-type:content-transfer-encoding; s=default; bh=1ofl+2HNMJ/j73gGt8FQXp4rWw0=; b=Zc5O5J0n3WyPuSghdByfb+iZyldh 84SL4so4aiTrKcrox5kcWt9fdJclIrlF7Z5WL6vl8jhctPTHiw1Ctd8rg6HO2gEw n62L6cm2Sdu4/Jt1l12VdFh7ihNixbt4QdYSOHM+R0GPxtkD3VfgcbUFNUW+Uagu 7wh7RITinJ5WAKo= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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=-0.2 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 X-HELO: know-smtprelay-omc-9.server.virginmedia.net X-Spam: 0 X-Authority: v=2.1 cv=TNS4MARa c=1 sm=1 tr=0 a=3mmLVpx7njBr2j334fpFjQ==:117 a=3mmLVpx7njBr2j334fpFjQ==:17 a=tdKlQm_5AAAA:8 a=kj9zAlcOel0A:10 a=vNQKSpHK5gFILvjSW1wA:9 a=CjuIK1q_8ugA:10 From: "Fergus" To: Cc: Subject: Re: Updated [test]: coreutils-8.24-2 Date: Wed, 26 Aug 2015 23:16:24 +0100 Message-ID: <001c01d0e04c$d8ebc210$8ac34630$@bonhard.uklinux.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Yesterday's update from coreutils-8.23-4 to 8.24-1 has done something horrible to cp. Previously cp -r {sourcepath}/subdirectory {targetpath} is allowed even when {targetpath}/subdirectory already exists - which, very often or even usually, it does. (A very common context is where a Cygwin user maintains their own installation resource under /release/ and seeks to grow the resource after an update! But instances are multiple.) However under 8.24-1 the instruction is halted with an error message if {targetpath}/subdirectory already exists. Surely this is an accident and not an intended property of the update?? I have not tried [test]: coreutils-8.24-2 and I do not know whether this and maybe other peculiarities of 8.24-1 have been identified and corrected, but hope that this will eventually happen? Thank you! Fergus -- 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