public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Cc: Jim Reisert AD1C <jjreisert@alum.mit.edu>
Subject: Revert coreutils 9.1 to test 8.32 to curr stable
Date: Mon, 6 Jun 2022 17:33:02 -0600	[thread overview]
Message-ID: <121ccc64-bb8e-30c1-2fba-b76920545a21@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAK-n8j6kmto82kLgtk4+zajY9trjhhQG=U2BdjiScbMa91-mZg@mail.gmail.com>

Verified below issue with coreutils 9.1 promoted last night to stable!
Problem does not occur in 8.32, so can we please revert coreutils 9.1 to 
test and restore 8.32 to stable.
Or is there some process by which I can do so?


On 2022-05-24 10:33, Jim Reisert AD1C wrote:
>> 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.
> 
> 


-- 
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.]

       reply	other threads:[~2022-06-06 23:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220521145633.53343-1-Brian.Inglis@SystematicSW.ab.ca>
     [not found] ` <CAK-n8j6kmto82kLgtk4+zajY9trjhhQG=U2BdjiScbMa91-mZg@mail.gmail.com>
2022-06-06 23:33   ` Brian Inglis [this message]
2022-06-07  9:24     ` Brian Inglis
2022-06-07  9:39     ` Jon Turney
2022-06-07 16:48       ` Brian Inglis
2022-06-07 18:48         ` Jon Turney

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=121ccc64-bb8e-30c1-2fba-b76920545a21@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin-apps@cygwin.com \
    --cc=jjreisert@alum.mit.edu \
    /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).