From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Updated: coreutils 9.1 cp problem
Date: Mon, 6 Jun 2022 21:52:24 -0600 [thread overview]
Message-ID: <2012d151-f573-4790-552a-dbbb18c56d02@SystematicSw.ab.ca> (raw)
In-Reply-To: <DB6P18901MB0055498078C3B142519D7AB7A4A59@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM>
Hi Fergus,
Verified and confirmed.
Please reinstall 8.32 until I can get this reverted in setup.
Have requested 9.1 be reverted to test and 8.32 reverted to current stable.
On 2022-06-06 21:21, Fergus Daly wrote:
> Since updating from coreutils 8.32 I’m getting a weird glitch from cp.
> If /location1/dir1/ contains additional material to /location2/dir1/ (as might frequently be the case when maintaining a backup) then the command
> $ cp -vrn /location1/dir1 /location2
> should copy the additional material across. (I do this regularly, working in two locations on two machines with a stick to manage the transactions.)
> Since updating coreutils, this command yields an error message as follows:
> $ cp -vrn /location1/dir1 /location2
> /bin/cp: cannot create directory '/location2/dir1': File exists
> I haven’t tried any other variations on cp or explored any other commands (e.g. ls) that have altered with the update.
> This occurs in both 32-bit and 64-bit Cygwin.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2022-06-07 3:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 3:21 Updated: coreutils 9.1 Fergus Daly
2022-06-07 3:52 ` Brian Inglis [this message]
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=2012d151-f573-4790-552a-dbbb18c56d02@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).