public inbox for
 help / color / mirror / Atom feed
From: Fergus Daly <>
To: "" <>
Cc: Fergus Daly <>
Subject: Re: Updated: coreutils 9.1
Date: Tue, 7 Jun 2022 03:21:43 +0000	[thread overview]
Message-ID: <DB6P18901MB0055498078C3B142519D7AB7A4A59@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM> (raw)

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.

             reply	other threads:[~2022-06-07  3:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07  3:21 Fergus Daly [this message]
2022-06-07  3:52 ` Updated: coreutils 9.1 cp problem Brian Inglis
     [not found] <>
     [not found] ` <>
     [not found]   ` <>
2022-07-19 16:45     ` Updated: coreutils 9.1 Brian Inglis
2022-07-19 17:06       ` Jim Reisert AD1C
2022-07-30  8:35 Fergus Daly

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DB6P18901MB0055498078C3B142519D7AB7A4A59@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM \ \ \

* 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).