Re: Updated: coreutils 9.1

Re: Updated: coreutils 9.1

[Brian Inglis]

Setup still shows 9.1 as test, but it should not be installed by anyone.
Setup now also shows 9.0 in test, and it can and should be installed by 
anyone who experienced issues with 9.1.

I ran it for a couple of weeks in my installs with no apparent issues 
before releasing it for testing.

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


On 2022-07-19 10:22, Jim Reisert AD1C wrote:
> On Mon, Jun 6, 2022 at 11:34 AM Jim Reisert AD1C wrote:
>> On Tue, May 24, 2022 at 10:33 AM, Jim Reisert AD1C wrote:

> Brian, the latest version (9.1-1 I think) from July 2022 still has the
> problem documented below. I reverted to the non-test version and it's
> working as it should.
> 
> [8PZCBK3:~/DXspots] $ make -n update_last_month
> make update QSNDATE=2206 LISDATE=Jun-2022 YEAR=2022
> make[1]: Entering directory '/cygdrive/c/users/jr920141/Home/DXspots'
> echo ""
> if [ -a 2022/QSN2206.EXC ]; then cp -pvf 2022/QSN2206.EXC here; fi
> if [ -a 2022/QSN2206.TXT ]; then cp -pvf 2022/QSN2206.TXT here; fi
> if [ -a 2022/ignore.csv  ]; then cp -pvf 2022/ignore.csv  here; fi
> 
> 
> [8PZCBK3:~/DXspots] $ make update_last_month
> make[1]: Entering directory '/cygdrive/c/users/jr920141/Home/DXspots'
> 
> '2022/QSN2206.TXT' -> 'here/QSN2206.TXT'
> cp: cannot create regular file 'here/QSN2206.TXT': File exists
> make[1]: *** [Makefile:262: here] Error 1

>>> The following package has been in test for two weeks with no reported or
>>> obvious issues and has now been upgraded to current stable in the Cygwin
>>> distribution:
>>>
>>> * coreutils     9.1

>> I really try NOT to contact the maintainers directly.  But in this
>> case, I did report a bug to the Cygwin list, and received no feedback.
>>
>> I copied my posting below:

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

Re: Updated: coreutils 9.1

[Jim Reisert AD1C]

On Tue, Jul 19, 2022 at 10:46 AM Brian Inglis wrote:

> Setup still shows 9.1 as test, but it should not be installed by anyone.
> Setup now also shows 9.0 in test, and it can and should be installed by
> anyone who experienced issues with 9.1.

9.0 (test) is working for me now, whereas 9.1 did not work. Thanks for
the fixes!

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, https://ad1c.us

Updated: coreutils 9.1

[Fergus Daly]

Brian Inglis wrote:

>> Setup still shows 9.1 as test, but it should not be installed by anyone.
>> Setup now also shows 9.0 in test, and it can and should be installed by
>> anyone who experienced issues with 9.1.

Jim Reisert wrote:

> 9.0 (test) is working for me now, whereas 9.1 did not work.
> Thanks for the fixes!

.. can and should be installed ..
Done.
9.0 (test) is working for me now, whereas 9.1 did not work.
(I had earlier reported a glitch.)
Thank you!

Re: Updated: coreutils 9.1

[Fergus Daly]

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