From: "Fergus" <fergus@bonhard.uklinux.net>
To: <cygwin@cygwin.com>
Cc: <fergus@bonhard.uklinux.net>
Subject: Re: Updated [test]: coreutils-8.24-2
Date: Wed, 26 Aug 2015 22:50:00 -0000 [thread overview]
Message-ID: <001c01d0e04c$d8ebc210$8ac34630$@bonhard.uklinux.net> (raw)
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
next reply other threads:[~2015-08-26 22:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 22:50 Fergus [this message]
2015-08-26 23:28 ` Eric Blake
2015-08-26 23:28 ` Fergus
2015-08-26 23:50 ` Eric Blake
2015-08-27 20:26 ` Sam Edge
2015-08-27 20:51 ` Peter Rosin
2015-08-27 21:40 ` Helmut Karlowski
2015-08-28 0:53 ` Sam Edge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001c01d0e04c$d8ebc210$8ac34630$@bonhard.uklinux.net' \
--to=fergus@bonhard.uklinux.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).