From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: Cygwin <cygwin@cygwin.com>
Subject: Re: Test: coreutils 9.1 (TEST)
Date: Tue, 24 May 2022 10:33:29 -0600 [thread overview]
Message-ID: <CAK-n8j6kmto82kLgtk4+zajY9trjhhQG=U2BdjiScbMa91-mZg@mail.gmail.com> (raw)
In-Reply-To: <20220521145633.53343-1-Brian.Inglis@SystematicSW.ab.ca>
[-- Attachment #1: Type: text/plain, Size: 1949 bytes --]
> The following test package has been uploaded to the Cygwin distribution:
>
> * coreutils 9.1
I am having a problem with "cp" that is not present in the previous
(non-test) version. I'm running the latest Cygwin on Windows 10:
CYGWIN_NT-10.0-19044 8PZCBK3 3.3.5-341.x86_64 2022-05-13 12:27 UTC
x86_64 Cygwin
The "cp" commands are in a Makefile. These are all text (not binary)
files. "here" is a directory.
if [ -a 2022/QSN2205.EXC ]; then cp -pvf 2022/QSN2205.EXC here; fi
if [ -a 2022/QSN2205.TXT ]; then cp -pvf 2022/QSN2205.TXT here; fi
if [ -a 2022/ignore.csv ]; then cp -pvf 2022/ignore.csv here; fi
These are the target files that are being copied *to*:
-rw-rw----+ 1 jr920141 Domain Users 11022 May 23 08:01 here/ignore.csv
-rw-rw----+ 1 jr920141 Domain Users 303543 May 23 10:25 here/QSN2205.EXC
-rw-rw----+ 1 jr920141 Domain Users 14395440 May 23 08:00 here/QSN2205.TXT
These are the source files that are being copied *from*:
-rw-rw----+ 1 jr920141 Domain Users 11303 May 24 08:20 ignore.csv
-rw-rw----+ 1 jr920141 Domain Users 20944 May 24 10:17 QSN2205.EXC
-rw-rw----+ 1 jr920141 Domain Users 14941120 May 24 08:19 QSN2205.TXT
It just so happens that the files are (now) the same. I had already done
the copy and no longer have the old files that were in the "here"
directory. But it doesn't matter whether the files are the same or
different. The problem still occurs.
This is the result:
[8PZCBK3:~/DXspots] $ make here
'2022/QSN2205.EXC' -> 'here/QSN2205.EXC'
'2022/QSN2205.TXT' -> 'here/QSN2205.TXT'
cp: cannot create regular file 'here/QSN2205.TXT': File exists
It makes no sense to me that the .EXC file was copied overtop of the
existing file, file but the .TXT file was not. The TXT file has DOS line
endings. The EXC file does not. I don't see why that would/should make a
difference.
cygcheck.out is attached.
--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, https://ad1c.us
[-- Attachment #2: cygcheck.out --]
[-- Type: application/octet-stream, Size: 95572 bytes --]
parent reply other threads:[~2022-05-24 16:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220521145633.53343-1-Brian.Inglis@SystematicSW.ab.ca>]
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='CAK-n8j6kmto82kLgtk4+zajY9trjhhQG=U2BdjiScbMa91-mZg@mail.gmail.com' \
--to=jjreisert@alum.mit.edu \
--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).